On Wednesday 08 May 2013, Srinivas KANDAGATLA wrote: > the pinctrl driver calls syconf_claim(np, "st,alt-control) to get a > field and then do a read/write on the field. > > Just in pinctrl driver we use around 50-100 sysconf registers scatters > across different groups. > > Without these new APIs, its very difficult to pass this information to > the drivers. But are those necessarily things you would configure using DT? If there are so many registers that are shared between mutliple subsystems, maybe using drivers/mfd/syscon for that is taking things further than you should, since it is unlike what any of the other SoC families need from syscon. Can you describe how your syscon registers are laid out? Which subsystems beside pinctrl need to directly interact with it? Is there any logical structure in it or do you just have tons of bits scattered around an MMIO area? 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
