From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM SMMU fixes
Date: Tue, 15 Apr 2014 17:55:07 +0200 [thread overview]
Message-ID: <15544035.e9eK8n7TO4@avalon> (raw)
In-Reply-To: <20140414165858.GI12916@arm.com>
Hi Will,
On Monday 14 April 2014 17:58:58 Will Deacon wrote:
> On Tue, Apr 08, 2014 at 02:57:43PM +0100, Marc Zyngier wrote:
> > On 08/04/14 14:41, Laurent Pinchart wrote:
> > > I've obviously forgotten that Will was away for a month. CC'ing Marc
> > > Zyngier.
> > >
> > > On Thursday 03 April 2014 01:52:55 Laurent Pinchart wrote:
> > >> On Friday 28 February 2014 16:37:08 Laurent Pinchart wrote:
> > >>> Hello Will,
> > >>>
> > >>> I've studied your arm-smmu driver as a base to write a Renesas IOMMU
> > >>> driver and found two small issues. Here are patches to fix them.
> > >>> Please bear with me if my understanding was incorrect and the patches
> > >>> wrong :-)
> > >>>
> > >>> Laurent Pinchart (2):
> > >>> iommu/arm-smmu: Replace list walk with platform driver data
> > >>> iommu/arm-smmu: Return 0 on unmap failure
> > >>>
> > >>> drivers/iommu/arm-smmu.c | 17 +++++------------
> > >>> 1 file changed, 5 insertions(+), 12 deletions(-)
> > >>
> > >> Do you plan to take these patches (or at least patch 2/2) in your tree
> > >> ? I can send a pull request to Joerg if you give me your acked-by.
> > >
> > > Marc, would you like to handle this, or would you prefer to wait until
> > > Will comes back ?
> >
> > Hi Laurent,
> >
> > Yup, I'll have a look and stash them in a temp tree. Given that Will
> > will be back in about a week, he will have the final say.
>
> I've already got the fix queued ("Return 0 on unmap failure") and plan to
> send it to Joerg this week.
Thank you.
> I think the other patch doesn't really add anything to the driver :)
Fair enough, it's your driver, so the decision is yours :-)
On a different but related topic, I've written an ipmmu-vmsa.c driver for a
Renesas IOMMU. The IP core has custom registers but uses VMSA-compatible page
tables. What would you think about sharing the page table management code
between the two drivers ? The biggest difference between the two
implementations is that I've hardcoded the long descriptor format, while you
have reused more system MMU macros that make the arm-smmu driver use 2 or 3
levels of page tables depending on whether LPAE is disabled or enabled.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-04-15 15:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 15:37 [PATCH 0/2] ARM SMMU fixes Laurent Pinchart
2014-02-28 15:37 ` [PATCH 1/2] iommu/arm-smmu: Replace list walk with platform driver data Laurent Pinchart
2014-02-28 16:38 ` Will Deacon
2014-03-02 17:59 ` Laurent Pinchart
2014-02-28 15:37 ` [PATCH 2/2] iommu/arm-smmu: Return 0 on unmap failure Laurent Pinchart
2014-02-28 16:39 ` Will Deacon
2014-04-02 23:52 ` [PATCH 0/2] ARM SMMU fixes Laurent Pinchart
2014-04-08 13:41 ` Laurent Pinchart
2014-04-08 13:57 ` Marc Zyngier
2014-04-14 16:58 ` Will Deacon
2014-04-15 15:55 ` Laurent Pinchart [this message]
2014-04-16 14:22 ` Will Deacon
2014-04-16 14:25 ` Laurent Pinchart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15544035.e9eK8n7TO4@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).