public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Kartik Rajput <kkartik@nvidia.com>
To: "robh@kernel.org" <robh@kernel.org>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
	"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
	Jon Hunter <jonathanh@nvidia.com>,
	Akhil R <akhilrajeev@nvidia.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"digetx@gmail.com" <digetx@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"andi.shyti@kernel.org" <andi.shyti@kernel.org>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>,
	"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH 2/5] dt-bindings: i2c: nvidia,tegra20-i2c: Document Tegra264 I2C
Date: Wed, 15 Jan 2025 11:46:12 +0000	[thread overview]
Message-ID: <741475917f255c943002ab8efa7def30f038d2dc.camel@nvidia.com> (raw)
In-Reply-To: <20250110155509.GA2935916-robh@kernel.org>

Thanks Rob!

On Fri, 2025-01-10 at 09:55 -0600, Rob Herring wrote:
> External email: Use caution opening links or attachments
> 
> 
> On Wed, Jan 08, 2025 at 04:36:17PM +0530, 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 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>
> > ---
> >  .../devicetree/bindings/i2c/nvidia,tegra20-i2c.yaml         | 6
> > ++++++
> >  1 file changed, 6 insertions(+)
> > 
> > diff --git a/Documentation/devicetree/bindings/i2c/nvidia,tegra20-
> > i2c.yaml b/Documentation/devicetree/bindings/i2c/nvidia,tegra20-
> > i2c.yaml
> > index b57ae6963e62..2a016359328e 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: |
> 
> Don't need '|' if no formatting.
> 

ACK. Will fix this in v2.

Thanks & Regards,
Kartik

  reply	other threads:[~2025-01-15 11:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-08 11:06 [PATCH 0/5] Add I2C support for Tegra264 Kartik Rajput
2025-01-08 11:06 ` [PATCH 1/5] i2c: tegra: Add HS mode support Kartik Rajput
2025-01-08 16:45   ` Thierry Reding
2025-01-15 11:40     ` Kartik Rajput
2025-01-09 12:18   ` kernel test robot
2025-01-08 11:06 ` [PATCH 2/5] dt-bindings: i2c: nvidia,tegra20-i2c: Document Tegra264 I2C Kartik Rajput
2025-01-08 16:47   ` Thierry Reding
2025-01-15 11:41     ` Kartik Rajput
2025-01-10 15:55   ` Rob Herring
2025-01-15 11:46     ` Kartik Rajput [this message]
2025-01-08 11:06 ` [PATCH 3/5] i2c: tegra: Add Tegra264 support Kartik Rajput
2025-01-09  4:43   ` Mukesh Kumar Savaliya
2025-01-09 10:24     ` Thierry Reding
2025-01-09 12:37       ` Mukesh Kumar Savaliya
2025-01-08 11:06 ` [PATCH 4/5] i2c: tegra: Add support for SW Mutex register Kartik Rajput
2025-01-08 17:01   ` Thierry Reding
2025-01-15 11:39     ` Kartik Rajput
2025-01-08 11:06 ` [PATCH 5/5] i2c: tegra: Do not configure DMA if not supported Kartik Rajput
2025-01-09 10:33   ` Thierry Reding
2025-01-15 11:42     ` Kartik Rajput
2025-01-09 10:37 ` [PATCH 0/5] Add I2C support for Tegra264 Thierry Reding
2025-01-15 11:44   ` 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=741475917f255c943002ab8efa7def30f038d2dc.camel@nvidia.com \
    --to=kkartik@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=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