public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Akhil R <akhilrajeev@nvidia.com>
Cc: andi.shyti@kernel.org, digetx@gmail.com, kkartik@nvidia.com,
	ldewangan@nvidia.com, linux-i2c@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
	smangipudi@nvidia.com, thierry.reding@gmail.com,
	wsa+renesas@sang-engineering.com, wsa@kernel.org
Subject: Re: [PATCH v12 4/6] i2c: tegra: Add HS mode support
Date: Tue, 18 Nov 2025 12:16:57 +0000	[thread overview]
Message-ID: <f173a987-dafd-4bc7-9905-745f855e12bf@nvidia.com> (raw)
In-Reply-To: <20251118110903.61560-1-akhilrajeev@nvidia.com>


On 18/11/2025 11:09, Akhil R wrote:
> On Mon, 17 Nov 2025 11:07:07 +0000, Jon Hunter wrote:
>> 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.
>>>
>>> Signed-off-by: Akhil R <akhilrajeev@nvidia.com>
>>> Signed-off-by: Kartik Rajput <kkartik@nvidia.com>
>>> ---
>>> v10 -> v12:
>>> 	* Update bus_freq_hz to max supported freq and updates to
>>> 	  accomodate the changes from Patch 2/6.
>>> 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 | 59 ++++++++++++++++++++++++++++++++--
>>>    1 file changed, 57 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/i2c/busses/i2c-tegra.c b/drivers/i2c/busses/i2c-tegra.c
>>> index 8a696c88882e..9ebeb6a2eaf5 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)
>>
>> This should be ordered according to the value. So place this above
>> I2C_HEADER_CONT_ON_NAK.
> 
> Agree.
> 
> Do we need a new version with this change or would it be possible to
> update while applying?

Given we need another minor fix to 3/6 you might as well send a new version.

Jon
-- 
nvpublic


  reply	other threads:[~2025-11-18 12:17 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 [this message]
2025-11-18 12:25   ` Jon Hunter
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=f173a987-dafd-4bc7-9905-745f855e12bf@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