From: Zhou Wang <wangzhou1@hisilicon.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Jingoo Han <jg1.han@samsung.com>,
Pratyush Anand <pratyush.anand@gmail.com>,
Arnd Bergmann <arnd@arndb.de>, <gabriele.paoloni@huawei.com>,
<lorenzo.pieralisi@arm.com>, James Morse <james.morse@arm.com>,
<Liviu.Dudau@arm.com>, <linux-pci@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <yuanzhichang@hisilicon.com>,
<zhudacai@hisilicon.com>, <zhangjukuo@huawei.com>,
<qiuzhenfa@hisilicon.com>, <liudongdong3@huawei.com>,
<qiujiang@huawei.com>, <kangfenglong@huawei.com>,
<liguozhu@hisilicon.com>, Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v4 4/5] Documentation: DT: Add Hisilicon PCIe host binding
Date: Wed, 22 Jul 2015 10:50:52 +0800 [thread overview]
Message-ID: <55AF050C.1070105@hisilicon.com> (raw)
In-Reply-To: <20150721230205.GN21967@google.com>
On 2015/7/22 7:02, Bjorn Helgaas wrote:
> [+cc Rob]
>
> On Tue, Jul 21, 2015 at 02:48:42PM +0800, Zhou Wang wrote:
>> This patch adds related DTS binding document for Hisilicon PCIe host driver.
>>
>> Signed-off-by: Zhou Wang <wangzhou1@hisilicon.com>
>
> If I merge this via my tree, I'm looking for an ack from Arnd and/or Rob
> here.
>
>> ---
>> .../devicetree/bindings/pci/hisilicon-pcie.txt | 46 ++++++++++++++++++++++
>> 1 file changed, 46 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/pci/hisilicon-pcie.txt
>>
>> diff --git a/Documentation/devicetree/bindings/pci/hisilicon-pcie.txt b/Documentation/devicetree/bindings/pci/hisilicon-pcie.txt
>> new file mode 100644
>> index 0000000..6c9b827
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/pci/hisilicon-pcie.txt
>> @@ -0,0 +1,46 @@
>> +Hisilicon PCIe host bridge DT description
>
> Even the website at http://hisilicon.com isn't consistent, but there is
> some indication that the correct capitalization would be "HiSilicon".
> Since this is English text, feel free to capitalize it correctly here :)
>
Hi Bjorn,
I checked with related colleagues about this. It should be "HiSilicon" as
formal name. Thanks for pointing this :)
> Similarly, Synopsys seems to use "DesignWare," so I try to use that when
> it makes sense.
>
>> +Hisilicon PCIe host controller is based on Designware PCI core.
>> +It shares common functions with PCIe Designware core driver and inherits
>> +common properties defined in
>> +Documentation/devicetree/bindings/pci/designware-pci.txt.
>> +
>> +Additional properties are described here:
>> +
>> +Required properties:
>> +- compatible: Should contain "hisilicon,hip05-pcie".
>> +- reg: Should contain rc_dbi, subctrl, config registers location and length.
>> +- reg-names: Must include the following entries:
>> + "rc_dbi": controller configuration registers;
>> + "subctrl": whole PCIe hosts configuration registers;
>> + "config": PCIe configuration space registers.
>> +- msi-parent: Should be its_pcie which is an its receiving MSI interrupts.
>
> I guess "its" here is an abbreviation for something; if so, this would read
> better as "... which is an ITS receiving ..."
>
It is ITS(Interrupt Translation Service) in GIC v3. Will modify it.
>> +- port-id: Should be 0, 1, 2 or 3.
>> +
>> +Optional properties:
>> +- status: Either "ok" or "disabled".
>> +- dma-coherent: Present if dma operations are coherent.
>
> "if DMA operations"
>
Thanks, will modify this.
Best regards,
Zhou
>> +
>> +Example:
>> + pcie@0xb0080000 {
>> + compatible = "hisilicon,hip05-pcie", "snps,dw-pcie";
>> + reg = <0 0xb0080000 0 0x10000>, <0 0xb0000000 0 0x10000>,
>> + <0x220 0x00000000 0 0x2000>;
>> + reg-names = "rc_dbi", "subctrl", "config";
>> + bus-range = <0 15>;
>> + msi-parent = <&its_pcie>;
>> + #address-cells = <3>;
>> + #size-cells = <2>;
>> + device_type = "pci";
>> + dma-coherent;
>> + ranges = <0x82000000 0 0x00000000 0x220 0x00000000 0 0x10000000>;
>> + num-lanes = <8>;
>> + port-id = <1>;
>> + #interrupts-cells = <1>;
>> + interrupts-map-mask = <0xf800 0 0 7>;
>> + interrupts-map = <0x0 0 0 1 &mbigen_pcie 1 10
>> + 0x0 0 0 2 &mbigen_pcie 2 11
>> + 0x0 0 0 3 &mbigen_pcie 3 12
>> + 0x0 0 0 4 &mbigen_pcie 4 13>;
>> + status = "ok";
>> + };
>> --
>> 1.9.1
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> .
>
WARNING: multiple messages have this Message-ID (diff)
From: wangzhou1@hisilicon.com (Zhou Wang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 4/5] Documentation: DT: Add Hisilicon PCIe host binding
Date: Wed, 22 Jul 2015 10:50:52 +0800 [thread overview]
Message-ID: <55AF050C.1070105@hisilicon.com> (raw)
In-Reply-To: <20150721230205.GN21967@google.com>
On 2015/7/22 7:02, Bjorn Helgaas wrote:
> [+cc Rob]
>
> On Tue, Jul 21, 2015 at 02:48:42PM +0800, Zhou Wang wrote:
>> This patch adds related DTS binding document for Hisilicon PCIe host driver.
>>
>> Signed-off-by: Zhou Wang <wangzhou1@hisilicon.com>
>
> If I merge this via my tree, I'm looking for an ack from Arnd and/or Rob
> here.
>
>> ---
>> .../devicetree/bindings/pci/hisilicon-pcie.txt | 46 ++++++++++++++++++++++
>> 1 file changed, 46 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/pci/hisilicon-pcie.txt
>>
>> diff --git a/Documentation/devicetree/bindings/pci/hisilicon-pcie.txt b/Documentation/devicetree/bindings/pci/hisilicon-pcie.txt
>> new file mode 100644
>> index 0000000..6c9b827
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/pci/hisilicon-pcie.txt
>> @@ -0,0 +1,46 @@
>> +Hisilicon PCIe host bridge DT description
>
> Even the website at http://hisilicon.com isn't consistent, but there is
> some indication that the correct capitalization would be "HiSilicon".
> Since this is English text, feel free to capitalize it correctly here :)
>
Hi Bjorn,
I checked with related colleagues about this. It should be "HiSilicon" as
formal name. Thanks for pointing this :)
> Similarly, Synopsys seems to use "DesignWare," so I try to use that when
> it makes sense.
>
>> +Hisilicon PCIe host controller is based on Designware PCI core.
>> +It shares common functions with PCIe Designware core driver and inherits
>> +common properties defined in
>> +Documentation/devicetree/bindings/pci/designware-pci.txt.
>> +
>> +Additional properties are described here:
>> +
>> +Required properties:
>> +- compatible: Should contain "hisilicon,hip05-pcie".
>> +- reg: Should contain rc_dbi, subctrl, config registers location and length.
>> +- reg-names: Must include the following entries:
>> + "rc_dbi": controller configuration registers;
>> + "subctrl": whole PCIe hosts configuration registers;
>> + "config": PCIe configuration space registers.
>> +- msi-parent: Should be its_pcie which is an its receiving MSI interrupts.
>
> I guess "its" here is an abbreviation for something; if so, this would read
> better as "... which is an ITS receiving ..."
>
It is ITS(Interrupt Translation Service) in GIC v3. Will modify it.
>> +- port-id: Should be 0, 1, 2 or 3.
>> +
>> +Optional properties:
>> +- status: Either "ok" or "disabled".
>> +- dma-coherent: Present if dma operations are coherent.
>
> "if DMA operations"
>
Thanks, will modify this.
Best regards,
Zhou
>> +
>> +Example:
>> + pcie at 0xb0080000 {
>> + compatible = "hisilicon,hip05-pcie", "snps,dw-pcie";
>> + reg = <0 0xb0080000 0 0x10000>, <0 0xb0000000 0 0x10000>,
>> + <0x220 0x00000000 0 0x2000>;
>> + reg-names = "rc_dbi", "subctrl", "config";
>> + bus-range = <0 15>;
>> + msi-parent = <&its_pcie>;
>> + #address-cells = <3>;
>> + #size-cells = <2>;
>> + device_type = "pci";
>> + dma-coherent;
>> + ranges = <0x82000000 0 0x00000000 0x220 0x00000000 0 0x10000000>;
>> + num-lanes = <8>;
>> + port-id = <1>;
>> + #interrupts-cells = <1>;
>> + interrupts-map-mask = <0xf800 0 0 7>;
>> + interrupts-map = <0x0 0 0 1 &mbigen_pcie 1 10
>> + 0x0 0 0 2 &mbigen_pcie 2 11
>> + 0x0 0 0 3 &mbigen_pcie 3 12
>> + 0x0 0 0 4 &mbigen_pcie 4 13>;
>> + status = "ok";
>> + };
>> --
>> 1.9.1
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
>> the body of a message to majordomo at vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> .
>
WARNING: multiple messages have this Message-ID (diff)
From: Zhou Wang <wangzhou1-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>
To: Bjorn Helgaas <bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Cc: Jingoo Han <jg1.han-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>,
Pratyush Anand
<pratyush.anand-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
gabriele.paoloni-hv44wF8Li93QT0dZR+AlfA@public.gmane.org,
lorenzo.pieralisi-5wv7dgnIgG8@public.gmane.org,
James Morse <james.morse-5wv7dgnIgG8@public.gmane.org>,
Liviu.Dudau-5wv7dgnIgG8@public.gmane.org,
linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
yuanzhichang-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org,
zhudacai-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org,
zhangjukuo-hv44wF8Li93QT0dZR+AlfA@public.gmane.org,
qiuzhenfa-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org,
liudongdong3-hv44wF8Li93QT0dZR+AlfA@public.gmane.org,
qiujiang-hv44wF8Li93QT0dZR+AlfA@public.gmane.org,
kangfenglong-hv44wF8Li93QT0dZR+AlfA@public.gmane.org,
liguozhu-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org,
Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH v4 4/5] Documentation: DT: Add Hisilicon PCIe host binding
Date: Wed, 22 Jul 2015 10:50:52 +0800 [thread overview]
Message-ID: <55AF050C.1070105@hisilicon.com> (raw)
In-Reply-To: <20150721230205.GN21967-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
On 2015/7/22 7:02, Bjorn Helgaas wrote:
> [+cc Rob]
>
> On Tue, Jul 21, 2015 at 02:48:42PM +0800, Zhou Wang wrote:
>> This patch adds related DTS binding document for Hisilicon PCIe host driver.
>>
>> Signed-off-by: Zhou Wang <wangzhou1-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>
>
> If I merge this via my tree, I'm looking for an ack from Arnd and/or Rob
> here.
>
>> ---
>> .../devicetree/bindings/pci/hisilicon-pcie.txt | 46 ++++++++++++++++++++++
>> 1 file changed, 46 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/pci/hisilicon-pcie.txt
>>
>> diff --git a/Documentation/devicetree/bindings/pci/hisilicon-pcie.txt b/Documentation/devicetree/bindings/pci/hisilicon-pcie.txt
>> new file mode 100644
>> index 0000000..6c9b827
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/pci/hisilicon-pcie.txt
>> @@ -0,0 +1,46 @@
>> +Hisilicon PCIe host bridge DT description
>
> Even the website at http://hisilicon.com isn't consistent, but there is
> some indication that the correct capitalization would be "HiSilicon".
> Since this is English text, feel free to capitalize it correctly here :)
>
Hi Bjorn,
I checked with related colleagues about this. It should be "HiSilicon" as
formal name. Thanks for pointing this :)
> Similarly, Synopsys seems to use "DesignWare," so I try to use that when
> it makes sense.
>
>> +Hisilicon PCIe host controller is based on Designware PCI core.
>> +It shares common functions with PCIe Designware core driver and inherits
>> +common properties defined in
>> +Documentation/devicetree/bindings/pci/designware-pci.txt.
>> +
>> +Additional properties are described here:
>> +
>> +Required properties:
>> +- compatible: Should contain "hisilicon,hip05-pcie".
>> +- reg: Should contain rc_dbi, subctrl, config registers location and length.
>> +- reg-names: Must include the following entries:
>> + "rc_dbi": controller configuration registers;
>> + "subctrl": whole PCIe hosts configuration registers;
>> + "config": PCIe configuration space registers.
>> +- msi-parent: Should be its_pcie which is an its receiving MSI interrupts.
>
> I guess "its" here is an abbreviation for something; if so, this would read
> better as "... which is an ITS receiving ..."
>
It is ITS(Interrupt Translation Service) in GIC v3. Will modify it.
>> +- port-id: Should be 0, 1, 2 or 3.
>> +
>> +Optional properties:
>> +- status: Either "ok" or "disabled".
>> +- dma-coherent: Present if dma operations are coherent.
>
> "if DMA operations"
>
Thanks, will modify this.
Best regards,
Zhou
>> +
>> +Example:
>> + pcie@0xb0080000 {
>> + compatible = "hisilicon,hip05-pcie", "snps,dw-pcie";
>> + reg = <0 0xb0080000 0 0x10000>, <0 0xb0000000 0 0x10000>,
>> + <0x220 0x00000000 0 0x2000>;
>> + reg-names = "rc_dbi", "subctrl", "config";
>> + bus-range = <0 15>;
>> + msi-parent = <&its_pcie>;
>> + #address-cells = <3>;
>> + #size-cells = <2>;
>> + device_type = "pci";
>> + dma-coherent;
>> + ranges = <0x82000000 0 0x00000000 0x220 0x00000000 0 0x10000000>;
>> + num-lanes = <8>;
>> + port-id = <1>;
>> + #interrupts-cells = <1>;
>> + interrupts-map-mask = <0xf800 0 0 7>;
>> + interrupts-map = <0x0 0 0 1 &mbigen_pcie 1 10
>> + 0x0 0 0 2 &mbigen_pcie 2 11
>> + 0x0 0 0 3 &mbigen_pcie 3 12
>> + 0x0 0 0 4 &mbigen_pcie 4 13>;
>> + status = "ok";
>> + };
>> --
>> 1.9.1
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
>> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> .
>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-07-22 2:51 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 6:48 [PATCH v4 0/5] PCI: hisi: Add PCIe host support for Hisilicon Soc Hip05 Zhou Wang
2015-07-21 6:48 ` Zhou Wang
2015-07-21 6:48 ` Zhou Wang
2015-07-21 6:48 ` [PATCH v4 1/5] ARM/PCI: remove align_resource in pci_sys_data Zhou Wang
2015-07-21 6:48 ` Zhou Wang
2015-07-21 6:48 ` Zhou Wang
2015-07-21 22:44 ` Bjorn Helgaas
2015-07-21 22:44 ` Bjorn Helgaas
2015-07-22 2:00 ` Zhou Wang
2015-07-22 2:00 ` Zhou Wang
2015-07-22 2:00 ` Zhou Wang
2015-07-23 18:06 ` Lorenzo Pieralisi
2015-07-23 18:06 ` Lorenzo Pieralisi
2015-07-23 18:06 ` Lorenzo Pieralisi
2015-07-21 6:48 ` [PATCH v4 2/5] PCI: designware: Add ARM64 support Zhou Wang
2015-07-21 6:48 ` Zhou Wang
2015-07-21 6:48 ` Zhou Wang
2015-07-21 6:48 ` [PATCH v4 3/5] PCI: hisi: Add PCIe host support for Hisilicon Soc Hip05 Zhou Wang
2015-07-21 6:48 ` Zhou Wang
2015-07-21 6:48 ` Zhou Wang
2015-07-21 22:37 ` Bjorn Helgaas
2015-07-21 22:37 ` Bjorn Helgaas
2015-07-22 2:33 ` Zhou Wang
2015-07-22 2:33 ` Zhou Wang
2015-07-22 2:33 ` Zhou Wang
2015-07-21 6:48 ` [PATCH v4 4/5] Documentation: DT: Add Hisilicon PCIe host binding Zhou Wang
2015-07-21 6:48 ` Zhou Wang
2015-07-21 6:48 ` Zhou Wang
2015-07-21 23:02 ` Bjorn Helgaas
2015-07-21 23:02 ` Bjorn Helgaas
2015-07-22 2:50 ` Zhou Wang [this message]
2015-07-22 2:50 ` Zhou Wang
2015-07-22 2:50 ` Zhou Wang
2015-07-21 6:48 ` [PATCH v4 5/5] MAINTAINERS: Add pcie-hisi maintainer Zhou Wang
2015-07-21 6:48 ` Zhou Wang
2015-07-21 6:48 ` Zhou Wang
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=55AF050C.1070105@hisilicon.com \
--to=wangzhou1@hisilicon.com \
--cc=Liviu.Dudau@arm.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=gabriele.paoloni@huawei.com \
--cc=james.morse@arm.com \
--cc=jg1.han@samsung.com \
--cc=kangfenglong@huawei.com \
--cc=liguozhu@hisilicon.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=liudongdong3@huawei.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=pratyush.anand@gmail.com \
--cc=qiujiang@huawei.com \
--cc=qiuzhenfa@hisilicon.com \
--cc=robh@kernel.org \
--cc=yuanzhichang@hisilicon.com \
--cc=zhangjukuo@huawei.com \
--cc=zhudacai@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 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.