Hi Leela,
On Thursday 07 of November 2013 17:21:16 Leela Krishna Amudala wrote:
> This patch adds pmusysreg node to Exynos5 dtsi file to handle PMU
> register accesses in a centralized way using syscon driver
>
> Signed-off-by: Leela Krishna Amudala <l.krishna@xxxxxxxxxxx>
> Reviewed-by: Tomasz Figa <t.figa@xxxxxxxxxxx>
> ---
> arch/arm/boot/dts/exynos5.dtsi | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/arch/arm/boot/dts/exynos5.dtsi b/arch/arm/boot/dts/exynos5.dtsi
> index e52b038..ad6e47c9 100644
> --- a/arch/arm/boot/dts/exynos5.dtsi
> +++ b/arch/arm/boot/dts/exynos5.dtsi
> @@ -106,4 +106,9 @@
> #size-cells = <0>;
> status = "disabled";
> };
> +
> + pmu_syscon: syscon@10040000 {
> + compatible = "syscon";
> + reg = <0x10040000 0x5000>;
> + };
> };
>
Just to be safe, I would also add some SoC-specific compatible value to
this node. My proposal is "samsung,exynos5250-pmu" for the PMU of
Exynos5250 (unless all Exynos 5 SoCs really have identical set of PMU
registers, but based on your patch to WDT driver, I don't think so) and
put the node in dtsi of particular SoC.
We already have a PMU driver in arch/arm/mach-exynos and we should rather
allow it to bind to some device tree node and access the registers it
needs when we finally stop mapping PMU registers statically.
You should also document such binding somewhere. IMHO [1] would be a good
place for it.
[1] - Documentation/devicetree/bindings/arm/samsung/pmu.txt
Best regards,
Tomasz
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
