From: Simon Horman <horms@verge.net.au>
To: Jacopo Mondi <jacopo+renesas@jmondi.org>
Cc: geert@linux-m68k.org, magnus.damm@gmail.com,
yoshihiro.shimoda.uh@renesas.com, joro@8bytes.org,
linux-renesas-soc@vger.kernel.org,
iommu@lists.linux-foundation.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [RESEND 0/6] iommu: ipmmu-vmsa: Add more Gen3 SoCs support
Date: Wed, 20 Jun 2018 13:29:14 +0200 [thread overview]
Message-ID: <20180620112909.gzbdpj2kwcehebnx@verge.net.au> (raw)
In-Reply-To: <1528973306-7962-1-git-send-email-jacopo+renesas@jmondi.org>
[CC Alex Williamson]
On Thu, Jun 14, 2018 at 12:48:20PM +0200, Jacopo Mondi wrote:
> Hello,
> this series collects patches sent to mailing lists in late 2017 to add
> support for a number of R-Car Gen3 SoCs to the ipmmu-vmsa driver.
>
> Part of the series these patches were part of went in through Alex Williamson
> tree and are now included in v4.17.
>
> These patches have not yet been collected, and need to be rebased on v4.17,
> and this what this series serves for.
>
> The series:
> - Increses the micro-TLB size to 48bits to accomodate newer SoCs
> - Adds support for M3-N, M3-W, V3-M and E3 to ipmmu-vmsa driver
> - Documents M3-N, V3H and E3 device tree bindings
>
> All patches have been acked/reviewed by, if nothing big happens they should
> be ready to be collected.
All patches:
Reviewed-by: Simon Horman <horms+renesas@verge.net.au>
Joerg, Alex,
I'd be most grateful if we could find a way for these patches to progress
into mainline.
>
> Thanks
> j
>
> Jacopo Mondi (2):
> dt-bindings: iommu/ipmmu-vmsa: Add R-Car M3-N (R8A77965)
> iommu/ipmmu-vmsa: Hook up R8A77965 DT matching code
>
> Magnus Damm (3):
> iommu/ipmmu-vmsa: Increase maximum micro-TLBS to 48
> iommu/ipmmu-vmsa: Hook up r8a7796 DT matching code
> iommu/ipmmu-vmsa: Document R-Car V3H and E3 IPMMU DT bindings
>
> Simon Horman (1):
> iommu/ipmmu-vmsa: Hook up r8a779(70|95) DT matching code
>
> .../bindings/iommu/renesas,ipmmu-vmsa.txt | 3 ++
> drivers/iommu/ipmmu-vmsa.c | 38 ++++++++++++++++++----
> 2 files changed, 34 insertions(+), 7 deletions(-)
>
> --
> 2.7.4
>
next prev parent reply other threads:[~2018-06-20 11:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 10:48 Jacopo Mondi
2018-06-14 10:48 ` [RESEND 1/6] iommu/ipmmu-vmsa: Increase maximum micro-TLBS to 48 Jacopo Mondi
2018-06-14 10:48 ` [RESEND 2/6] iommu/ipmmu-vmsa: Hook up r8a7796 DT matching code Jacopo Mondi
2018-06-14 10:48 ` [RESEND 3/6] iommu/ipmmu-vmsa: Hook up r8a779(70|95) " Jacopo Mondi
2018-06-14 10:48 ` [RESEND 4/6] dt-bindings: iommu/ipmmu-vmsa: Add R-Car M3-N (R8A77965) Jacopo Mondi
2018-06-14 10:48 ` [RESEND 5/6] iommu/ipmmu-vmsa: Hook up R8A77965 DT matching code Jacopo Mondi
2018-06-14 10:48 ` [RESEND 6/6] iommu/ipmmu-vmsa: Document R-Car V3H and E3 IPMMU DT bindings Jacopo Mondi
2018-06-20 11:29 ` Simon Horman [this message]
2018-07-06 12:12 ` [RESEND 0/6] iommu: ipmmu-vmsa: Add more Gen3 SoCs support Joerg Roedel
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=20180620112909.gzbdpj2kwcehebnx@verge.net.au \
--to=horms@verge.net.au \
--cc=alex.williamson@redhat.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jacopo+renesas@jmondi.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=yoshihiro.shimoda.uh@renesas.com \
/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
all inboxes | Powered by JetHome®