From: Francesco Dolcini <francesco@dolcini.it>
To: Judith Mendez <jm@ti.com>
Cc: Tom Rini <trini@konsulko.com>, Simon Glass <sjg@chromium.org>,
Francois Berder <fberder@outlook.fr>,
u-boot@lists.denx.de
Subject: Re: [PATCH] gpio: pca953x: Add GPIO settle delay
Date: Mon, 13 Jul 2026 09:07:52 +0200 [thread overview]
Message-ID: <20260713070752.GC13102@francesco-nb> (raw)
In-Reply-To: <20260710230409.147210-1-jm@ti.com>
Hello Judith,
On Fri, Jul 10, 2026 at 06:04:09PM -0500, Judith Mendez wrote:
> Some board designs have slow RC circuits on GPIO outputs controlled by
> PCA953X I2C expanders. On some board designs, pin voltage transitions
> can take significant time after I2C write command completes.
>
> Add an optional "gpio-settle-delay-ms" device tree property for the
> pca953x driver to add a delay after I2C write if specified, allowing to
> compensate for slow RC circuits.
>
> Signed-off-by: Judith Mendez <jm@ti.com>
> ---
> drivers/gpio/pca953x_gpio.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/gpio/pca953x_gpio.c b/drivers/gpio/pca953x_gpio.c
> index 965a5fcf30b..54b957069c9 100644
> --- a/drivers/gpio/pca953x_gpio.c
> +++ b/drivers/gpio/pca953x_gpio.c
> @@ -333,6 +339,8 @@ static int pca953x_probe(struct udevice *dev)
>
> info->bank_count = DIV_ROUND_UP(info->gpio_count, BANK_SZ);
>
> + info->settle_delay_ms = dev_read_u32_default(dev, "gpio-settle-delay-ms", 0);
Is this property supported also in Linux and defined in the Linux
binding? I do not think we should have U-Boot specific DT properties.
Francesco
next prev parent reply other threads:[~2026-07-13 7:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 23:04 [PATCH] gpio: pca953x: Add GPIO settle delay Judith Mendez
2026-07-13 7:07 ` Francesco Dolcini [this message]
2026-07-13 20:48 ` Mendez, Judith
2026-07-13 12:00 ` Kathpalia, Tanmay
2026-07-13 20:49 ` Mendez, Judith
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=20260713070752.GC13102@francesco-nb \
--to=francesco@dolcini.it \
--cc=fberder@outlook.fr \
--cc=jm@ti.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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.