Javier Martinez Canillas wrote: > > Hello, > Hi, > On 01/20/2015 06:54 PM, Mike Turquette wrote: > > Quoting Sylwester Nawrocki (2015-01-20 06:04:00) > >> Hi, > >> > >> On 20/01/15 11:35, Javier Martinez Canillas wrote: > >> > When a power domain is powered off on Exynos5420 SoC, the input clocks of > >> > the devices attached to this power domain are re-parented to oscclk and > >> > restored to the original parent after powering on the power domain. > >> > > >> > So a reference to the input and parent clocks for the devices attached to > >> > a power domain are needed to be able to do the re-parenting. The DISP1 pd > >> > includes modules which uses the following clocks: > >> > > >> > ACLK_200_DISP1 (MIXER and HDMILINK) > >> > ACLK_300_DISP1 (FIMD1) > >> > ACLK_400_DISP1 (Internal Buses) > >> > > >> > Each of these clocks are generated as the output of a clock mux so add an > >> > ID for all of these clock muxes and their parents to be referenced in the > >> > DISP1 power domain device node. > >> > > >> > Signed-off-by: Javier Martinez Canillas <javier.marti...@collabora.co.uk> > >> > >> The patch looks OK to me, I'm fine with it being merged via Kukjin's tree > >> due to the dts dependencies (including other pending dts patches touching > >> the arch/arm/boot/dts/exynos5420.dtsi file). > >> I think we need also Mike ACK for that, I could also queue the patch for > >> the clk tree and create a topic branch, but merging both patches via > >> arm-soc seems a more sane option in this case. > >> > >> Acked-by: Sylwester Nawrocki <s.nawro...@samsung.com> > > > > Acked-by: Michael Turquette <mturque...@linaro.org> > > > > Thanks a lot Sylwester and Mike for your acks. > > Kukjin, could you please pick $subject and "Patch 2/2 ARM: dts: Add DISP1 > power domain for exynos5420" through your tree? > Sure, I will after applying Marek's generic power domain patch.
Thanks, Kukjin -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
