From: Kartik Rajput <kkartik@nvidia.com>
To: "thierry.reding@gmail.com" <thierry.reding@gmail.com>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
Jon Hunter <jonathanh@nvidia.com>,
Akhil R <akhilrajeev@nvidia.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"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>,
"digetx@gmail.com" <digetx@gmail.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH v3 2/5] i2c: tegra: Do not configure DMA if not supported
Date: Mon, 16 Jun 2025 10:01:39 +0000 [thread overview]
Message-ID: <990e01e1864180247212775c2e27955a73bfea56.camel@nvidia.com> (raw)
In-Reply-To: <z3evk6j53hbgf426kc4ltdv4dbisoqnwkfwhapyenpadhey6v7@zvbljg5svppi>
Thanks for reviewing the patch Thierry!
On Tue, 2025-06-10 at 10:28 +0200, Thierry Reding wrote:
> On Mon, Jun 09, 2025 at 03:04:17PM +0530, Kartik Rajput wrote:
> > On Tegra264, not all I2C controllers have the necessary interface
> > to
> > GPC DMA, this causes failures when function tegra_i2c_init_dma()
> > is called.
> >
> > Ensure that "dmas" device-tree property is present before
> > initializing
> > DMA in function tegra_i2c_init_dma().
> >
> > Signed-off-by: Kartik Rajput <kkartik@nvidia.com>
> > ---
> > v1 -> v2:
> > * Update commit message to clarify that some I2C
> > controllers may
> > not have the necessary interface to GPC DMA.
> > ---
> > drivers/i2c/busses/i2c-tegra.c | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/drivers/i2c/busses/i2c-tegra.c
> > b/drivers/i2c/busses/i2c-tegra.c
> > index ebd51165c46b..c7237d26b813 100644
> > --- a/drivers/i2c/busses/i2c-tegra.c
> > +++ b/drivers/i2c/busses/i2c-tegra.c
> > @@ -448,6 +448,9 @@ static int tegra_i2c_init_dma(struct
> > tegra_i2c_dev *i2c_dev)
> > if (IS_VI(i2c_dev))
> > return 0;
> >
> > + if (!device_property_present(i2c_dev->dev, "dmas"))
> > + return 0;
>
> I know that you use the OF-independent variant here, but has this
> been
> tested on ACPI?
No, Tegra I2C driver does not support DMA with ACPI boot.
>
> Originally the intention behind this code was to get some sort of
> validation of the DT (i.e. dmas property is desired, so we want to
> flag
> if it isn't provided) with the fallback existing mostly just so
> things
> can operate in the absence (or if APB/GPC DMA isn't available for
> some
> reason).
>
> If we now solely make this depend on the availability of the DT (or
> ACPI) property, then we loose all of that validation. I suppose we
> have
> DT schema to check for these kinds of things now, but since we're not
> marking these properties as required, there's really no validation at
> all anymore.
>
> My concern is that if somebody's left out the dmas/dma-names
> properties
> by accident, they may not get what they were asking for and we have
> no
> hints to provide whatsoever. Maybe that's okay if we provide the base
> DT, which has been unmodified for a while.
Should I add an info print here, to indicate that we are missing the
"dmas" property?
>
> If that's what we want to do, it no longer makes sense to keep the
> IS_VI() check above, though, because that's just redundant now.
Ack, I will move this check above.
>
> Thierry
Thanks & Regards,
Kartik
next prev parent reply other threads:[~2025-06-16 10:01 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
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 [this message]
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=990e01e1864180247212775c2e27955a73bfea56.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