From: thunder.leizhen@huawei•com (leizhen)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH RFC v1 0/2] Add support for Hisilicon SMMU architecture
Date: Fri, 6 Jun 2014 08:21:05 +0800 [thread overview]
Message-ID: <53910971.2010908@huawei.com> (raw)
In-Reply-To: <20140605152140.GA31564@leverpostej>
OK, thanks for your suggestion, I will adjust my code as soon as possible.
On 2014/6/5 23:21, Mark Rutland wrote:
> On Thu, Jun 05, 2014 at 02:37:08PM +0100, Zhen Lei wrote:
>> This driver is base on arm_smmu.c, beause of hisilicon smmu-v1 is similar to
>> arm-smmu, some code can be direct reused. for example: map and unmap, device
>> tree configuration, and the software framework. Somebody may doubted: why not
>> strip the share code in one file, and put hardware-dependent part into other
>> files? Yeah, it's right. But now, in order to make the code flow clearly, just
>> put all hisilicon smmu driver code in hisi_smmu.c.If this driver is acceptable,
>> I will update and submit a revised verion.
>
> This does not make the code flow clearer. If anything this makes it
> harder to review the series, because it's not clear what the delta from
> the existing ARM SMMU driver is.
>
> No-one is going to be happy merging a redundant copy of (portions of)
> the existing ARM SMMU driver. Whatever gets merged will look very
> different due to the refactoring required to remedy that, so there's
> almost no point reviewing this in any depth until that's sorted out.
>
> Mark.
>
>>
>> Zhen Lei (2):
>> documentation/iommu: Add description of Hisilicon System MMU binding
>> iommu/hisilicon: Add support for Hisilicon Ltd. System MMU
>> architecture
>>
>> .../devicetree/bindings/iommu/hisilicon,smmu.txt | 70 +
>> drivers/iommu/Kconfig | 11 +
>> drivers/iommu/Makefile | 1 +
>> drivers/iommu/hisi-smmu.c | 1686 ++++++++++++++++++++
>> 4 files changed, 1768 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/iommu/hisilicon,smmu.txt
>> create mode 100644 drivers/iommu/hisi-smmu.c
>>
>> --
>> 1.8.0
>>
>>
>>
>> _______________________________________________
>> linux-arm-kernel mailing list
>> linux-arm-kernel at lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>>
>
> .
>
prev parent reply other threads:[~2014-06-06 0:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 13:37 [PATCH RFC v1 0/2] Add support for Hisilicon SMMU architecture Zhen Lei
2014-06-05 13:37 ` [PATCH RFC v1 1/2] documentation/iommu: Add description of Hisilicon System MMU binding Zhen Lei
2014-06-05 15:26 ` Mark Rutland
2014-06-06 6:48 ` Arnd Bergmann
2014-06-06 11:07 ` Dave Martin
2014-06-11 8:12 ` leizhen
2014-06-16 16:26 ` Will Deacon
2014-06-16 16:42 ` Arnd Bergmann
2014-06-16 16:45 ` Will Deacon
2014-06-16 17:25 ` Arnd Bergmann
2014-06-16 18:26 ` Will Deacon
2014-06-17 7:14 ` Arnd Bergmann
2014-06-17 11:49 ` Thierry Reding
2014-06-18 11:10 ` Varun Sethi
2014-06-18 12:31 ` Will Deacon
2014-06-20 9:54 ` Varun Sethi
2014-06-20 17:49 ` Will Deacon
2014-06-20 18:57 ` Varun Sethi
2014-06-24 14:30 ` Will Deacon
2014-06-17 7:57 ` leizhen
2014-06-16 16:44 ` Arnd Bergmann
2014-06-05 13:37 ` [PATCH RFC v1 2/2] iommu/hisilicon: Add support for Hisilicon Ltd. System MMU architecture Zhen Lei
2014-06-05 15:21 ` [PATCH RFC v1 0/2] Add support for Hisilicon SMMU architecture Mark Rutland
2014-06-06 0:21 ` leizhen [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=53910971.2010908@huawei.com \
--to=thunder.leizhen@huawei$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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