On Wed, Dec 27, 2023 at 1:35 PM Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxx> wrote: > [snip] > > > > I dislike this approach entirely. Here's what I would do: > > > > In the reset core: parse the phandle of the reset-gpios property. Use > > the resulting node with gpio_device_find_by_fwnode(). If the device is > > not up yet, defer probe. You'll now have the GPIO device object. > > Retrieve its label using gpio_device_get_label(). Now you should have > > everything you need (the offset and flags of the GPIO you'll get from > > __of_parse_phandle_with_args()) to set up the lookup tables. See > > I don't get exactly what do you want to use as the cookie for lookup > reset controller? I'm not sure what you refer to as "cookie". :( > 1. GPIO controller node? No way, not enough > 2. GPIO label? > 3. Or some combination of above? This would work, I guess, a bit more > complicated cookie than just one pointer/unsigned long. > For a GPIO lookup you need: 1. The name of the target device (in your case "reset-gpio.X", you can either keep track of device IDs yourself or live with the fact that you may have one deferred probe between when the device is registered and bound and when you are able to read its final name for the lookup). 2. The label of the GPIO chip (whatever gpio_device_get_label() returns). 3. The hardware offset of the pin (which you can get by parsing the phandle). You may need additional lookup flags but the above allows you to correctly assign a GPIO to a device. No need for cookies. Bart > > include/linux/gpio/machine.h. An example of that would be in: > > bcm2835_spi_setup() in drivers/spi/spi-bcm2835.c. > > > > Then with a lookup table in place, you instantiate your device and > > it'll get its GPIO as it should. This is not ideal but much better > > than the above. > > > Best regards, > Krzysztof >
