From: Rob Herring <robh@kernel.org>
To: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Mark Rutland <mark.rutland@arm.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Masami Hiramatsu <masami.hiramatsu@linaro.org>,
Jassi Brar <jaswinder.singh@linaro.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: PCI: add UniPhier PCIe host controller description
Date: Tue, 25 Sep 2018 15:55:02 -0500 [thread overview]
Message-ID: <20180925205502.GA12949@bogus> (raw)
In-Reply-To: <1536226832-5089-2-git-send-email-hayashi.kunihiko@socionext.com>
On Thu, Sep 06, 2018 at 06:40:31PM +0900, Kunihiko Hayashi wrote:
> Add DT bindings for PCIe controller implemented in UniPhier SoCs when
> configured in Root Complex (host) mode. This controller is based on
> the DesignWare PCIe core.
>
> Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
> ---
> .../devicetree/bindings/pci/uniphier-pcie.txt | 78 ++++++++++++++++++++++
> 1 file changed, 78 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/pci/uniphier-pcie.txt
>
> diff --git a/Documentation/devicetree/bindings/pci/uniphier-pcie.txt b/Documentation/devicetree/bindings/pci/uniphier-pcie.txt
> new file mode 100644
> index 0000000..a34e167
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/pci/uniphier-pcie.txt
> @@ -0,0 +1,78 @@
> +Socionext UniPhier PCIe host controller bindings
> +
> +This describes the devicetree bindings for PCIe host controller implemented
> +on Socionext UniPhier SoCs.
> +
> +UniPhier PCIe host controller is based on the Synopsys DesignWare PCI core.
> +It shares common functions with the PCIe DesignWare core driver and inherits
> +common properties defined in
> +Documentation/devicetree/bindings/pci/designware-pcie.txt.
> +
> +Required properties:
> +- compatible: Should be "socionext,uniphier-pcie".
> +- reg: Specifies offset and length of the register set for the device.
> + According to the reg-names, appropriate register sets are required.
> +- reg-names: Must include the following entries:
> + "dbi" - controller configuration registers
> + "link" - SoC-specific glue layer registers
> + "config" - PCIe configuration space
> +- clocks: A phandle to the clock gate for PCIe glue layer including
> + the host controller.
> +- resets: A phandle to the reset line for PCIe glue layer including
> + the host controller.
> +- interrupts: A list of interrupt specifiers. According to the
> + interrupt-names, appropriate interrupts are required.
> +- interrupt-names: Must include the following entries:
> + "dma" - DMA interrupt
> + "msi" - MSI interrupt
> + "intx" - Legacy INTA/B/C/D interrupt
> +
> +Optional properties:
> +- phys: A phandle to generic PCIe PHY. According to the phy-names, appropriate
> + phys are required.
> +- phy-names: Must be "pcie-phy".
> +
> +Required sub-node:
> +- interrupt-controller: Specifies interrupt controller for legacy PCI
> + interrupts. The node name isn't important.
No, it is important.
With that sentence removed,
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2018-09-25 20:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 9:40 [PATCH v2 0/2] add new UniPhier PCIe host driver Kunihiko Hayashi
2018-09-06 9:40 ` [PATCH v2 1/2] dt-bindings: PCI: add UniPhier PCIe host controller description Kunihiko Hayashi
2018-09-25 20:55 ` Rob Herring [this message]
2018-09-26 12:33 ` Kunihiko Hayashi
2018-09-06 9:40 ` [PATCH v2 2/2] PCI: controller: dwc: add UniPhier PCIe host controller support Kunihiko Hayashi
2018-09-25 16:14 ` Lorenzo Pieralisi
2018-09-25 17:53 ` Gustavo Pimentel
2018-09-26 12:31 ` Kunihiko Hayashi
2018-09-27 7:44 ` Kunihiko Hayashi
2018-09-28 11:06 ` Lorenzo Pieralisi
2018-09-28 13:17 ` Marc Zyngier
2018-09-28 15:43 ` Lorenzo Pieralisi
2018-10-08 5:45 ` Kishon Vijay Abraham I
2018-10-08 14:32 ` Lorenzo Pieralisi
2018-10-12 10:50 ` Kunihiko Hayashi
2018-10-01 10:06 ` Lorenzo Pieralisi
2018-10-01 11:06 ` Kunihiko Hayashi
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=20180925205502.GA12949@bogus \
--to=robh@kernel.org \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=jaswinder.singh@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=masami.hiramatsu@linaro.org \
--cc=yamada.masahiro@socionext.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).