All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Sai Kumar Cholleti <skmr537@gmail.com>
Cc: bgolaszewski@baylibre.com, linux-gpio@vger.kernel.org,
	mmcclain@noprivs.com, stable@vger.kernel.org
Subject: Re: [PATCH v2] gpio: exar: set value when external pull-up or pull-down is present
Date: Mon, 4 Nov 2024 20:56:27 +0200	[thread overview]
Message-ID: <ZykY251SaLeksh9T@smile.fi.intel.com> (raw)
In-Reply-To: <20241104154757.2306076-1-skmr537@gmail.com>

On Mon, Nov 04, 2024 at 09:17:57PM +0530, Sai Kumar Cholleti wrote:
> Setting GPIO direction = high, sometimes results in GPIO value = 0.
> 
> If a GPIO is pulled high, the following construction results in the
> value being 0 when the desired value is 1:
> 
> $ echo "high" > /sys/class/gpio/gpio336/direction
> $ cat /sys/class/gpio/gpio336/value
> 0
> 
> Before the GPIO direction is changed from an input to an output,
> exar_set_value() is called with value = 1, but since the GPIO is an
> input when exar_set_value() is called, _regmap_update_bits() reads a 1
> due to an external pull-up.  regmap_set_bits() sets force_write =
> false, so the value (1) is not written.  When the direction is then
> changed, the GPIO becomes an output with the value of 0 (the hardware
> default).
> 
> regmap_write_bits() sets force_write = true, so the value is always
> written by exar_set_value() and an external pull-up doesn't affect the
> outcome of setting direction = high.
> 
> 
> The same can happen when a GPIO is pulled low, but the scenario is a
> little more complicated.
> 

> $ echo high > /sys/class/gpio/gpio351/direction 

This...

> $ cat /sys/class/gpio/gpio351/value
> 1
> 
> $ echo in > /sys/class/gpio/gpio351/direction 

...this...

> $ cat /sys/class/gpio/gpio351/value
> 0
> 
> $ echo low > /sys/class/gpio/gpio351/direction 

...this...

> $ cat /sys/class/gpio/gpio351/value
> 1

> Fixes: 36fb7218e878 ("gpio: exar: switch to using regmap") 

...and this lines have a trailing space.

> Signed-off-by: Sai Kumar Cholleti <skmr537@gmail.com>
> Signed-off-by: Matthew McClain <mmcclain@noprivs.com>

Hmm... Missing Co-developed-by?
This SoB chain puzzles me a bit, the committer should go last AFAIR.

...

> +	/*
> +	 * regmap_write_bits forces value to be written when an external

regmap_write_bits()


> +	 * pull up/down might otherwise indicate value was already set

Missing period at the end.

> +	 */

...

Other than above LGTM.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2024-11-04 18:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-30 13:46 [PATCH] gpio: exar set value handling for hw with gpio pull-up or pull-down Sai Kumar Cholleti
2024-08-01 15:18 ` Matthew McClain
2024-08-12 17:22 ` Andy Shevchenko
2024-08-13 15:07   ` Matthew McClain
2024-11-04 13:25     ` Andy Shevchenko
2024-11-04 15:47       ` [PATCH v2] gpio: exar: set value when external pull-up or pull-down is present Sai Kumar Cholleti
2024-11-04 18:56         ` Andy Shevchenko [this message]
2024-11-05  7:15           ` [PATCH v3] " Sai Kumar Cholleti
2024-11-05 14:39             ` Andy Shevchenko
2024-11-12 15:30               ` Andy Shevchenko
2024-11-18 11:00                 ` Bartosz Golaszewski
2024-11-18 12:34                   ` Andy Shevchenko
2024-11-19 13:50                     ` sai kumar
2024-11-21  8:10             ` Bartosz Golaszewski
  -- strict thread matches above, loose matches on Subject: below --
2024-11-04 15:18 [PATCH v2] " Sai Kumar Cholleti

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=ZykY251SaLeksh9T@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=mmcclain@noprivs.com \
    --cc=skmr537@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.