On Thu, Aug 29, 2013 at 11:31 AM, Sonic Zhang <sonic....@gmail.com> wrote: > On Thu, Aug 29, 2013 at 4:12 PM, Linus Walleij <linus.wall...@linaro.org> > wrote:
>> This is similar to the situation in the pinctrl-nomadik.c driver, >> where the pinctrl portions wait for the GPIO devices to instantiate >> before proceeding to probe "on top" of the GPIO blocks, using >> the latter to get to the registers. >> >> I am not sure we have found the best way to sort out this >> type of system, let's see what we can come up with. > > In the blackfin pinctrol-adi2 driver, I probe all gpio devices > independently after all logic pinctrl devices. When one gpio device is > probed, it can get its pinctrl device name from its platform data and > add its gpio range into the pinctrl device via > gpiochip_add_pin_range(). The gpio device don't need to know anything > else about its pinctrl device. This is ideal in the situation when there is a clear separation between the GPIO and pin control (muxing, biasing) registers. So you're doing the right thing. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
