linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	Roman Guskov <rguskov@dh-electronics.com>
Subject: Re: [PATCH v1 1/1] gpiolib: Read "gpio-line-names" from a firmware node
Date: Fri, 5 Mar 2021 13:26:45 +0100	[thread overview]
Message-ID: <2f567d44-4aaa-02f7-a60f-d6ad5404373a@denx.de> (raw)
In-Reply-To: <YEIjGcPF9yNnKdSp@smile.fi.intel.com>

On 3/5/21 1:24 PM, Andy Shevchenko wrote:
> On Fri, Mar 05, 2021 at 01:11:39PM +0100, Marek Vasut wrote:
>> On 3/5/21 1:02 PM, Andy Shevchenko 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.
>>>
>>> Fixes: 7cba1a4d5e162 ("gpiolib: generalize devprop_gpiochip_set_names() for device properties")
>>> Reported-by: Marek Vasut <marex@denx.de>
>>> Reported-by: Roman Guskov <rguskov@dh-electronics.com>
>>> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>>
>> Tested-by: Marek Vasut <marex@denx.de>
>> Reviewed-by: Marek Vasut <marex@denx.de>
> 
> Thanks!
> 
>> Thanks
>>
>>>    static int devprop_gpiochip_set_names(struct gpio_chip *chip)
>>>    {
>>>    	struct gpio_device *gdev = chip->gpiodev;
>>> -	struct device *dev = chip->parent;
>>> +	struct fwnode_handle *fwnode = dev_fwnode(&gdev->dev);
>>
>> You could make the order here a reverse xmas tree, but that's a nitpick.
> 
> They are dependent, can't be reordered.

Doh, you're right.

  reply	other threads:[~2021-03-05 12:27 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 [this message]
2021-03-07 13:55 ` Bartosz Golaszewski
2021-03-07 16:14   ` Andy Shevchenko
2021-03-08 11:45     ` Andy Shevchenko
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=2f567d44-4aaa-02f7-a60f-d6ad5404373a@denx.de \
    --to=marex@denx.de \
    --cc=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=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;
as well as URLs for NNTP newsgroup(s).