On Mon, Jun 18, 2018 at 10:45 AM, Linus Walleij <linus.walleij@xxxxxxxxxx> wrote: > This makes it possible to pass an initialized GPIO descriptor > to the driver through platform data. > > This is useful when we are dealing with EEPROMs on expansion > boards where the GPIO has to be looked up indirectly using a > connector abstraction (several systems using the same > connector) so the machine descriptor tables cannot be used > to associate the descriptor with the device and we then want > to pass this descriptor on to the EEPROM driver this way > instead. How this descriptor is supposed to be created? Whenever we probe the device we might add properties to it (consider how MFD does instansiate them), I guess same way GPIO lookup tables work. No? P.S. I really would like to hear a _strong_ argument why it can't be done using other means like built-in device properties or GPIO lookup tables (which on my opinion have to work in the similar way at run time). -- With Best Regards, Andy Shevchenko -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
