linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: fcooper@ti.com
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH] Input: edt-ft5x06 - Only call desc_to_gpio for valid gpios
Date: Tue, 6 Oct 2015 15:41:32 -0700	[thread overview]
Message-ID: <20151006224132.GC31850@dtor-ws> (raw)
In-Reply-To: <1444168187-3542-1-git-send-email-fcooper@ti.com>

Hi Franklin,

On Tue, Oct 06, 2015 at 04:49:47PM -0500, fcooper@ti.com wrote:
> From: Franklin S Cooper Jr <fcooper@ti.com>
> 
> Since reset and wake pin are optional the gpio structure for those
> pins may be null. Therefore, they can't be blindly passed to
> desc_to_gpio.
> 
> Only use desc_to_gpio for valid gpios.
> 
> This issue was detected by Smatch
> http://permalink.gmane.org/gmane.linux.kernel.input/45927
> 
> Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com>
> ---
> This patch is based on top of the following patchset which already
> is already in linux-next:
> https://patchwork.kernel.org/patch/7166931/
> 
>  drivers/input/touchscreen/edt-ft5x06.c | 9 ++++++---
>  1 file changed, 6 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/input/touchscreen/edt-ft5x06.c b/drivers/input/touchscreen/edt-ft5x06.c
> index 7239c31..f877404 100644
> --- a/drivers/input/touchscreen/edt-ft5x06.c
> +++ b/drivers/input/touchscreen/edt-ft5x06.c
> @@ -876,11 +876,13 @@ static int edt_ft5x06_ts_probe(struct i2c_client *client,
>  	struct edt_ft5x06_ts_data *tsdata;
>  	struct input_dev *input;
>  	unsigned long irq_flags;
> -	int error;
> +	int error, reset_pin, wake_pin;
>  	char fw_version[EDT_NAME_LEN];
>  
>  	dev_dbg(&client->dev, "probing for EDT FT5x06 I2C\n");
>  
> +	reset_pin = wake_pin = -1;
> +
>  	tsdata = devm_kzalloc(&client->dev, sizeof(*tsdata), GFP_KERNEL);
>  	if (!tsdata) {
>  		dev_err(&client->dev, "failed to allocate driver data.\n");
> @@ -908,12 +910,14 @@ static int edt_ft5x06_ts_probe(struct i2c_client *client,
>  	if (tsdata->wake_gpio) {
>  		usleep_range(5000, 6000);
>  		gpiod_set_value_cansleep(tsdata->wake_gpio, 1);
> +		wake_pin = desc_to_gpio(tsdata->wake_gpio);
>  	}
>  
>  	if (tsdata->reset_gpio) {
>  		usleep_range(5000, 6000);
>  		gpiod_set_value_cansleep(tsdata->reset_gpio, 0);
>  		msleep(300);
> +		reset_pin = desc_to_gpio(tsdata->reset_gpio);
>  	}
>  
>  	input = devm_input_allocate_device(&client->dev);
> @@ -987,8 +991,7 @@ static int edt_ft5x06_ts_probe(struct i2c_client *client,
>  
>  	dev_dbg(&client->dev,
>  		"EDT FT5x06 initialized: IRQ %d, WAKE pin %d, Reset pin %d.\n",
> -		client->irq, desc_to_gpio(tsdata->wake_gpio),
> -		desc_to_gpio(tsdata->reset_gpio));
> +		client->irq, wake_pin, reset_pin);

I changed to use ternary operators in dev_dbg instead of temp variables
and applied.

Thanks.

-- 
Dmitry

      reply	other threads:[~2015-10-06 22:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-06 21:49 [PATCH] Input: edt-ft5x06 - Only call desc_to_gpio for valid gpios fcooper
2015-10-06 22:41 ` Dmitry Torokhov [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=20151006224132.GC31850@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=fcooper@ti.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@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).