[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <11003810.ccjcAXkzhi@phil>
Date: Sat, 14 May 2016 22:19:43 +0200
From: Heiko Stuebner <heiko@...ech.de>
To: John Keeping <john@...anate.com>
Cc: iommu@...ts.linux-foundation.org, Joerg Roedel <joro@...tes.org>,
linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org,
ZhengShunQian <zhengsq@...k-chips.com>
Subject: Re: [PATCH] iommu/rockchip: fix zap cache during device attach
Am Dienstag, 10. Mai 2016, 16:50:46 schrieb John Keeping:
> rk_iommu_command() takes a struct rk_iommu and iterates over the slave
> MMUs, so this is doubly wrong in that we're passing in the wrong pointer
> and talking to MMUs that we shouldn't be.
>
> Fixes: cd6438c5f844 ("iommu/rockchip: Reconstruct to support multi
> slaves") Signed-off-by: John Keeping <john@...anate.com>
on a rk3288-veyron
Tested-by: Heiko Stuebner <heiko@...ech.de>
Reviewed-by: Heiko Stuebner <heiko@...ech.de>
I was wondering for a short time why this didn't spew warnings until I
realized that the iommu->bases[i] is of course a void* .
Heiko
Powered by blists - more mailing lists