From: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
To: Peng Fan <van.freenix-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: Question about arm smmu
Date: Wed, 4 Nov 2015 14:43:08 +0000 [thread overview]
Message-ID: <20151104144308.GQ5405@arm.com> (raw)
In-Reply-To: <20151104134439.GA4022-12w76u+6CWdQVMFFLWfSwA@public.gmane.org>
On Wed, Nov 04, 2015 at 09:44:40PM +0800, Peng Fan wrote:
> Hi Will,
Hello,
> I am trying to enable SMMU(mmu500) on an platform.
> My platform support only 32 SIDs, but it have more than 100 masters.
> So I need to let different masters share one SID. I read current
> arm-smmu.c, but it needs each master has unique SID. Do you have
> some suggestions about how to let different masters sharing one
> SID?
We can achieve that using iommu_groups, but then we need a way to
describe those groups in the device-tree, as opposed to putting
each device into its own group like we do at present. Robin (CC'd) had
some work-in-progress for this, iirc.
> On my platform, SID can be dynamically programmed. So I can program
> DMA0 and DMA1 using one SID, saying 0x5. But I do not have a good
> idea how to support this use case in arm-smmu.c driver.
I think we've have the firmware allocating the SIDs, then describing
the grouping to Linux in the device-tree.
Will
next prev parent reply other threads:[~2015-11-04 14:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 13:44 Question about arm smmu Peng Fan
[not found] ` <20151104134439.GA4022-12w76u+6CWdQVMFFLWfSwA@public.gmane.org>
2015-11-04 14:43 ` Will Deacon [this message]
[not found] ` <20151104144308.GQ5405-5wv7dgnIgG8@public.gmane.org>
2015-11-04 15:31 ` Robin Murphy
[not found] ` <563A24EB.6090106-5wv7dgnIgG8@public.gmane.org>
2015-11-05 2:41 ` Peng Fan
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=20151104144308.GQ5405@arm.com \
--to=will.deacon-5wv7dgnigg8@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=van.freenix-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.