On Mon, Dec 7, 2020 at 4:49 PM Greg KH wrote:
> Sometimes we just do a "add a new driver to the real spot" that goes
> through the subsystem tree, and when that is accepted, I delete the
> driver in the staging tree. This is most often in networking.
That's unnice, it will loose the history, it
On Mon, Dec 07, 2020 at 04:40:06PM +0100, Linus Walleij wrote:
> On Mon, Dec 7, 2020 at 2:57 PM Sergio Paracuellos
> wrote:
> > On Mon, Dec 7, 2020 at 2:05 PM Linus Walleij
> > wrote:
>
> > > After this I think the driver looks good and can graduate from staging.
> > > Can you send a patch to m
On Mon, Dec 7, 2020 at 2:57 PM Sergio Paracuellos
wrote:
> On Mon, Dec 7, 2020 at 2:05 PM Linus Walleij wrote:
> > After this I think the driver looks good and can graduate from staging.
> > Can you send a patch to move this to drivers/pinctrl next
> >
> > I think drivers/pinctrl/pinctrl-rt2880.
Hi Linus,
On Mon, Dec 7, 2020 at 2:05 PM Linus Walleij wrote:
>
> On Sun, Dec 6, 2020 at 11:53 AM Sergio Paracuellos
> wrote:
>
> > If the gpio DT node has the 'gpio-ranges' property, the range will be
> > added by the gpio core and doesn't need to be added by the pinctrl
> > driver.
> >
> > By
On Sun, Dec 6, 2020 at 11:53 AM Sergio Paracuellos
wrote:
> If the gpio DT node has the 'gpio-ranges' property, the range will be
> added by the gpio core and doesn't need to be added by the pinctrl
> driver.
>
> By having the gpio-ranges property, we can map every pin between
> gpio node and pin
If the gpio DT node has the 'gpio-ranges' property, the range will be
added by the gpio core and doesn't need to be added by the pinctrl
driver.
By having the gpio-ranges property, we can map every pin between
gpio node and pinctrl node and we can stop using the deprecated
pinctrl_add_gpio_range()
