Message ID | 20210302191613.29476-1-noltari@gmail.com |
---|---|
Headers | show |
Series | pinctrl: add BCM63XX pincontrol support | expand |
On Tue, Mar 2, 2021 at 8:16 PM Álvaro Fernández Rojas <noltari@gmail.com> wrote: > v2: introduce changes suggested by Linus Walleij and remove interrupts > - In order to use GPIO_REGMAP, the need to get gpio_chip from gpio_regmap > and use it for pinctrl_add_gpio_range() and gpio_chip.direction_input() > and gpio_chip.direction_output(). Looking so much better don't you think? :) If you also get rid of the exposed struct using DT gpio-ranges we are done I think, just need some DT review slack for the DT maintainers for the bindings. Yours, Linus Walleij
Hi Linus, > El 3 mar 2021, a las 10:29, Linus Walleij <linus.walleij@linaro.org> escribió: > > On Tue, Mar 2, 2021 at 8:16 PM Álvaro Fernández Rojas <noltari@gmail.com> wrote: > >> v2: introduce changes suggested by Linus Walleij and remove interrupts >> - In order to use GPIO_REGMAP, the need to get gpio_chip from gpio_regmap >> and use it for pinctrl_add_gpio_range() and gpio_chip.direction_input() >> and gpio_chip.direction_output(). > > Looking so much better don't you think? :) Yeah :) > > If you also get rid of the exposed struct using DT gpio-ranges we are > done I think, just need some DT review slack for the DT maintainers > for the bindings. I’m already preparing v3 series, introducing shared base code and simplifying everything :). > > Yours, > Linus Walleij Best regards, Álvaro.