* Archit Taneja <[email protected]> [140416 06:20]:
> Add DT node for the ctrl-core sub module of the DRA7 control module. We map 
> the
> CTRL_MODULE_CORE address region up to 0x4a002d60, this region contains 
> register
> fields which configure clocks. The remainder of the registers are related to
> pad configurations or cross-bar configurations, and therefore aren't mapped.

Can you please check if this can just use the existing
regmap syscon mapping:

syscon = <&dra7_ctrl_general>;

See how the drivers/regulator/pbias-regulator.c is using the
syscon to initialize a regulator and then omap_hsmmc.c just does
the standard regulator calls.

Depending what the range 0x4a002000 0x6d0 contains, you may
want to set it up as another syscon area.

Regards,

Tony

 
> Signed-off-by: Archit Taneja <[email protected]>
> ---
>  arch/arm/boot/dts/dra7.dtsi | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
> 
> diff --git a/arch/arm/boot/dts/dra7.dtsi b/arch/arm/boot/dts/dra7.dtsi
> index 1c0f8e1..58bbdf3 100644
> --- a/arch/arm/boot/dts/dra7.dtsi
> +++ b/arch/arm/boot/dts/dra7.dtsi
> @@ -148,6 +148,19 @@
>                       };
>               };
>  
> +             ctrl_core: ctrl_core@4a002000 {
> +                     compatible = "ti,dra7-ctrl-core";
> +                     reg = <0x4a002000 0x6d0>;
> +
> +                     ctrl_core_clocks: clocks {
> +                             #address-cells = <1>;
> +                             #size-cells = <0>;
> +                     };
> +
> +                     ctrl_core_clockdomains: clockdomains {
> +                     };
> +             };
> +
>               counter32k: counter@4ae04000 {
>                       compatible = "ti,omap-counter32k";
>                       reg = <0x4ae04000 0x40>;
> -- 
> 1.8.3.2
> 
> 
> _______________________________________________
> linux-arm-kernel mailing list
> [email protected]
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to