From: Conor Dooley <conor@kernel.org>
To: Kartik Rajput <kkartik@nvidia.com>
Cc: akhilrajeev@nvidia.com, andi.shyti@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
thierry.reding@gmail.com, jonathanh@nvidia.com,
ldewangan@nvidia.com, digetx@gmail.com,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/5] dt-bindings: i2c: nvidia,tegra20-i2c: Document Tegra264 I2C
Date: Mon, 9 Jun 2025 17:09:53 +0100 [thread overview]
Message-ID: <20250609-sizzle-shush-b2eb1443b3f7@spud> (raw)
In-Reply-To: <20250609093420.3050641-2-kkartik@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 1900 bytes --]
On Mon, Jun 09, 2025 at 03:04:16PM +0530, Kartik Rajput wrote:
> iTegra264 has 17 generic I2C controllers, two of which are in always-on
> partition of the SoC. In addition to the features supported by Tegra194
> it also supports a SW mutex register to allow sharing the same I2C
> instance across multiple firmware.
>
> Document compatible string "nvidia,tegra264-i2c" for Tegra264 I2C.
>
> Signed-off-by: Kartik Rajput <kkartik@nvidia.com>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
> ---
> v2 -> v3:
> * Add constraints for "nvidia,tegra264-i2c".
> v1 -> v2:
> * Fixed typos.
> ---
> .../devicetree/bindings/i2c/nvidia,tegra20-i2c.yaml | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/i2c/nvidia,tegra20-i2c.yaml b/Documentation/devicetree/bindings/i2c/nvidia,tegra20-i2c.yaml
> index 6b6f6762d122..f0693b872cb6 100644
> --- a/Documentation/devicetree/bindings/i2c/nvidia,tegra20-i2c.yaml
> +++ b/Documentation/devicetree/bindings/i2c/nvidia,tegra20-i2c.yaml
> @@ -80,6 +80,12 @@ properties:
> support for 64 KiB transactions whereas earlier chips supported no
> more than 4 KiB per transactions.
> const: nvidia,tegra194-i2c
> + - description:
> + Tegra264 has 17 generic I2C controllers, two of which are in the AON
> + (always-on) partition of the SoC. In addition to the features from
> + Tegra194, a SW mutex register is added to support use of the same I2C
> + instance across multiple firmwares.
> + const: nvidia,tegra264-i2c
>
> reg:
> maxItems: 1
> @@ -186,6 +192,7 @@ allOf:
> contains:
> enum:
> - nvidia,tegra194-i2c
> + - nvidia,tegra264-i2c
> then:
> required:
> - resets
> --
> 2.43.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-06-09 16:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 9:34 [PATCH v3 0/5] Add I2C support for Tegra264 Kartik Rajput
2025-06-09 9:34 ` [PATCH v3 1/5] dt-bindings: i2c: nvidia,tegra20-i2c: Document Tegra264 I2C Kartik Rajput
2025-06-09 10:13 ` Kartik Rajput
2025-06-09 16:09 ` Conor Dooley [this message]
2025-06-09 9:34 ` [PATCH v3 2/5] i2c: tegra: Do not configure DMA if not supported Kartik Rajput
2025-06-10 8:28 ` Thierry Reding
2025-06-16 10:01 ` Kartik Rajput
2025-07-07 15:24 ` Thierry Reding
2025-06-09 9:34 ` [PATCH v3 3/5] i2c: tegra: Add HS mode support Kartik Rajput
2025-06-09 9:34 ` [PATCH v3 4/5] i2c: tegra: Add support for SW mutex register Kartik Rajput
2025-06-10 7:49 ` Thierry Reding
2025-06-16 10:25 ` Kartik Rajput
2025-07-07 15:29 ` Thierry Reding
2025-06-09 9:34 ` [PATCH v3 5/5] i2c: tegra: Add Tegra264 support Kartik Rajput
2025-06-10 7:53 ` Thierry Reding
2025-06-16 10:29 ` 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=20250609-sizzle-shush-b2eb1443b3f7@spud \
--to=conor@kernel.org \
--cc=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