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,
smangipudi@nvidia.com, thierry.reding@gmail.com
Subject: Re: [PATCH v8 2/4] i2c: tegra: Add HS mode support
Date: Thu, 18 Sep 2025 18:33:37 +0100 [thread overview]
Message-ID: <a85af39b-166a-4eff-a6c1-4721e7374c73@nvidia.com> (raw)
In-Reply-To: <20250918171247.72087-1-akhilrajeev@nvidia.com>
On 18/09/2025 18:12, Akhil R wrote:
...
>> OK, I see now. So we need to program the normal timings first and then
>> we are re-using the variables to then program the HS timings. And
>> because of that we cannot setup the HS timing values in the existing
>> case statement?
>>
>>> So, I am not sure if moving this section to the switch block will add
>>> any benefit. We might end up making it more complicated that it is now.
>>
>> Yes that's true. It was really this else part that caught my eye ...
>>
>> } else if (t->bus_freq_hz > I2C_MAX_FAST_MODE_PLUS_FREQ) {
>> t->bus_freq_hz = I2C_MAX_FAST_MODE_PLUS_FREQ;
>> }
>>
>> It feels like at least this part should be handled as part of the case
>> statement.
>
> Yes. That makes sense. If you agree, we can remove the else part because
> we weren't doing this before when HS mode support was not there. It is not
> directly related to the HS mode support as well. We can add this at a later
> point in a separate patch if found required.
Hmmm ... I am not sure because then we could potentially program the
packet header incorrectly later on. May be that will never happen?
However, I think it would be better to not make any assumptions here and
make the code as robust as possible.
Jon
--
nvpublic
next prev parent reply other threads:[~2025-09-18 17:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 8:56 [PATCH v8 0/4] Add I2C support for Tegra264 Kartik Rajput
2025-09-17 8:56 ` [PATCH v8 1/4] i2c: tegra: Do not configure DMA if not supported Kartik Rajput
2025-09-17 14:08 ` Jon Hunter
2025-09-18 7:10 ` Kartik Rajput
2025-09-17 8:56 ` [PATCH v8 2/4] i2c: tegra: Add HS mode support Kartik Rajput
2025-09-17 13:59 ` Jon Hunter
2025-09-18 10:04 ` Akhil R
2025-09-18 10:21 ` Jon Hunter
2025-09-18 11:16 ` Akhil R
2025-09-18 12:55 ` Jon Hunter
2025-09-18 17:12 ` Akhil R
2025-09-18 17:33 ` Jon Hunter [this message]
2025-09-17 8:56 ` [PATCH v8 3/4] i2c: tegra: Add support for SW mutex register Kartik Rajput
2025-09-17 8:56 ` [PATCH v8 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=a85af39b-166a-4eff-a6c1-4721e7374c73@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
all inboxes | Powered by JetHome®