From: Akhil R <akhilrajeev@nvidia.com>
To: <andi.shyti@kernel.org>, <conor+dt@kernel.org>,
<devicetree@vger.kernel.org>, <digetx@gmail.com>,
<jonathanh@nvidia.com>, <krzk+dt@kernel.org>,
<linux-i2c@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-tegra@vger.kernel.org>, <thierry.reding@gmail.com>
Cc: <akhilrajeev@nvidia.com>, <ldewangan@nvidia.com>, <robh@kernel.org>
Subject: [PATCH 0/2] i2c: tegra: Add Tegra256 I2C controller support
Date: Thu, 31 Jul 2025 14:41:20 +0530 [thread overview]
Message-ID: <20250731091122.53921-1-akhilrajeev@nvidia.com> (raw)
This series adds support for Tegra256 I2C controllers to the Tegra I2C driver.
Tegra256 consists of 8 generic I2C controllers similar to previous Tegra generations,
but with a different parent clock frequency requiring adjusted timing parameters.
The changes add the "nvidia,tegra256-i2c" compatible string to device tree bindings
and implement the corresponding hardware feature structure with appropriate timing
parameters and clock divisors.
Akhil R (2):
dt-bindings: i2c: nvidia,tegra20-i2c: Add Tegra256 I2C
i2c: tegra: Add Tegra256 support
.../bindings/i2c/nvidia,tegra20-i2c.yaml | 6 +++++
drivers/i2c/busses/i2c-tegra.c | 26 +++++++++++++++++++
2 files changed, 32 insertions(+)
--
2.50.1
next reply other threads:[~2025-07-31 9:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 9:11 Akhil R [this message]
2025-07-31 9:11 ` [PATCH 1/2] dt-bindings: i2c: nvidia,tegra20-i2c: Add Tegra256 I2C compatible Akhil R
2025-07-31 17:37 ` Rob Herring (Arm)
2025-08-01 9:56 ` Thierry Reding
2025-07-31 9:11 ` [PATCH 2/2] i2c: tegra: Add Tegra256 support Akhil R
2025-08-01 9:56 ` Thierry Reding
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=20250731091122.53921-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=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;
as well as URLs for NNTP newsgroup(s).