Re: [REGRESSION] mux/gpio.c is not able to get any gpio pins

2018-01-17 Thread Linus Walleij
On Wed, Jan 17, 2018 at 11:39 AM, Peter Rosin wrote: > On 2018-01-17 10:35, Linus Walleij wrote: >> I would first try to add the gpio range in the DTS. Then the >> GPIO core will add the range (the code is in drivers/gpio/gpiolib-of.c) >> and everything will be happy. > > If I, in the above menti

Re: [REGRESSION] mux/gpio.c is not able to get any gpio pins

2018-01-17 Thread Peter Rosin
On 2018-01-17 10:35, Linus Walleij wrote: > On Wed, Jan 17, 2018 at 12:57 AM, Peter Rosin wrote: >> On 2018-01-17 00:18, Linus Walleij wrote: > >>> I think gpiod_set_transitory() calls chip->set_config(chip, gpio, packed); >>> which calls gpiochip_generic_config() which calls >>> pinctrl_gpio_se

Re: [REGRESSION] mux/gpio.c is not able to get any gpio pins

2018-01-17 Thread Linus Walleij
On Wed, Jan 17, 2018 at 12:57 AM, Peter Rosin wrote: > On 2018-01-17 00:18, Linus Walleij wrote: >> I think gpiod_set_transitory() calls chip->set_config(chip, gpio, packed); >> which calls gpiochip_generic_config() which calls >> pinctrl_gpio_set_config() which calls >> pinctrl_get_device_gpio_

Re: [REGRESSION] mux/gpio.c is not able to get any gpio pins

2018-01-16 Thread Peter Rosin
On 2018-01-17 00:18, Linus Walleij wrote: > On Tue, Jan 16, 2018 at 10:47 PM, Peter Rosin wrote: > >> diff between the two: >> >> --- bootlog.good2018-01-16 22:39:29.196022434 +0100 >> +++ bootlog.bad 2018-01-16 22:39:51.474264534 +0100 >> @@ -118,7 +118,7 @@ >> 0x0018-0x001a

Re: [REGRESSION] mux/gpio.c is not able to get any gpio pins

2018-01-16 Thread Linus Walleij
On Tue, Jan 16, 2018 at 10:47 PM, Peter Rosin wrote: > diff between the two: > > --- bootlog.good2018-01-16 22:39:29.196022434 +0100 > +++ bootlog.bad 2018-01-16 22:39:51.474264534 +0100 > @@ -118,7 +118,7 @@ > 0x0018-0x001a : "oftree" > 0x0020-0x0070 : "