From: Michal Simek <michal.simek@amd.com>
To: Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com>,
<linux-i2c@vger.kernel.org>
Cc: <michal.simek@xilinx.com>, <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 12:56:07 +0200 [thread overview]
Message-ID: <920041df-0ac2-7298-4568-c8bba4a2838c@amd.com> (raw)
In-Reply-To: <20220728055150.18368-1-shubhrajyoti.datta@xilinx.com>
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?
Thanks,
Michal
next prev parent reply other threads:[~2022-07-29 10:56 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 [this message]
2022-07-29 11:05 ` Datta, Shubhrajyoti
2022-07-29 11:17 ` Michal Simek
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=920041df-0ac2-7298-4568-c8bba4a2838c@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@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