From: Dinh Nguyen <dinguyen@kernel.org>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: andriy.shevchenko@linux.intel.com,
mika.westerberg@linux.intel.com, robh+dt@kernel.org,
krzk+dt@kernel.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCHv5 1/2] i2c: designware: introduce a custom scl recovery for SoCFPGA platforms
Date: Mon, 20 Jun 2022 17:41:01 -0500 [thread overview]
Message-ID: <b4fb0c7f-2fd9-35ff-1d09-8940e3b66455@kernel.org> (raw)
In-Reply-To: <f8647bec-eca7-b318-4f79-bc4bae721004@linux.intel.com>
On 6/17/22 07:59, Jarkko Nikula wrote:
> Hi
>
> On 6/16/22 17:12, Dinh Nguyen wrote:
>> The I2C pins on the SoCFPGA platforms do not go through a GPIO module,
>> thus cannot be recovered by the default method of by doing a GPIO access.
>> Only a reset of the I2C IP block can a recovery be successful.
>>
> One thing what is unclear to me how does this release the I2C slave that
> potentially keeps the SDA stuck low. Does platform specific reset
> sequence send 9 SCL pulses, toggle HW reset of the clients or cycle
> power of them?
>
> If recovery is only controller point of view then worth to emphasis it
> in the commit log and perhaps add a comment too into
> i2c_socfpga_scl_recovery(). Some might hit an issue that I2C client is
> stuck and wonder why recovery won't work.
The recovery is only resetting the controller itself and not the client.
I'll add a comment in v6 to highlight this.
>
>> The assignment of the recover_bus needs to get done before the call to
>> devm_gpiod_get_optional(), otherwise, the assignment is not taking place
>> because of an error after returning from devm_gpiod_get_optional().
>>
> This sentence no longer true after v3?
Correct...will update.
Dinh
prev parent reply other threads:[~2022-06-20 22:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 14:12 [PATCHv5 1/2] i2c: designware: introduce a custom scl recovery for SoCFPGA platforms Dinh Nguyen
2022-06-16 14:12 ` [PATCHv5 2/2] dt-bindings: i2c: dw: Add Intel's SoCFPGA I2C controller Dinh Nguyen
2022-06-17 12:59 ` [PATCHv5 1/2] i2c: designware: introduce a custom scl recovery for SoCFPGA platforms Jarkko Nikula
2022-06-20 22:41 ` Dinh Nguyen [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=b4fb0c7f-2fd9-35ff-1d09-8940e3b66455@kernel.org \
--to=dinguyen@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=jarkko.nikula@linux.intel.com \
--cc=krzk+dt@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=robh+dt@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).