From: Dmitry Osipenko <digetx@gmail.com>
To: Sowjanya Komatineni <skomatineni@nvidia.com>,
thierry.reding@gmail.com, jonathanh@nvidia.com,
mkarthik@nvidia.com, smohammed@nvidia.com, talho@nvidia.com
Cc: linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH V9 2/5] i2c: tegra: add bus clear master support
Date: Fri, 1 Feb 2019 22:06:39 +0300 [thread overview]
Message-ID: <f74879c3-4cbe-d59e-ee57-3ebe5bb0a269@gmail.com> (raw)
In-Reply-To: <1549040867-18149-2-git-send-email-skomatineni@nvidia.com>
01.02.2019 20:07, Sowjanya Komatineni пишет:
> Bus clear feature of Tegra I2C controller helps to recover from
> bus hang when I2C master loses the bus arbitration due to the
> slave device holding SDA LOW continuously for some unknown reasons.
>
> Per I2C specification, the device that held the bus LOW should
> release it within 9 clock pulses.
>
> During bus clear operation, Tegra I2C controller sends 9 clock
> pulses and terminates the transaction with STOP condition.
> Upon successful bus clear operation, bus goes to idle state and
> driver retries the transaction.
>
> Signed-off-by: Sowjanya Komatineni <skomatineni@nvidia.com>
> Acked-by: Thierry Reding <treding@nvidia.com>
> ---
> [V9] : Rebased to 5.0-rc4
> [V5/V6/V7/V8]: Same as V4
> [V4]: Added I2C Bus Clear support patch to this version of series.
>
> drivers/i2c/busses/i2c-tegra.c | 73 ++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 73 insertions(+)
Reviewed-by: Dmitry Osipenko <digetx@gmail.com>
next prev parent reply other threads:[~2019-02-01 19:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 17:07 [PATCH V9 1/5] i2c: tegra: sort all the include headers alphabetically Sowjanya Komatineni
2019-02-01 17:07 ` [PATCH V9 2/5] i2c: tegra: add bus clear master support Sowjanya Komatineni
2019-02-01 19:06 ` Dmitry Osipenko [this message]
2019-02-01 17:07 ` [PATCH V9 3/5] i2c: tegra: Add DMA support Sowjanya Komatineni
2019-02-01 18:57 ` Dmitry Osipenko
2019-02-01 19:20 ` Sowjanya Komatineni
2019-02-01 19:22 ` Dmitry Osipenko
2019-02-02 14:13 ` Dmitry Osipenko
2019-02-02 18:43 ` Sowjanya Komatineni
2019-02-03 16:42 ` Dmitry Osipenko
2019-02-01 20:21 ` Sowjanya Komatineni
2019-02-01 20:30 ` Dmitry Osipenko
2019-02-01 21:36 ` Sowjanya Komatineni
2019-02-01 21:45 ` Dmitry Osipenko
2019-02-02 14:01 ` Dmitry Osipenko
2019-02-02 18:32 ` Sowjanya Komatineni
2019-02-03 16:48 ` Dmitry Osipenko
2019-02-04 8:18 ` Thierry Reding
2019-02-03 14:19 ` Dmitry Osipenko
2019-02-03 14:47 ` Dmitry Osipenko
2019-02-03 15:27 ` Dmitry Osipenko
2019-02-04 12:57 ` Dmitry Osipenko
2019-02-05 1:37 ` Sowjanya Komatineni
2019-02-05 6:20 ` Dmitry Osipenko
2019-02-04 8:04 ` Thierry Reding
2019-02-01 17:07 ` [PATCH V9 4/5] i2c: tegra: update transfer timeout Sowjanya Komatineni
2019-02-01 19:16 ` Dmitry Osipenko
2019-02-01 19:37 ` Sowjanya Komatineni
2019-02-01 19:41 ` Dmitry Osipenko
2019-02-04 7:54 ` Thierry Reding
2019-02-01 17:07 ` [PATCH V9 5/5] i2c: tegra: add i2c interface timing support Sowjanya Komatineni
2019-02-01 19:05 ` [PATCH V9 1/5] i2c: tegra: sort all the include headers alphabetically Dmitry Osipenko
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=f74879c3-4cbe-d59e-ee57-3ebe5bb0a269@gmail.com \
--to=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mkarthik@nvidia.com \
--cc=skomatineni@nvidia.com \
--cc=smohammed@nvidia.com \
--cc=talho@nvidia.com \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).