| Message ID | 1373021097-32420-7-git-send-email-hdoyu@nvidia.com |
|---|---|
| State | Superseded, archived |
| Headers | show |
On 07/05/2013 04:44 AM, Hiroshi Doyu wrote:
> Fix IOMMU register address.
Oh dear, how serious is this?
That incorrect node got added in v3.9 - a long time ago. Does the SMMU
driver touch registers during probe() or under any other condition right
now? If so, can that hang the CPU or end up trashing some other HW
module's registers?
I'm trying to determine whether we need to urgently send this patch as a
fix Cc: stable.
--
To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, Jul 16, 2013 at 05:18:29PM -0600, Stephen Warren wrote: > On 07/05/2013 04:44 AM, Hiroshi Doyu wrote: > > Fix IOMMU register address. > > Oh dear, how serious is this? > > That incorrect node got added in v3.9 - a long time ago. Does the SMMU > driver touch registers during probe() or under any other condition right > now? If so, can that hang the CPU or end up trashing some other HW > module's registers? > > I'm trying to determine whether we need to urgently send this patch as a > fix Cc: stable. Judging by the TRM there's nothing in the range from 0x7000ec00 to 0x7000f7ff, so hopefully we got lucky. Thierry
diff --git a/arch/arm/boot/dts/tegra114.dtsi b/arch/arm/boot/dts/tegra114.dtsi index abf6c40..1f45cf5 100644 --- a/arch/arm/boot/dts/tegra114.dtsi +++ b/arch/arm/boot/dts/tegra114.dtsi @@ -318,9 +318,9 @@ iommu { compatible = "nvidia,tegra114-smmu", "nvidia,tegra30-smmu"; - reg = <0x7000f010 0x02c - 0x7000f1f0 0x010 - 0x7000f228 0x074>; + reg = <0x70019010 0x02c + 0x700191f0 0x010 + 0x70019228 0x074>; nvidia,#asids = <4>; dma-window = <0 0x40000000>; nvidia,swgroups = <0x18659fe>;
Fix IOMMU register address. Signed-off-by: Hiroshi Doyu <hdoyu@nvidia.com> --- arch/arm/boot/dts/tegra114.dtsi | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)