Linux I2C development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Eddie James <eajames@linux.ibm.com>,
	Chris Packham <chris.packham@alliedtelesis.co.nz>,
	peda@axentia.se, p.zabel@pengutronix.de
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: muxes: pca954x: Allow sharing reset GPIO
Date: Fri, 7 Jun 2024 08:46:10 +0200	[thread overview]
Message-ID: <31a9060a-aef3-4b1a-8db8-ada5e57833cc@linaro.org> (raw)
In-Reply-To: <a8f8aefa-9013-4ede-adce-0f585d3e528f@linux.ibm.com>

On 06/06/2024 23:58, Eddie James wrote:
> 
> On 3/10/24 23:14, Chris Packham wrote:
>> Some hardware designs with multiple PCA954x devices use a reset GPIO
>> connected to all the muxes. Support this configuration by making use of
>> the reset controller framework which can deal with the shared reset
>> GPIOs. Fall back to the old GPIO descriptor method if the reset
>> controller framework is not enabled.
> 
> 
> Hello Chris, Krzysztof,
> 
> 
> This change makes it so that the reset subsystem reset doesn't behave in 
> the same way as the fallback gpio reset. The gpio, as part of acquiring 
> it, gets set high, and then set low in the mux driver. So, the device 
> reset is toggled. In the case of the reset subsystem option, the reset 
> is only de-asserted (so the device is taken out of reset).
> 
> 
> I'm interested in preserving the previous behavior but with the shared 
> reset line. This can't be done just by doing "assert" first because the 
> shared reset subsystem doesn't allow that. So the reset-gpio driver 
> would have to implement the reset operation - no problem. However, how 
> to specify the wait time for the reset-gpio driver here? Something like 
> the simple reset driver maybe? Or a function call from the reset 
> consumer driver to specify the wait time for that reset?

You can check my slides from EOSS/OSSNA this year:
https://ossna2024.sched.com/event/1aPvr?iframe=no
maybe links to original work will help you.

Best regards,
Krzysztof


  reply	other threads:[~2024-06-07  6:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11  4:14 [PATCH] i2c: muxes: pca954x: Allow sharing reset GPIO Chris Packham
2024-03-11  6:25 ` Krzysztof Kozlowski
2024-03-11 20:07   ` Chris Packham
2024-06-06 21:58 ` Eddie James
2024-06-07  6:46   ` Krzysztof Kozlowski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-08  4:19 Chris Packham
2024-01-11  8:53 ` Krzysztof Kozlowski
2024-01-11  9:27 ` Peter Rosin

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=31a9060a-aef3-4b1a-8db8-ada5e57833cc@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=chris.packham@alliedtelesis.co.nz \
    --cc=eajames@linux.ibm.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=peda@axentia.se \
    /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