Re: [PATCH v1] gpiolib: Don't probe gpio_device if it's not the primary device

On Fri, Feb 5, 2021 at 3:07 AM Saravana Kannan wrote: > Dmitry reported[1] boot error messages caused by > commit 4731210c09f5 ("gpiolib: Bind gpio_device to a driver to enable > fw_devlink=on by default"). > > gpio-1022 (cpu-pwr-req-hog): hogged as input > max77620-pinctrl max77620-pinctrl: pin

Re: [PATCH v1] gpiolib: Don't probe gpio_device if it's not the primary device

Hi Saravana, On Fri, Feb 5, 2021 at 3:09 AM Saravana Kannan wrote: > Dmitry reported[1] boot error messages caused by > commit 4731210c09f5 ("gpiolib: Bind gpio_device to a driver to enable > fw_devlink=on by default"). > > gpio-1022 (cpu-pwr-req-hog): hogged as input > max77620-pinctrl max77620

Re: [PATCH v1] gpiolib: Don't probe gpio_device if it's not the primary device

On Fri, Feb 5, 2021 at 3:08 AM Saravana Kannan wrote: > > Dmitry reported[1] boot error messages caused by > commit 4731210c09f5 ("gpiolib: Bind gpio_device to a driver to enable > fw_devlink=on by default"). > > gpio-1022 (cpu-pwr-req-hog): hogged as input > max77620-pinctrl max77620-pinctrl: pi

[PATCH v1] gpiolib: Don't probe gpio_device if it's not the primary device

Dmitry reported[1] boot error messages caused by commit 4731210c09f5 ("gpiolib: Bind gpio_device to a driver to enable fw_devlink=on by default"). gpio-1022 (cpu-pwr-req-hog): hogged as input max77620-pinctrl max77620-pinctrl: pin gpio4 already requested by max77620-pinctrl; cannot claim for gpi