From: Michal Simek <michal.simek@amd.com>
To: "Datta, Shubhrajyoti" <shubhrajyoti.datta@amd.com>,
Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Cc: "michal.simek@xilinx.com" <michal.simek@xilinx.com>,
"git-dev (AMD-Xilinx)" <git-dev@amd.com>,
Chirag Parekh <chiragp@xilinx.com>,
"Robert Hancock" <robert.hancock@calian.com>
Subject: Re: [PATCH v3] i2c: cadence: Add standard bus recovery support
Date: Fri, 29 Jul 2022 13:17:51 +0200 [thread overview]
Message-ID: <407919d2-c3e3-68e1-30d5-2d2db00db0dd@amd.com> (raw)
In-Reply-To: <BY5PR12MB49024F4C35287AF1D66EF4A181999@BY5PR12MB4902.namprd12.prod.outlook.com>
On 7/29/22 13:05, Datta, Shubhrajyoti wrote:
> [AMD Official Use Only - General]
>
>
>
>> -----Original Message-----
>> From: Simek, Michal <michal.simek@amd.com>
>> Sent: Friday, July 29, 2022 4:26 PM
>> To: Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com>; linux-
>> i2c@vger.kernel.org
>> Cc: michal.simek@xilinx.com; git-dev (AMD-Xilinx) <git-dev@amd.com>;
>> Chirag Parekh <chiragp@xilinx.com>; Robert Hancock
>> <robert.hancock@calian.com>
>> Subject: Re: [PATCH v3] i2c: cadence: Add standard bus recovery support
>>
>>
>>
>> On 7/28/22 07:51, Shubhrajyoti Datta wrote:
>>> Hook up the standard GPIO/pinctrl-based recovery support.
>>> We are doing the recovery at the beginning on a timeout.
>>>
>>> Multiple people have contributed to the series.
>>> Original patch from Cirag and another one from Robert.
>>>
>>> Cc: Chirag Parekh <chiragp@xilinx.com>
>>> Cc: Robert Hancock <robert.hancock@calian.com>
>>> Signed-off-by: Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com>
>>> ---
>>> v2:
>>> Updated the busbusy check on a timeout
>>> v3:
>>> Added pinctrl_get
>>>
>>> Did unit testing and probed the scl to see the clock pulses.
>>
>> Can you please describe testing procedure? What board did you use?
>> What was the hardware configuration?
>
>
> Tested on zcu102 . and then I called the recovery in send setup .
> Also I had added the prints in the
> To confirm that the core was calling the zynqmp pinctrl to set pin mux.
>
> The scl line was Probed. I could see the clock cycles in the scl line.
>
> [ 84.286340] zynqmp-pinctrl firmware:zynqmp-firmware:pinctrl: set mux for pin 14
> [ 84.293779] zynqmp-pinctrl firmware:zynqmp-firmware:pinctrl: set mux for pin 15
> [ 84.301266] i2c-core: set_scl_gpio_value 164 1
> [ 84.305807] i2c i2c-0: SCL is set_scl 1 i ia 1
> [ 84.310331] i2c-core: get_scl_gpio_value 158
> [ 84.314681] i2c-core: set_scl_gpio_value 164 0
> [ 84.322519] i2c i2c-0: SCL is set_scl 0
> [ 84.326439] i2c i2c-0: SCL is set_scl 0 i ia 2
> [ 84.330965] i2c-core: set_scl_gpio_value 164 1
> [ 84.335496] i2c i2c-0: SCL is set_scl 1
> [ 84.339418] i2c i2c-0: SCL is set_scl 1 i ia 3
> [ 84.343947] i2c-core: get_scl_gpio_value 158
> [ 84.348302] i2c-core: set_scl_gpio_value 164 0
> [ 84.356135] i2c i2c-0: SCL is set_scl 0
> [ 84.360059] i2c i2c-0: SCL is set_scl 0 i ia 4
> [ 84.364586] i2c-core: set_scl_gpio_value 164 1
> [ 84.369117] i2c i2c-0: SCL is set_scl 1
> [ 84.373037] i2c i2c-0: SCL is set_scl 1 i ia 5
> [ 84.377564] i2c-core: get_scl_gpio_value 158
> [ 84.381914] i2c-core: set_scl_gpio_value 164 0
ok. Thanks.
Acked-by: Michal Simek <michal.simek@amd.com>
Thanks,
Michal
next prev parent reply other threads:[~2022-07-29 11:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 5:51 [PATCH v3] i2c: cadence: Add standard bus recovery support Shubhrajyoti Datta
2022-07-29 10:56 ` Michal Simek
2022-07-29 11:05 ` Datta, Shubhrajyoti
2022-07-29 11:17 ` Michal Simek [this message]
2022-09-27 7:06 ` Michal Simek
2022-09-27 20:32 ` Wolfram Sang
2022-09-27 20:35 ` Wolfram Sang
2022-09-29 7:29 ` Michal Simek
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=407919d2-c3e3-68e1-30d5-2d2db00db0dd@amd.com \
--to=michal.simek@amd.com \
--cc=chiragp@xilinx.com \
--cc=git-dev@amd.com \
--cc=linux-i2c@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=robert.hancock@calian.com \
--cc=shubhrajyoti.datta@amd.com \
--cc=shubhrajyoti.datta@xilinx.com \
/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