From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Cc: linux-gpio <linux-gpio@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Marek Vasut <marex@denx.de>,
Roman Guskov <rguskov@dh-electronics.com>
Subject: Re: [PATCH v1 1/1] gpiolib: Read "gpio-line-names" from a firmware node
Date: Mon, 8 Mar 2021 13:45:06 +0200 [thread overview]
Message-ID: <YEYOQqFch8yTE2SZ@smile.fi.intel.com> (raw)
In-Reply-To: <CAHp75Vf9XbZ4S-2aqfQafaw8jJrW3oVQYEw06roi3zOBKRMmOA@mail.gmail.com>
On Sun, Mar 07, 2021 at 06:14:49PM +0200, Andy Shevchenko wrote:
> On Sun, Mar 7, 2021 at 4:22 PM Bartosz Golaszewski
> <bgolaszewski@baylibre.com> wrote:
> > On Fri, Mar 5, 2021 at 1:02 PM Andy Shevchenko
> > <andriy.shevchenko@linux.intel.com> wrote:
> > >
> > > On STM32MP1, the GPIO banks are subnodes of pin-controller@50002000,
> > > see arch/arm/boot/dts/stm32mp151.dtsi. The driver for
> > > pin-controller@50002000 is in drivers/pinctrl/stm32/pinctrl-stm32.c
> > > and iterates over all of its DT subnodes when registering each GPIO
> > > bank gpiochip. Each gpiochip has:
> > >
> > > - gpio_chip.parent = dev,
> > > where dev is the device node of the pin controller
> > > - gpio_chip.of_node = np,
> > > which is the OF node of the GPIO bank
> > >
> > > Therefore, dev_fwnode(chip->parent) != of_fwnode_handle(chip.of_node),
> > > i.e. pin-controller@50002000 != pin-controller@50002000/gpio@5000*000.
> > >
> > > The original code behaved correctly, as it extracted the "gpio-line-names"
> > > from of_fwnode_handle(chip.of_node) = pin-controller@50002000/gpio@5000*000.
> > >
> > > To achieve the same behaviour, read property from the firmware node.
...
> > Did you run the OF unit tests on this? The check for the parent dev
> > was added after a bug was reported that was only triggered in unit
> > tests.
>
> Parent is not used anymore. But I can run unittests next week (or if
> you know that they are failing now, can you please show the failure?).
For the record:
[ 40.587868] ### dt-test ### end of unittest - 190 passed, 0 failed
If you have tests failed, we need more information about what line fails, etc.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-03-08 11:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 12:02 [PATCH v1 1/1] gpiolib: Read "gpio-line-names" from a firmware node Andy Shevchenko
2021-03-05 12:11 ` Marek Vasut
2021-03-05 12:24 ` Andy Shevchenko
2021-03-05 12:26 ` Marek Vasut
2021-03-07 13:55 ` Bartosz Golaszewski
2021-03-07 16:14 ` Andy Shevchenko
2021-03-08 11:45 ` Andy Shevchenko [this message]
2021-03-08 13:00 ` Bartosz Golaszewski
2021-03-15 9:01 ` Bartosz Golaszewski
2021-03-15 10:16 ` Andy Shevchenko
2021-03-15 12:50 ` Andy Shevchenko
2021-03-15 14:04 ` Bartosz Golaszewski
2021-03-15 14:34 ` Andy Shevchenko
2021-03-15 16:47 ` Bartosz Golaszewski
2021-03-15 17:04 ` Andy Shevchenko
2021-04-10 0:45 ` Marek Vasut
2021-04-10 9:06 ` Bartosz Golaszewski
2021-04-10 13:18 ` Marek Vasut
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YEYOQqFch8yTE2SZ@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bgolaszewski@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=rguskov@dh-electronics.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox