From: Dinh Nguyen <dinguyen@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: jarkko.nikula@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: [PATCHv2 1/2] i2c: designware: introduce a custom scl recovery for SoCFPGA platforms
Date: Thu, 26 May 2022 14:08:55 -0500 [thread overview]
Message-ID: <3dafa370-cd77-e3ba-a48b-2ca3674432ab@kernel.org> (raw)
In-Reply-To: <Yo0LKQchQwitJVHm@smile.fi.intel.com>
On 5/24/22 11:43, Andy Shevchenko wrote:
> On Tue, May 24, 2022 at 08:54:40AM -0500, 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.
>
> Better now, but see my additional comments.
>
> ...
>
>> + switch (dev->flags & MODEL_MASK) {
>> + case MODEL_SOCFPGA:
>> + rinfo->recover_bus = i2c_socfpga_scl_recovery;
>> + break;
>> + default:
>> + rinfo->recover_bus = i2c_generic_scl_recovery;
>> + break;
>> + }
>
>> + adap->bus_recovery_info = rinfo;
>
> Usually we do not assign the pointer while data structure is incomplete.
> That's said, please leave this line as it was.
>
> On top of that, why you can't move the above switch to the place where old
> function was assigned?
>
I have to put the switch statement before the call to
devm_gpiod_get_optional(), otherwise the recover_bus function pointer
will not get set.
Dinh
next prev parent reply other threads:[~2022-05-26 19:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 13:54 [PATCHv2 1/2] i2c: designware: introduce a custom scl recovery for SoCFPGA platforms Dinh Nguyen
2022-05-24 13:54 ` [PATCHv2 2/2] dt-bindings: i2c: dw: Add Intel's SoCFPGA I2C controller Dinh Nguyen
2022-05-24 16:43 ` [PATCHv2 1/2] i2c: designware: introduce a custom scl recovery for SoCFPGA platforms Andy Shevchenko
2022-05-26 19:08 ` Dinh Nguyen [this message]
2022-06-01 13:48 ` Dinh Nguyen
2022-06-10 11:36 ` Andy Shevchenko
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=3dafa370-cd77-e3ba-a48b-2ca3674432ab@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 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.