From: Jon Hunter <jonathanh@nvidia.com>
To: Akhil R <akhilrajeev@nvidia.com>
Cc: 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 16:02:36 +0000 [thread overview]
Message-ID: <17d683d1-c306-4860-acc2-9c09bbce0d55@nvidia.com> (raw)
In-Reply-To: <20251106061733.36157-1-akhilrajeev@nvidia.com>
On 06/11/2025 06:17, Akhil R wrote:
> 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:
I can't say I am a fan of this 'default' part. I don't find this very
clear at all.
> + /*
> + * 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;
Looking at this code are we better off converting this to a simple
if-statement?
So we have ...
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 {
...
}
Jon
--
nvpublic
next prev parent reply other threads:[~2025-11-06 16:02 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
2025-11-06 16:02 ` Jon Hunter [this message]
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=17d683d1-c306-4860-acc2-9c09bbce0d55@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=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
all inboxes | Powered by JetHome®