From: joro@8bytes.org (Joerg Roedel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1] iommu/rockchip: reconstruct to support multi slaves
Date: Fri, 29 Jan 2016 12:26:45 +0100 [thread overview]
Message-ID: <20160129112645.GC4204@8bytes.org> (raw)
In-Reply-To: <1453186980-21055-1-git-send-email-zhengsq@rock-chips.com>
On Tue, Jan 19, 2016 at 03:03:00PM +0800, Shunqian Zheng wrote:
> From: ZhengShunQian <zhengsq@rock-chips.com>
>
> There are some IPs, such as video encoder/decoder, contains 2 slave iommus,
> one for reading and the other for writing. They share the same irq and
> clock with master.
>
> This patch reconstructs to support this case by making them share the same
> Page Directory, Page Tables and even the register operations.
> That means every instruction to the reading MMU registers would be
> duplicated to the writing MMU and vice versa.
>
> Signed-off-by: ZhengShunQian <zhengsq@rock-chips.com>
> ---
> drivers/iommu/rockchip-iommu.c | 214 ++++++++++++++++++++++++++---------------
> 1 file changed, 135 insertions(+), 79 deletions(-)
Applied, thanks.
prev parent reply other threads:[~2016-01-29 11:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 7:03 [PATCH v1] iommu/rockchip: reconstruct to support multi slaves Shunqian Zheng
2016-01-29 11:26 ` Joerg Roedel [this message]
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=20160129112645.GC4204@8bytes.org \
--to=joro@8bytes.org \
--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).