public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Akhil R <akhilrajeev@nvidia.com>
To: <jonathanh@nvidia.com>
Cc: <akhilrajeev@nvidia.com>, <andi.shyti@kernel.org>,
	<conor+dt@kernel.org>, <devicetree@vger.kernel.org>,
	<digetx@gmail.com>, <kkartik@nvidia.com>, <krzk+dt@kernel.org>,
	<ldewangan@nvidia.com>, <linux-i2c@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
	<robh@kernel.org>, <thierry.reding@gmail.com>
Subject: Re: [PATCH v9 2/4] i2c: tegra: Add HS mode support
Date: Thu, 6 Nov 2025 11:47:33 +0530	[thread overview]
Message-ID: <20251106061733.36157-1-akhilrajeev@nvidia.com> (raw)
In-Reply-To: <84f7f5d4-bb6a-4e2a-9579-0d957b692de2@nvidia.com>

On Fri, 24 Oct 2025 16:28:50 +0100, Jon Hunter wrote:
> On 01/10/2025 07:47, Kartik Rajput wrote:

...

>>   /**
>> @@ -678,16 +685,28 @@ static int tegra_i2c_init(struct tegra_i2c_dev *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 (!i2c_dev->hw->has_hs_mode_support)
>> +                     t->bus_freq_hz = I2C_MAX_FAST_MODE_PLUS_FREQ;
>> +             fallthrough;
>> +
>>
> This looks odd. I guess this is carry over from the previous code, but
> now it looks very odd to someone reviewing the code after this change
> has been made. We need to make the code here more logical so that the
> reader stands a chance of understanding the new logic.

Would it look better if I update as below?

@@ -678,8 +685,26 @@ static int tegra_i2c_init(struct tegra_i2c_dev *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:
+               /*
+                * 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 (i2c_dev->hw->has_hs_mode_support) {
+                       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;
+                       non_hs_mode = i2c_dev->hw->clk_divisor_fast_mode;
+
+                       break;
+               } else {
+                       t->bus_freq_hz = I2C_MAX_FAST_MODE_PLUS_FREQ;
+               }
+               fallthrough;
+
+       case I2C_MAX_STANDARD_MODE_FREQ + 1 ... I2C_MAX_FAST_MODE_PLUS_FREQ:
                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;
@@ -688,6 +713,7 @@ static int tegra_i2c_init(struct tegra_i2c_dev *i2c_dev)

...

>> @@ -717,6 +736,18 @@ static int tegra_i2c_init(struct tegra_i2c_dev *i2c_dev)
>>   	if (i2c_dev->hw->has_interface_timing_reg && tsu_thd)
>>   		i2c_writel(i2c_dev, tsu_thd, I2C_INTERFACE_TIMING_1);
>>   
>>   
>> +	/* Write HS mode registers. These will get used only for HS mode*/
>> +	if (i2c_dev->hw->has_hs_mode_support) {
>> +		tlow = i2c_dev->hw->tlow_hs_mode;
>> +		thigh = i2c_dev->hw->thigh_hs_mode;
>> +		tsu_thd = i2c_dev->hw->setup_hold_time_hs_mode;
>> +
>> +		val = FIELD_PREP(I2C_HS_INTERFACE_TIMING_THIGH, thigh) |
>> +			FIELD_PREP(I2C_HS_INTERFACE_TIMING_TLOW, tlow);
>> +		i2c_writel(i2c_dev, val, I2C_HS_INTERFACE_TIMING_0);
>> +		i2c_writel(i2c_dev, tsu_thd, I2C_HS_INTERFACE_TIMING_1);
>> +	}
>> +
>
> I still think all of the above needs a bit of work.

I suppose the above section can be as is since HS mode registers are independent
of other speed modes. Any suggestions or thoughts?

Regards,
Akhil

  reply	other threads:[~2025-11-06  6:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-01  6:47 [PATCH v9 0/4] Add I2C support for Tegra264 Kartik Rajput
2025-10-01  6:47 ` [PATCH v9 1/4] i2c: tegra: Do not configure DMA if not supported Kartik Rajput
2025-10-24 15:20   ` Jon Hunter
2025-10-28 10:00     ` Akhil R
2025-10-28 10:41       ` Jon Hunter
2025-10-28 13:08         ` Akhil R
2025-10-28 16:09           ` Jon Hunter
2025-11-06 15:51   ` Jon Hunter
2025-10-01  6:47 ` [PATCH v9 2/4] i2c: tegra: Add HS mode support Kartik Rajput
2025-10-24 15:28   ` Jon Hunter
2025-11-06  6:17     ` Akhil R [this message]
2025-11-06 16:02       ` Jon Hunter
2025-10-01  6:47 ` [PATCH v9 3/4] i2c: tegra: Add support for SW mutex register Kartik Rajput
2025-10-24 15:42   ` Jon Hunter
2025-10-28 12:54     ` Akhil R
2025-10-28 16:14       ` Jon Hunter
2025-11-06 15:52   ` Jon Hunter
2025-10-01  6:47 ` [PATCH v9 4/4] i2c: tegra: Add Tegra264 support Kartik Rajput
2025-10-24 15:43   ` Jon Hunter
2025-10-21  8:17 ` [PATCH v9 0/4] Add I2C support for Tegra264 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=20251106061733.36157-1-akhilrajeev@nvidia.com \
    --to=akhilrajeev@nvidia.com \
    --cc=andi.shyti@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=digetx@gmail.com \
    --cc=jonathanh@nvidia.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=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