linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Longerbeam <slongerbeam@gmail.com>
To: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>,
	linus.walleij@linaro.org, gnurou@gmail.com, robh+dt@kernel.org,
	mark.rutland@arm.com
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Steve Longerbeam <steve_longerbeam@mentor.com>
Subject: Re: [PATCH] gpio: pca953x: Add optional reset gpio control
Date: Tue, 10 Jan 2017 11:13:11 -0800	[thread overview]
Message-ID: <1b85a1aa-4382-03d0-7920-4f1fdfcbda76@gmail.com> (raw)
In-Reply-To: <e043cb00-9b8e-edec-0949-b23fbed6e2c5@mentor.com>



On 01/04/2017 02:25 AM, Vladimir Zapolskiy wrote:
> Hi Steve,
>
> On 01/02/2017 11:07 PM, Steve Longerbeam wrote:
>> Add optional reset-gpios pin control. If present, de-assert the
>> specified reset gpio pin to bring the chip out of reset.
>>
>> Signed-off-by: Steve Longerbeam <steve_longerbeam@mentor.com>
>> Cc: Linus Walleij <linus.walleij@linaro.org>
>> Cc: Alexandre Courbot <gnurou@gmail.com>
>> Cc: linux-gpio@vger.kernel.org
>> Cc: linux-kernel@vger.kernel.org
>> ---
>>   Documentation/devicetree/bindings/gpio/gpio-pca953x.txt |  4 ++++
>>   drivers/gpio/gpio-pca953x.c                             | 11 +++++++++++
>>   2 files changed, 15 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/gpio/gpio-pca953x.txt b/Documentation/devicetree/bindings/gpio/gpio-pca953x.txt
>> index 08dd15f..da54f4c 100644
>> --- a/Documentation/devicetree/bindings/gpio/gpio-pca953x.txt
>> +++ b/Documentation/devicetree/bindings/gpio/gpio-pca953x.txt
>> @@ -29,6 +29,10 @@ Required properties:
>>   	onsemi,pca9654
>>   	exar,xra1202
>>   
>> +Optional properties:
>> + - reset-gpios: GPIO specification for the RESET input
>> +
>> +
> Drop the surplus empty line above.

done.

>
>>   Example:
>>   
>>   
>> diff --git a/drivers/gpio/gpio-pca953x.c b/drivers/gpio/gpio-pca953x.c
>> index d5d72d8..ca2ddea 100644
>> --- a/drivers/gpio/gpio-pca953x.c
>> +++ b/drivers/gpio/gpio-pca953x.c
>> @@ -22,6 +22,7 @@
>>   #include <linux/of_platform.h>
>>   #include <linux/acpi.h>
>>   #include <linux/regulator/consumer.h>
>> +#include <linux/gpio/consumer.h>
>>   
>>   #define PCA953X_INPUT		0
>>   #define PCA953X_OUTPUT		1
>> @@ -754,8 +755,18 @@ static int pca953x_probe(struct i2c_client *client,
>>   		invert = pdata->invert;
>>   		chip->names = pdata->names;
>>   	} else {
>> +		struct gpio_desc *reset_gpio;
>> +
>>   		chip->gpio_start = -1;
>>   		irq_base = 0;
>> +
>> +		/* see if we need to de-assert a reset pin */
>> +		reset_gpio = devm_gpiod_get_optional(&client->dev, "reset",
>> +						     GPIOD_OUT_LOW);
>> +		if (IS_ERR(reset_gpio)) {
>> +			dev_err(&client->dev, "request for reset pin failed\n");
> I'm not confident that the error message is wanted here, you may consider either
> to remove it or at least print it out if (PTR_ERR(reset_gpio) != -EPROBE_DEFER).

no problem, I just removed it.


Steve

  reply	other threads:[~2017-01-10 19:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-02 21:07 [PATCH] pca953x: Add optional reset gpio control Steve Longerbeam
2017-01-02 21:07 ` [PATCH] gpio: " Steve Longerbeam
2017-01-03 23:37   ` Andy Shevchenko
     [not found]     ` <CAHp75VeCKPy4B51P_N9Bp03zPUbRodKzitc-n16ZRKJWcEF4fA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-04 10:20       ` Vladimir Zapolskiy
     [not found]         ` <7bfce806-7670-0bf3-bdf2-00aaf68b5b11-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
2017-01-04 10:31           ` Andy Shevchenko
2017-01-10 19:10             ` Steve Longerbeam
2017-01-10 18:57       ` Steve Longerbeam
     [not found]   ` <1483391271-17304-2-git-send-email-steve_longerbeam-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
2017-01-04 10:25     ` Vladimir Zapolskiy
2017-01-10 19:13       ` Steve Longerbeam [this message]
2017-01-04 13:22   ` Rob Herring
2017-01-10 19:21     ` Steve Longerbeam

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=1b85a1aa-4382-03d0-7920-4f1fdfcbda76@gmail.com \
    --to=slongerbeam@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gnurou@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=steve_longerbeam@mentor.com \
    --cc=vladimir_zapolskiy@mentor.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).