From: Jon Hunter <jonathanh@nvidia.com>
To: Kartik Rajput <kkartik@nvidia.com>,
akhilrajeev@nvidia.com, andi.shyti@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
thierry.reding@gmail.com, ldewangan@nvidia.com, digetx@gmail.com,
smangipudi@nvidia.com, linux-i2c@vger.kernel.org,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v11 2/4] i2c: tegra: Add HS mode support
Date: Tue, 11 Nov 2025 11:24:45 +0000 [thread overview]
Message-ID: <83b76f45-e08f-4fc7-811c-647bac2c3d36@nvidia.com> (raw)
In-Reply-To: <20251111091627.870613-3-kkartik@nvidia.com>
On 11/11/2025 09:16, Kartik Rajput wrote:
> From: Akhil R <akhilrajeev@nvidia.com>
>
> 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.
>
> Signed-off-by: Akhil R <akhilrajeev@nvidia.com>
> Signed-off-by: Kartik Rajput <kkartik@nvidia.com>
> ---
> v10 -> v11:
> * Update the if condition as per the comments received on:
> https://lore.kernel.org/linux-tegra/20251110080502.865953-1-kkartik@nvidia.com/T/#t
> v9 -> v10:
> * Change switch block to an if-else block.
> v5 -> v9:
> * In the switch block, handle the case when hs mode is not
> supported. Also update it to use Fast mode for master code
> byte as per the I2C spec for HS mode.
> v3 -> v5:
> * Set has_hs_mode_support to false for unsupported SoCs.
> v2 -> v3:
> * Document tlow_hs_mode and thigh_hs_mode.
> v1 -> v2:
> * Document has_hs_mode_support.
> * Add a check to set the frequency to fastmode+ if the device
> does not support HS mode but the requested frequency is more
> than fastmode+.
> ---
> drivers/i2c/busses/i2c-tegra.c | 62 ++++++++++++++++++++++++++--------
> 1 file changed, 48 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-tegra.c b/drivers/i2c/busses/i2c-tegra.c
> index bd26b232ffb3..2b18ceb837da 100644
> --- a/drivers/i2c/busses/i2c-tegra.c
> +++ b/drivers/i2c/busses/i2c-tegra.c
> @@ -91,6 +91,7 @@
> #define I2C_HEADER_IE_ENABLE BIT(17)
> #define I2C_HEADER_REPEAT_START BIT(16)
> #define I2C_HEADER_CONTINUE_XFER BIT(15)
> +#define I2C_HEADER_HS_MODE BIT(22)
> #define I2C_HEADER_SLAVE_ADDR_SHIFT 1
>
> #define I2C_BUS_CLEAR_CNFG 0x084
> @@ -198,6 +199,8 @@ enum msg_end_type {
> * @thigh_std_mode: High period of the clock in standard mode.
> * @tlow_fast_fastplus_mode: Low period of the clock in fast/fast-plus modes.
> * @thigh_fast_fastplus_mode: High period of the clock in fast/fast-plus modes.
> + * @tlow_hs_mode: Low period of the clock in HS mode.
> + * @thigh_hs_mode: High period of the clock in HS mode.
> * @setup_hold_time_std_mode: Setup and hold time for start and stop conditions
> * in standard mode.
> * @setup_hold_time_fast_fast_plus_mode: Setup and hold time for start and stop
> @@ -206,6 +209,7 @@ enum msg_end_type {
> * in HS mode.
> * @has_interface_timing_reg: Has interface timing register to program the tuned
> * timing settings.
> + * @has_hs_mode_support: Has support for high speed (HS) mode transfers.
> */
> struct tegra_i2c_hw_feature {
> bool has_continue_xfer_support;
> @@ -226,10 +230,13 @@ struct tegra_i2c_hw_feature {
> u32 thigh_std_mode;
> u32 tlow_fast_fastplus_mode;
> u32 thigh_fast_fastplus_mode;
> + u32 tlow_hs_mode;
> + u32 thigh_hs_mode;
> u32 setup_hold_time_std_mode;
> u32 setup_hold_time_fast_fast_plus_mode;
> u32 setup_hold_time_hs_mode;
> bool has_interface_timing_reg;
> + bool has_hs_mode_support;
> };
>
> /**
> @@ -677,25 +684,28 @@ static int tegra_i2c_init(struct tegra_i2c_dev *i2c_dev)
> if (IS_VI(i2c_dev))
> tegra_i2c_vi_init(i2c_dev);
>
> - switch (t->bus_freq_hz) {
> - case I2C_MAX_STANDARD_MODE_FREQ + 1 ... I2C_MAX_FAST_MODE_PLUS_FREQ:
> - default:
> + if (t->bus_freq_hz <= I2C_MAX_STANDARD_MODE_FREQ) {
> + tlow = i2c_dev->hw->tlow_std_mode;
> + thigh = i2c_dev->hw->thigh_std_mode;
> + tsu_thd = i2c_dev->hw->setup_hold_time_std_mode;
> + non_hs_mode = i2c_dev->hw->clk_divisor_std_mode;
> + } else {
> tlow = i2c_dev->hw->tlow_fast_fastplus_mode;
> thigh = i2c_dev->hw->thigh_fast_fastplus_mode;
> tsu_thd = i2c_dev->hw->setup_hold_time_fast_fast_plus_mode;
>
> - if (t->bus_freq_hz > I2C_MAX_FAST_MODE_FREQ)
> - non_hs_mode = i2c_dev->hw->clk_divisor_fast_plus_mode;
> - else
> + /*
> + * When HS mode is supported, the non-hs timing registers will be used for the
> + * master code byte for transition to HS mode. As per the spec, the 8 bit master
> + * code should be sent at max 400kHz. Therefore, limit the bus speed to fast mode.
> + * Whereas when HS mode is not supported, allow the highest speed mode capable.
> + */
> + if (t->bus_freq_hz < I2C_MAX_FAST_MODE_PLUS_FREQ ||
> + (t->bus_freq_hz > I2C_MAX_FAST_MODE_PLUS_FREQ &&
> + i2c_dev->hw->has_hs_mode_support))
> non_hs_mode = i2c_dev->hw->clk_divisor_fast_mode;
I am still not sure this is correct. Before we had ...
if (t->bus_freq_hz > I2C_MAX_FAST_MODE_FREQ)
non_hs_mode = i2c_dev->hw->clk_divisor_fast_plus_mode;
Now we have ...
if (t->bus_freq_hz >= I2C_MAX_FAST_MODE_PLUS_FREQ)
non_hs_mode = i2c_dev->hw->clk_divisor_fast_plus_mode;
Don't we want ...
if (t->bus_freq_hz <= I2C_MAX_FAST_MODE_FREQ)
non_hs_mode = i2c_dev->hw->clk_divisor_fast_mode;
else if (i2c_dev->hw->has_hs_mode_support)
non_hs_mode = i2c_dev->hw->clk_divisor_fast_mode;
else
non_hs_mode = i2c_dev->hw->clk_divisor_fast_plus_mode;
Or
if (!i2c_dev->hw->has_hs_mode_support && t->bus_freq_hz >
I2C_MAX_FAST_MODE_FREQ)
non_hs_mode = i2c_dev->hw->clk_divisor_fast_plus_mode;
else
non_hs_mode = i2c_dev->hw->clk_divisor_fast_mode;
Jon
--
nvpublic
next prev parent reply other threads:[~2025-11-11 11:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 9:16 [PATCH v11 0/4] Add I2C support for Tegra264 Kartik Rajput
2025-11-11 9:16 ` [PATCH v11 1/4] i2c: tegra: Do not configure DMA if not supported Kartik Rajput
2025-11-11 9:16 ` [PATCH v11 2/4] i2c: tegra: Add HS mode support Kartik Rajput
2025-11-11 11:24 ` Jon Hunter [this message]
2025-11-11 9:16 ` [PATCH v11 3/4] i2c: tegra: Add support for SW mutex register Kartik Rajput
2025-11-11 9:16 ` [PATCH v11 4/4] i2c: tegra: Add Tegra264 support Kartik Rajput
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=83b76f45-e08f-4fc7-811c-647bac2c3d36@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=akhilrajeev@nvidia.com \
--cc=andi.shyti@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=kkartik@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=ldewangan@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=smangipudi@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).