From: Jon Hunter <jonathanh@nvidia.com>
To: Akhil R <akhilrajeev@nvidia.com>,
andi.shyti@kernel.org, digetx@gmail.com,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org, thierry.reding@gmail.com,
wsa+renesas@sang-engineering.com, wsa@kernel.org
Cc: kkartik@nvidia.com, ldewangan@nvidia.com, smangipudi@nvidia.com
Subject: Re: [PATCH v12 4/6] i2c: tegra: Add HS mode support
Date: Tue, 18 Nov 2025 12:25:27 +0000 [thread overview]
Message-ID: <926d94d9-0719-4ade-910b-6042a2a8171b@nvidia.com> (raw)
In-Reply-To: <20251115042632.69708-5-akhilrajeev@nvidia.com>
On 15/11/2025 04:26, Akhil R wrote:
> Add support for HS (High Speed) mode transfers, which is supported by
> Tegra194 onwards. Also adjust the bus frequency such that it uses the
> fast plus mode when HS mode is not supported.
Technically, Tegra20 supported HS mode (according to the documentation).
However, from what I have found, it appears that HS mode only works on
Tegra194+ devices. So Thierry suggested that we document that HS is
broken on devices prior to Tegra194.
So the variable 'has_hs_mode_support' is a bit misleading. It might be
better to change this to 'hs_mode_broken' and reverse the logic.
Jon
--
nvpublic
next prev parent reply other threads:[~2025-11-18 12:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-15 4:26 [PATCH v12 0/6] Updates for Tegra264 and Tegra256 Akhil R
2025-11-15 4:26 ` [PATCH v12 1/6] i2c: tegra: Do not configure DMA if not supported Akhil R
2025-11-15 4:26 ` [PATCH v12 2/6] i2c: tegra: Use separate variables for fast and fastplus Akhil R
2025-11-17 9:51 ` Jon Hunter
2025-11-15 4:26 ` [PATCH v12 3/6] i2c: tegra: Update Tegra256 timing parameters Akhil R
2025-11-17 9:52 ` Jon Hunter
2025-11-15 4:26 ` [PATCH v12 4/6] i2c: tegra: Add HS mode support Akhil R
2025-11-17 11:07 ` Jon Hunter
2025-11-18 11:09 ` Akhil R
2025-11-18 12:16 ` Jon Hunter
2025-11-18 12:25 ` Jon Hunter [this message]
2025-11-15 4:26 ` [PATCH v12 5/6] i2c: tegra: Add support for SW mutex register Akhil R
2025-11-15 4:26 ` [PATCH v12 6/6] i2c: tegra: Add Tegra264 support Akhil R
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=926d94d9-0719-4ade-910b-6042a2a8171b@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=akhilrajeev@nvidia.com \
--cc=andi.shyti@kernel.org \
--cc=digetx@gmail.com \
--cc=kkartik@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=smangipudi@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=wsa+renesas@sang-engineering.com \
--cc=wsa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox