From: thunder.leizhen@huawei.com (leizhen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] iommu/arm-smmu: Add initial driver support for ARM SMMUv3 devices
Date: Wed, 27 May 2015 17:12:44 +0800 [thread overview]
Message-ID: <55658A8C.4020903@huawei.com> (raw)
In-Reply-To: <20150526161245.GR1565@arm.com>
On 2015/5/27 0:12, Will Deacon wrote:
> On Mon, May 25, 2015 at 03:07:17AM +0100, leizhen wrote:
>> On 2015/5/21 19:25, Will Deacon wrote:
>>> On Wed, May 13, 2015 at 09:33:19AM +0100, leizhen wrote:
>>>> If SMMU_IDR1.SIDSIZE = 32 really exist(or too big), we need dynamic choose
>>>> Lv2 table size(4K,16K,64K). Because Lv1 table maybe too big, and can not
>>>> be allocated by current API, a dts configuration should be added, like
>>>> lv1-table-base = <0x0 0x0>, and we use ioremap_cache get VA(maybe ioremap,
>>>> for non-coherent SMMU).
>>>>
>>>> Oh, I can do it after your patches upstreamed, because this problem maybe
>>>> only I met.
>>>
>>> I'll have a think about this and see what I can come up with for version
>>> 2 of the patch. I'd like to avoid adding additional properties to the DT
>>> until they're actually needed, though.
>>
>> OK. Will you support non-pci devices in patch version 2?
>
> I don't (yet) plan to support non-PCI devices, for two reasons:
>
> (1) The support should be based on top of Laurent's RFC series here:
>
> http://lists.infradead.org/pipermail/linux-arm-kernel/2015-May/343686.html
>
> which needs some review etc.
>
> (2) My simulator only has PCI endpoints
>
> Of course, if you have something that you can test with, then I'm more
> than happy to review patches adding this support providing that they're
> based on the series above.
OK. I'm so glad to do it.
>
> On the table front, my current v2 patch uses 16k level-2 tables allocated
> lazily (so each one has 256 entries and covers a single PCI bus). I've
> also capped the SIDSIZE to 21 for the moment, which means we get a 64k
> table there.
>
> Sound reasonable for the time being?
OK. My SIDSIZE is 25, I will also do this.
>
> Will
>
> .
>
next prev parent reply other threads:[~2015-05-27 9:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 18:00 [PATCH 0/3] iommu/arm-smmu: Add driver for ARM SMMUv3 devices Will Deacon
2015-05-08 18:00 ` [PATCH 1/3] Documentation: dt-bindings: Add device-tree binding for ARM SMMUv3 IOMMU Will Deacon
2015-05-08 18:00 ` [PATCH 2/3] iommu/arm-smmu: Add initial driver support for ARM SMMUv3 devices Will Deacon
2015-05-12 7:40 ` leizhen
2015-05-12 16:55 ` Will Deacon
2015-05-13 8:33 ` leizhen
2015-05-21 11:25 ` Will Deacon
2015-05-25 2:07 ` leizhen
2015-05-26 16:12 ` Will Deacon
2015-05-27 9:12 ` leizhen [this message]
2015-05-19 15:24 ` Joerg Roedel
2015-05-20 17:09 ` Will Deacon
2015-05-29 6:43 ` Joerg Roedel
2015-05-29 11:35 ` Robin Murphy
2015-05-29 14:40 ` Joerg Roedel
2015-06-01 9:40 ` Will Deacon
2015-06-02 7:39 ` Joerg Roedel
2015-06-02 9:47 ` Will Deacon
2015-06-02 18:43 ` Joerg Roedel
2015-05-08 18:00 ` [PATCH 3/3] drivers/vfio: Allow type-1 IOMMU instantiation on top of an ARM SMMUv3 Will Deacon
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=55658A8C.4020903@huawei.com \
--to=thunder.leizhen@huawei.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).