On Tue, Jan 10, 2012 at 2:51 PM, Shawn Guo <[email protected]> wrote: > On Tue, Jan 10, 2012 at 11:43:28AM +0100, Linus Walleij wrote: >> What we need to know right now is what you need from the pin >> controller core to do that. We have a (custom) pinconf API now, >> does it fit the bill? >> > Hmm, I do not think it fits right away, as I do not think it's sensible > to have pinctrl client drivers call pin_config_set() directly.
OK that's more or less what Stephen said too so I'm cooking a config table ala pinmux with string identifiers. >> I have spent some time on generic pin config, it was not much >> commented so if it helps you please ACK the patches. >> > Since the ARM community is the one who is most interested in pinctrl > subsystem so far, I guess copying LAKML will help collect more comments > and various tags. (For example, I'm interested in pinctrl, but I do > not track LKML as close as I do for LAKML). True. I'll fix that. >> Next from discussions with Stpehen I've sort of figured out that >> we need a config mapping table of sorts and then a means to activate >> entries of that table at runtime. I'm trying to come up with something >> for this. >> > That's something we are waiting for pinconf being usable for imx. I'll fix something, please review when it appears! Thanks, Linus Walleij _______________________________________________ devicetree-discuss mailing list [email protected] https://lists.ozlabs.org/listinfo/devicetree-discuss
