From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [PATCH 1/1] IOMMU: function flush_iotlb_page is not flushing correct entry Date: Thu, 18 Jun 2009 08:05:56 +0300 Message-ID: <20090618050554.GD8079@atomide.com> References: <1245058706-22504-1-git-send-email-Hiroshi.DOYU@nokia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mho-02-ewr.mailhop.org ([204.13.248.72]:62842 "EHLO mho-02-ewr.mailhop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751726AbZFRHGB (ORCPT ); Thu, 18 Jun 2009 03:06:01 -0400 Content-Disposition: inline In-Reply-To: <1245058706-22504-1-git-send-email-Hiroshi.DOYU@nokia.com> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Hiroshi DOYU Cc: linux-omap@vger.kernel.org, Fernando Guzman Lugo * Hiroshi DOYU [090615 12:39]: > From: Fernando Guzman Lugo > > From: Fernando Guzman Lugo > > The function flush_iotlb_page is not loading the CAM register with > the correct entry to be flushed, so it is flushing other entry > > Signed-off-by: Fernando Guzman Lugo > Signed-off-by: Hiroshi DOYU > --- > arch/arm/plat-omap/iommu.c | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > mode change 100644 => 100755 arch/arm/plat-omap/iommu.c > > diff --git a/arch/arm/plat-omap/iommu.c b/arch/arm/plat-omap/iommu.c > old mode 100644 > new mode 100755 This made some bad mode changes as noted by Paul, will fix in l-o master and in omap-fixes. But please check your repos too! Tony > index 4cf449f..4a03013 > --- a/arch/arm/plat-omap/iommu.c > +++ b/arch/arm/plat-omap/iommu.c > @@ -298,7 +298,7 @@ void flush_iotlb_page(struct iommu *obj, u32 da) > if ((start <= da) && (da < start + bytes)) { > dev_dbg(obj->dev, "%s: %08x<=%08x(%x)\n", > __func__, start, da, bytes); > - > + iotlb_load_cr(obj, &cr); > iommu_write_reg(obj, 1, MMU_FLUSH_ENTRY); > } > } > -- > 1.6.0.4 > > -- > To unsubscribe from this list: send the line "unsubscribe linux-omap" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html