Power Related Fixes for Exynos5250
Get series with b4
b4 am 1474895.cu1U1Gy5We@amdc1227Versions newest first
- v1 Latest3 of 5 patches 0 repliesNew
3 of 5 patches are in this archive. The cover letter announces 5.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | clk: samsung: exynos5250: Add CLK_IGNORE_UNUSED flag for the sysreg clock | +0 | 0 replies | |
| 2/5 | ARM: EXYNOS5: Fix PMU register configuration for local power blocks | +0 | 1 reply | |
| 3/5 | clk: max77686: Replace is_enabled() with is_prepared call-back | +0 | 1 reply |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/5] Power Related Fixes for Exynos5250
Hi Abhilash,
Quoted 20 lines · On Wednesday 11 of December 2013 17:27:04 Abhilash Kesavan wrote:
Patch 1 prevents the gating of sysreg clock on Exynos5250. Patch 2 is a re-send of an earlier patch.
(http://www.spinics.net/lists/linux-samsung-soc/msg15485.html)
Patches 3 and 4 are fixes for MAX77686 on Exynos5250 based Snow board (boot-up issues).
Patch 5 implements a power-off call-back for Exynos5250 that can be re-used for Exynos5420.The patches have been tested on an SMDK5250 based Chromebook.
Abhilash Kesavan (4):
clk: samsung: exynos5250: AddCLK_IGNORE_UNUSEDflag for the sysreg
clock
ARM: EXYNOS5: Fix PMU register configuration for local power blocks
clk: max77686: Replaceis_enabled()withis_preparedcall-back
ARM: dts: Setup the interrupt parent for max77686Olof Johansson (1):
ARM: EXYNOS5250: Implementpm_power_off
Quoted 6 lines
arch/arm/boot/dts/cros5250-common.dtsi | 11 ++++ arch/arm/mach-exynos/include/mach/regs-pmu.h | 3 + arch/arm/mach-exynos/pmu.c | 86 ++++++++++++++++++++------ drivers/clk/clk-max77686.c | 4 +- drivers/clk/samsung/clk-exynos5250.c | 3 +- 5 files changed, 86 insertions(+), 21 deletions(-)
You used the old and now invalid address of DT mailing list.
Anyway, there is no need to send patches for .dts* files to DT mailing list anymore. Just changes in drivers that affect how they handle data from DT and binding documentation (Documentation/devicetree/.*). So please drop the DT mailing list in next iteration of the series.
Best regards,
Tomasz