[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <56fcl2ip6ecu4inig7ecpjt7qrsdt6sehkrzrk6joysbp6tea7@4xdgxhhe3aso>
Date: Wed, 15 Oct 2025 23:10:55 +0300
From: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
To: Robin Murphy <robin.murphy@....com>
Cc: Konrad Dybcio <konradybcio@...nel.org>, Joerg Roedel <joro@...tes.org>,
Will Deacon <will@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, linux-arm-msm@...r.kernel.org,
iommu@...ts.linux.dev, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, Konrad Dybcio <konrad.dybcio@...aro.org>
Subject: Re: [PATCH v2] dt-bindings: iommu: qcom_iommu: Allow 'tbu' clock
On Wed, Oct 15, 2025 at 05:48:05PM +0100, Robin Murphy wrote:
> On 2025-10-15 5:41 pm, Konrad Dybcio wrote:
> > From: Konrad Dybcio <konrad.dybcio@...aro.org>
> >
> > Some IOMMUs on some platforms (there doesn't seem to be a good denominator
It would be nice to provide some examples here.
> > for this) require the presence of a third clock, specifically for
> > accessing the IOMMU's Translation Buffer Unit (TBU). Allow it.
>
> Hmmm, but isn't the only thing that accesses TBUs the consumer of the
> qcom,tbu binding, which already has its own clock?
qcom,tbu is only defined for normal arm,mmu-500 platforms. Here Konrad
is fixing the older and more obscure Qualcomm virtual MMU device.
>
> Thanks,
> Robin.
>
> > Reviewed-by: Rob Herring <robh@...nel.org>
> > Signed-off-by: Konrad Dybcio <konrad.dybcio@...aro.org>
> > ---
> > Resending from a 2023 megaseries, no changes
> >
> > v1: https://lore.kernel.org/lkml/20230627-topic-more_bindings-v1-7-6b4b6cd081e5@linaro.org/
> > ---
> > Documentation/devicetree/bindings/iommu/qcom,iommu.yaml | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
--
With best wishes
Dmitry
Powered by blists - more mailing lists