On 10/06/13 15:02, Arnd Bergmann wrote:
> There are multiple ways of doing that, e.g. you could export a function
> from syscon.c that you call to register the device node and then import
> the regmap from syscon into your high-level driver again.
>
Hi Arnd/Linus,
Thankyou for your comments,
I did try using the full sysconf names in compatible and make use of
syscon driver, with this change the nodes look much neater.
The nodes changes to:
syscfg_sbc:syscfg@fe600000{
compatible = "st,stih416-sbc-syscfg", "syscon";
reg = <0xfe600000 0x1000>;
};
From:
syscfg_sbc:syscfg@fe600000{
compatible = "st,stih416-syscfg";
reg = <0xfe600000 0x1000>;
syscfg-range = <0 999>;
syscfg-name = "SYSCFG_SBC";
};
Also I got rid of the drivers/mfd/stixxxx-syscfg.c driver all together
for this basic support patch series, I will add this once there are new
high level functions.
Additional compatible string will allow code to get to regmap via syscon
apis.
I will get rid of this driver in next version for this series.
Thanks,
srini
> Arnd
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
