On Thu, Feb 14, 2013 at 1:22 PM, Lars Poeschel <poeschel@xxxxxxxxxxx> wrote: > On Wednesday 13 February 2013 at 13:51:12, Linus Walleij wrote: >> Have you considered this [pinctrl] approach? > > No, I haven't. And although this doesn't solve all my problems, I like the > idea very much! Thank you for this! But at the moment it looks to me that > this could be a bit overkill for setting this single register and I don't > think this is, what Grant meant me to do. So there is this corner case where some GPIO driver does some pinctrl business, I mean, really really little of it. And then it may be overkill. Sometimes though, the hardware actually can do a lot of this biasing and muxing it just wasn't part of the driver yet or done in e.g. boot loaders, and then it's usually better to use pinctrl. Adding custom APIs to the GPIO drivers will however always cause a maintenance burden on the GPIO maintainers, so that's why pinctrl & GPIO is nice. I don't know which case this would be though. Yours, Linus Walleij -- 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
