[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BYAPR12MB271012F225E35C1459E58D07B3BD0@BYAPR12MB2710.namprd12.prod.outlook.com>
Date: Fri, 30 Aug 2019 18:12:08 +0000
From: Krishna Reddy <vdumpa@...dia.com>
To: Robin Murphy <robin.murphy@....com>
CC: Sachin Nikam <Snikam@...dia.com>,
"Thomas Zeng (SW-TEGRA)" <thomasz@...dia.com>,
Juha Tukkinen <jtukkinen@...dia.com>,
Mikko Perttunen <mperttunen@...dia.com>,
Pritesh Raithatha <praithatha@...dia.com>,
"iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Timo Alho <talho@...dia.com>, Yu-Huan Hsu <YHsu@...dia.com>,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
Thierry Reding <treding@...dia.com>,
Alexander Van Brunt <avanbrunt@...dia.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: RE: [PATCH 2/7] dt-bindings: arm-smmu: Add binding for nvidia,smmu-v2
>> + "nidia,smmu-v2"
>> "qcom,smmu-v2"
>I agree with Mikko that the compatible must be at least SoC-specific, but potentially even instance-specific (e.g. "nvidia,tegra194-gpu-smmu")
> depending on how many of these parallel-SMMU configurations might be hiding in current and future SoCs.
I am correcting the spelling mistake pointed by Mikko. The NVIDIA SMMUv2 implementation is getting used beyond Tegra194 SOC.
To be able to use the smmu compatible string across multiple SOC's, "nvidia,smmu-v2" compatible string is chosen.
Are you suggesting to make it soc specific and add another one in future?
-KR
Powered by blists - more mailing lists