[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aUROk0jRQoLmBRo3@Asurada-Nvidia>
Date: Thu, 18 Dec 2025 10:57:23 -0800
From: Nicolin Chen <nicolinc@...dia.com>
To: Jon Hunter <jonathanh@...dia.com>
CC: Ashish Mhetre <amhetre@...dia.com>, <will@...nel.org>,
<robin.murphy@....com>, <joro@...tes.org>, <robh@...nel.org>,
<krzk+dt@...nel.org>, <conor+dt@...nel.org>, <thierry.reding@...il.com>,
<vdumpa@...dia.com>, <jgg@...pe.ca>, <linux-arm-kernel@...ts.infradead.org>,
<iommu@...ts.linux.dev>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-tegra@...r.kernel.org>
Subject: Re: [PATCH V7 2/4] iommu/arm-smmu-v3: Add device-tree support for
CMDQV driver
On Thu, Dec 18, 2025 at 08:48:32AM +0000, Jon Hunter wrote:
> On 18/12/2025 06:32, Ashish Mhetre wrote:
> > On 12/18/2025 2:13 AM, Jon Hunter wrote:
> > > > + smmu->impl_dev = &pdev->dev;
> > > > + smmu->options |= ARM_SMMU_OPT_TEGRA241_CMDQV;
> > > > + dev_info(smmu->dev, "found companion CMDQV device: %s\n",
> > > > + dev_name(smmu->impl_dev));
> > >
> > > This seems a bit noisy. dev_dbg?
> > >
> >
> > This info print is similar to what is there in ACPI path as well.
> > It's only a single print per SMMU at boot time. Should I still change
> > it to dev_dbg?
>
> Yes, I would.
It's really not that bad IMHO, I am not against that though..
If we have to change that, we'd need another patch changing the
one in the ACPI path as well to keep things aligned.
Nicolin
Powered by blists - more mailing lists