From: chenfeng <puck.chen@hisilicon.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: <yudongbin@hisilicon.com>, <saberlily.xia@hisilicon.com>,
<suzhuangluan@hisilicon.com>, <kong.kongxinwei@hisilicon.com>,
<xuyiping@hisilicon.com>, <z.liuxinliang@hisilicon.com>,
<puck.chen@aliyun.com>, <weidong2@hisilicon.com>,
<w.f@huawei.com>, <joro@8bytes.org>, <robh+dt@kernel.org>,
<pawel.moll@arm.com>, <ijc+devicetree@hellion.org.uk>,
<galak@codeaurora.org>, <linux-kernel@vger.kernel.org>,
<xuwei5@hisilicon.com>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <qijiwen@hisilicon.com>,
<peter.panshilin@hisilicon.com>, <dan.zhao@hisilicon.com>,
<linuxarm@huawei.com>
Subject: Re: [PATCH V2 1/3] Documentation for system mmu in hi6220 platform.
Date: Tue, 20 Oct 2015 20:33:35 +0800 [thread overview]
Message-ID: <5626349F.3040108@hisilicon.com> (raw)
In-Reply-To: <20151020103402.GB968@leverpostej>
Mark, thanks very much.
On 2015/10/20 18:34, Mark Rutland wrote:
> On Tue, Oct 20, 2015 at 04:45:22PM +0800, Chen Feng wrote:
>> docs: iommu: Documentation for smmu in hi6220 SoC.
>>
>> Signed-off-by: Chen Feng <puck.chen@hisilicon.com>
>> Signed-off-by: Yu Dongbin <yudongbin@hisilicon.com>
>> ---
>> .../bindings/iommu/hisi,hi6220-iommu.txt | 52 ++++++++++++++++++++++
>> 1 file changed, 52 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/iommu/hisi,hi6220-iommu.txt
>>
>> diff --git a/Documentation/devicetree/bindings/iommu/hisi,hi6220-iommu.txt b/Documentation/devicetree/bindings/iommu/hisi,hi6220-iommu.txt
>> new file mode 100644
>> index 0000000..93e0701
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/iommu/hisi,hi6220-iommu.txt
>> @@ -0,0 +1,52 @@
>> +Hi6220 SoC SMMU Device Driver devicetree document
>> +=======================================================================
>> +The Architecture of SMMU on Hi6220 SoC:
>> +
>> + +------------------------------------------------------------------+
>> + | |
>> + | +---------+ +--------+ +-------------+ +-------+ |
>> + | | ADE | | ISP | | V/J codec | | G3D | |
>> + | +----|----+ +---|----+ +------|------+ +---|---| |
>> + | | | | | |
>> + | ---------v-----------v--------------v--------------v----- |
>> + | Media Bus |
>> + | --------------------------------|---------------|-------- |
>> + | | | |
>> + | +---v---------------v--------+ |
>> + | | SMMU | |
>> + | +----------|---------|-------+ |
>> + | | | |
>> + +--------------------------------------------|---------|-----------+
>> + | |
>> + +------------v---------v-----------+
>> + | DDRC |
>> + +----------------------------------+
>> +
>> +Note:
>> +The media system shared the same smmu IP. to access DDR memory. And all
>
> Nit: s/IP./IP/
>
>> +media IP used the same page table.
>> +
>> +Below binding describes the system mmu for media system in hi6220 platform
>> +
>> +Required properties:
>> +- compatible: Should be "hisilicon,hi6220-smmu" example:
>> + compatible = "hisilicon,hi6220-smmu";
>
> No need for the example here.
>
> Just say:
>
> - compatible: should contain "hisilicon,hi6220-smmu".
>
ok,
>> +- reg: A tuple of base address and size of System MMU registers.
>> +- interrupts: An interrupt specifier for interrupt signal of System MMU.
>> +- clocks: The clock used for smmu IP.
>> +- clock-names: The name to enable clock with clock framework.
>
> The description of clocks and clock-names makes no sense.
>
> You must define the exact set of names you expect, and the relationship
> between clocks and clock names. e.g.
>
ok
> - clocks: a list of phandle + clock-specifier pairs, one for each entry
> in clock-names
>
> - clock-names: should contain:
> * "smmu_clk"
> * "media_sc_clk"
> * "smmu_peri_clk"
>
>> +- #iommu-cells: The iommu-cells should be 1 for muti-master to use.
>
> s/muti/multi/
>
> You must define what that one cell corresponds to in the hardware.
>
> Thanks,
> Mark.
>
I will change this next version.
>> +
>> +Examples:
>> + smmu@f4210000 {
>> + compatible = "hisilicon,hi6220-smmu";
>> + reg = <0x0 0xf4210000 0x0 0x1000>;
>> + interrupts = <GIC_SPI 113 IRQ_TYPE_LEVEL_HIGH>;
>> + clocks = <&sys_ctrl HI6220_MMU_CLK>,
>> + <&media_ctrl HI6220_MED_MMU>,
>> + <&sys_ctrl HI6220_MEDIA_PLL_SRC>;
>> + clock-names = "smmu_clk",
>> + "media_sc_clk",
>> + "smmu_peri_clk";
>> + #iommu-cells = <1>;
>> + };
>> --
>> 1.9.1
>>
>
> .
>
next prev parent reply other threads:[~2015-10-20 12:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 8:45 [PATCH V2 1/3] Documentation for system mmu in hi6220 platform Chen Feng
2015-10-20 8:45 ` [PATCH V2 2/3] Add iommu driver for hi6220 SoC platform Chen Feng
2015-10-20 15:02 ` Robin Murphy
2015-10-21 1:56 ` chenfeng
2015-10-23 9:10 ` chenfeng
2015-10-20 8:45 ` [PATCH V2 3/3] Add dts node for smmu on hi6220 SoC Chen Feng
2015-10-20 9:00 ` Arnd Bergmann
2015-10-20 10:17 ` chenfeng
2015-10-20 10:34 ` [PATCH V2 1/3] Documentation for system mmu in hi6220 platform Mark Rutland
2015-10-20 12:33 ` chenfeng [this message]
2015-10-22 1:15 ` Rob Herring
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=5626349F.3040108@hisilicon.com \
--to=puck.chen@hisilicon.com \
--cc=dan.zhao@hisilicon.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=joro@8bytes.org \
--cc=kong.kongxinwei@hisilicon.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=peter.panshilin@hisilicon.com \
--cc=puck.chen@aliyun.com \
--cc=qijiwen@hisilicon.com \
--cc=robh+dt@kernel.org \
--cc=saberlily.xia@hisilicon.com \
--cc=suzhuangluan@hisilicon.com \
--cc=w.f@huawei.com \
--cc=weidong2@hisilicon.com \
--cc=xuwei5@hisilicon.com \
--cc=xuyiping@hisilicon.com \
--cc=yudongbin@hisilicon.com \
--cc=z.liuxinliang@hisilicon.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;
as well as URLs for NNTP newsgroup(s).