From: Thierry Reding <thierry.reding@gmail.com>
To: Sowjanya Komatineni <skomatineni@nvidia.com>
Cc: Jonathan Hunter <jonathanh@nvidia.com>,
Timo Alho <talho@nvidia.com>,
"wsa@the-dreams.de" <wsa@the-dreams.de>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH V1] i2c: tegra: fix tegra186 hw supported features
Date: Mon, 18 Feb 2019 17:28:24 +0100 [thread overview]
Message-ID: <20190218162824.GA11872@ulmo> (raw)
In-Reply-To: <BYAPR12MB3398E17BB92CC0D33996FBD4C2630@BYAPR12MB3398.namprd12.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2503 bytes --]
On Mon, Feb 18, 2019 at 04:13:46PM +0000, Sowjanya Komatineni wrote:
> > >
> > > On 18/02/2019 08:42, Thierry Reding wrote:
> > > > On Sat, Feb 16, 2019 at 08:33:07AM -0800, Sowjanya Komatineni wrote:
> > > >> Tegra186 does not support multi-master mode and also there is no
> > > >> master fifo control register.
> > > >>
> > > >> This patch fixes supported features of Tegra186 and prevents
> > > >> crashing during boot as master fifo control register are not
> > > >> present on Tegra186 and prior.
> > > >>
> > > >> Signed-off-by: Sowjanya Komatineni <skomatineni@nvidia.com>
> > > >> ---
> > > >> drivers/i2c/busses/i2c-tegra.c | 4 ++--
> > > >> 1 file changed, 2 insertions(+), 2 deletions(-)
> > > >
> > > > We really should've caught this earlier. Jon, let's think about ways
> > > > to make it easier to catch these things in the future on our test system.
> > >
> > > Indeed. This has fixed the boot regression I was seeing over the
> > > weekend on -next for Tegra186. However, I am bit confused here,
> > > because when I look at the Tegra186 TRM it states that the I2C
> > > supports multi-master mode which disagrees with this patch.
> > > Furthermore, it seems odd that
> > > Tegra210 and Tegra194 would support multi-master mode but Tegra186
> > > does not. So is this really correct?
> > >
> > > I would expect at least the missing master FIFO registers to cause a crash on Tegra186. The internal architecture specification also says that multi-master is supported.
> > >
> > > Sowjanya: do you have other documents that suggest we don't support multi-master on Tegra186 specifically? Or is this to work around an issue specific to Tegra186?
> > >
> > > As it is this contradicts documentation, so we need to either fix the commit to remove only master FIFO support or we need to fix the docs to reflect reality.
> > >
> > > Thierry
>
> Thierry/Jonathan,
>
> Design wise we support but due to known hw bugs we defeatured
> multi-master mode. TRM docs also says no multi master support for
> T210, T186 and multi-master is supported only on T194.
>
> T210 also has multi master enabled in driver. We should disable that
> also.
Okay, I think it makes sense to split this into two patches:
1) remove master FIFO support on Tegra186 because that leads to a
crash
2) remove multi-master support on Tegra210 and Tegra186 with a commit
message that explains that it was defeatured because of known bugs
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-02-18 16:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-16 16:33 [PATCH V1] i2c: tegra: fix tegra186 hw supported features Sowjanya Komatineni
2019-02-16 16:33 ` Sowjanya Komatineni
2019-02-18 8:42 ` Thierry Reding
2019-02-18 9:34 ` Jon Hunter
2019-02-18 9:34 ` Jon Hunter
2019-02-18 14:50 ` Thierry Reding
2019-02-18 16:13 ` Sowjanya Komatineni
2019-02-18 16:28 ` Thierry Reding [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=20190218162824.GA11872@ulmo \
--to=thierry.reding@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=skomatineni@nvidia.com \
--cc=talho@nvidia.com \
--cc=wsa@the-dreams.de \
/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.