From: Krzysztof Kozlowski <krzk@kernel.org>
To: Kartik Rajput <kkartik@nvidia.com>,
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 v2 1/5] dt-bindings: i2c: nvidia,tegra20-i2c: Document Tegra264 I2C
Date: Thu, 30 Jan 2025 17:14:10 +0100 [thread overview]
Message-ID: <db995d99-f277-4438-89aa-299b0c821d00@kernel.org> (raw)
In-Reply-To: <20250130143424.52389-2-kkartik@nvidia.com>
On 30/01/2025 15:34, Kartik Rajput wrote:
> Tegra264 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>
You did not update the constraints.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-01-30 16:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 14:34 [PATCH v2 0/5] Add I2C support for Tegra264 Kartik Rajput
2025-01-30 14:34 ` [PATCH v2 1/5] dt-bindings: i2c: nvidia,tegra20-i2c: Document Tegra264 I2C Kartik Rajput
2025-01-30 16:14 ` Krzysztof Kozlowski [this message]
2025-01-30 14:34 ` [PATCH v2 2/5] i2c: tegra: Do not configure DMA if not supported Kartik Rajput
2025-01-30 14:34 ` [PATCH v2 3/5] i2c: tegra: Add HS mode support Kartik Rajput
2025-01-30 14:34 ` [PATCH v2 4/5] i2c: tegra: Add support for SW mutex register Kartik Rajput
2025-01-30 16:12 ` Krzysztof Kozlowski
2025-01-30 16:35 ` Kartik Rajput
2025-01-30 17:49 ` Krzysztof Kozlowski
2025-01-31 6:46 ` Kartik Rajput
2025-01-30 14:34 ` [PATCH v2 5/5] 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=db995d99-f277-4438-89aa-299b0c821d00@kernel.org \
--to=krzk@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