Message ID | 1472737551-15272-5-git-send-email-m.szyprowski@samsung.com |
---|---|
State | Superseded |
Headers | show |
[...] >>> I see some serious design problems with multiple entries in power domains >>> property. First how to show that some part of the device IS NOT in >>> any domain? >> >> Is that even possible? Every device should be in some power >> domain, even if it's just an "always on" power domain that we >> don't really control from software. > > > Right now none dts of which I'm aware of doesn't define the power domain for > the parts of the SoC, which are always on and doesn't need any additional > management. Actually there's is one reason for doing this, as it would allow devices to be monitored for device PM QoS constraints by the genpd governor. Although, I doubt's someone actually does it because of this benefit, at least yet. [...] Kind regards Uffe -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/arch/arm/boot/dts/exynos4x12.dtsi b/arch/arm/boot/dts/exynos4x12.dtsi index 3394bdcf10ae..4daea67546b9 100644 --- a/arch/arm/boot/dts/exynos4x12.dtsi +++ b/arch/arm/boot/dts/exynos4x12.dtsi @@ -74,6 +74,11 @@ compatible = "samsung,exynos4412-clock"; reg = <0x10030000 0x20000>; #clock-cells = <1>; + + isp-clock-controller { + compatible = "samsung,exynos4412-isp-clock"; + power-domains = <&pd_isp>; + }; }; mct@10050000 {
Exynos4412 clock controller contains some additional clocks for FIMC-ISP (Camera ISP) subsystem. Registers for those clocks are partially located in the SOC area, which belongs to ISP power domain. This patch extends clock controller node with ISP clock sub-node and link (phandle) to ISP power domain. Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com> --- arch/arm/boot/dts/exynos4x12.dtsi | 5 +++++ 1 file changed, 5 insertions(+) -- 1.9.1 -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html