linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Christophe Leroy <christophe.leroy@c-s.fr>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] gpio: fix "gpio-line-names" property retrieval
Date: Fri, 15 Dec 2017 11:44:03 +0200	[thread overview]
Message-ID: <20171215094403.GR22431@lahna.fi.intel.com> (raw)
In-Reply-To: <20171215080915.DDA106C974@localhost.localdomain>

On Fri, Dec 15, 2017 at 09:09:15AM +0100, Christophe Leroy wrote:
> Following commit 9427ecbed46cc ("gpio: Rework of_gpiochip_set_names()
> to use device property accessors"), "gpio-line-names" DT property is
> not retrieved anymore when chip->parent is not set by the driver.

Thanks for taking care of this and sorry about the breakage.

I think this changelog should have few more words about the reason it
started to fail.

> This patch fixes that.
> 
> Fixes: 9427ecbed46cc ("gpio: Rework of_gpiochip_set_names()
> to use device property accessors")

Don't wrap the Fixes line.

> Cc: stable@vger.kernel.org
> Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>
> ---
>  drivers/gpio/gpiolib-devprop.c | 16 ++++++++++------
>  1 file changed, 10 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/gpio/gpiolib-devprop.c b/drivers/gpio/gpiolib-devprop.c
> index 27f383bda7d9..310dbc451a85 100644
> --- a/drivers/gpio/gpiolib-devprop.c
> +++ b/drivers/gpio/gpiolib-devprop.c
> @@ -30,20 +30,24 @@ void devprop_gpiochip_set_names(struct gpio_chip *chip)
>  	struct gpio_device *gdev = chip->gpiodev;
>  	const char **names;
>  	int ret, i;
> +	struct device *dev;
>  
> -	if (!chip->parent) {
> +	if (chip->parent) {
> +		dev = chip->parent;
> +	} else if (gdev->dev.of_node) {
> +		dev = &gdev->dev;
> +	} else {

I wonder if it would be better to change devprop_gpiochip_set_names()
take struct fwnode_handle as second parameter and use that instead of
chip->parent below? The reason why this happens now is that not all DT
enabled drivers seem to set chip->parent (which I guess is pretty valid
thing to do) but they still set of_node accordingly.

>  		dev_warn(&gdev->dev, "GPIO chip parent is NULL\n");
>  		return;
>  	}
>  
> -	ret = device_property_read_string_array(chip->parent, "gpio-line-names",
> +	ret = device_property_read_string_array(dev, "gpio-line-names",
>  						NULL, 0);
>  	if (ret < 0)
>  		return;
>  
>  	if (ret != gdev->ngpio) {
> -		dev_warn(chip->parent,
> -			 "names %d do not match number of GPIOs %d\n", ret,
> +		dev_warn(dev, "names %d do not match number of GPIOs %d\n", ret,
>  			 gdev->ngpio);
>  		return;
>  	}
> @@ -52,10 +56,10 @@ void devprop_gpiochip_set_names(struct gpio_chip *chip)
>  	if (!names)
>  		return;
>  
> -	ret = device_property_read_string_array(chip->parent, "gpio-line-names",
> +	ret = device_property_read_string_array(dev, "gpio-line-names",
>  						names, gdev->ngpio);
>  	if (ret < 0) {
> -		dev_warn(chip->parent, "failed to read GPIO line names\n");
> +		dev_warn(dev, "failed to read GPIO line names\n");
>  		kfree(names);
>  		return;
>  	}
> -- 
> 2.13.3

      reply	other threads:[~2017-12-15  9:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-15  8:09 [PATCH] gpio: fix "gpio-line-names" property retrieval Christophe Leroy
2017-12-15  9:44 ` Mika Westerberg [this message]

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=20171215094403.GR22431@lahna.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=christophe.leroy@c-s.fr \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /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).