From: Rob Herring <robh@kernel.org>
To: Christian Bruel <christian.bruel@foss.st.com>
Cc: lpieralisi@kernel.org, kw@linux.com,
manivannan.sadhasivam@linaro.org, bhelgaas@google.com,
krzk+dt@kernel.org, conor+dt@kernel.org,
mcoquelin.stm32@gmail.com, alexandre.torgue@foss.st.com,
p.zabel@pengutronix.de, cassel@kernel.org,
quic_schintav@quicinc.com, fabrice.gasnier@foss.st.com,
linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/5] dt-bindings: PCI: Add STM32MP25 PCIe endpoint bindings
Date: Fri, 15 Nov 2024 10:39:41 -0600 [thread overview]
Message-ID: <20241115163941.GA3324312-robh@kernel.org> (raw)
In-Reply-To: <20241112161925.999196-4-christian.bruel@foss.st.com>
On Tue, Nov 12, 2024 at 05:19:23PM +0100, Christian Bruel wrote:
> STM32MP25 PCIe Controller is based on the DesignWare core configured as
> end point mode from the SYSCFG register.
>
> Signed-off-by: Christian Bruel <christian.bruel@foss.st.com>
> ---
> .../bindings/pci/st,stm32-pcie-ep.yaml | 97 +++++++++++++++++++
> 1 file changed, 97 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/pci/st,stm32-pcie-ep.yaml
>
> diff --git a/Documentation/devicetree/bindings/pci/st,stm32-pcie-ep.yaml b/Documentation/devicetree/bindings/pci/st,stm32-pcie-ep.yaml
> new file mode 100644
> index 000000000000..f0d215982794
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/pci/st,stm32-pcie-ep.yaml
> @@ -0,0 +1,97 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/pci/st,stm32-pcie-ep.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: STM32MP25 PCIe endpoint driver
> +
> +maintainers:
> + - Christian Bruel <christian.bruel@foss.st.com>
> +
> +description:
> + PCIe endpoint controller based on the Synopsys DesignWare PCIe core.
> +
> +allOf:
> + - $ref: /schemas/pci/snps,dw-pcie-common.yaml#
snps,dw-pcie-ep.yaml
> +
> +properties:
> + compatible:
> + const: st,stm32mp25-pcie-ep
> +
> + reg:
> + items:
> + - description: Data Bus Interface (DBI) registers.
> + - description: PCIe configuration registers.
> +
> + reg-names:
> + items:
> + - const: dbi
> + - const: addr_space
> +
> + clocks:
> + maxItems: 1
> + description: PCIe system clock
> +
> + clock-names:
> + const: core
> +
> + resets:
> + maxItems: 1
> +
> + reset-names:
> + const: core
> +
> + phys:
> + maxItems: 1
> +
> + phy-names:
> + const: pcie-phy
> +
> + reset-gpios:
> + description: GPIO controlled connection to PERST# signal
> + maxItems: 1
> +
> + access-controllers:
> + maxItems: 1
> +
> + power-domains:
> + maxItems: 1
All these properties common between RC and EP modes should be in
a shared schema.
> +
> +required:
> + - resets
> + - reset-names
> + - clocks
> + - clock-names
> + - phys
> + - phy-names
> + - reset-gpios
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/clock/st,stm32mp25-rcc.h>
> + #include <dt-bindings/gpio/gpio.h>
> + #include <dt-bindings/phy/phy.h>
> + #include <dt-bindings/reset/st,stm32mp25-rcc.h>
> +
> + pcie-ep@48400000 {
> + compatible = "st,stm32mp25-pcie-ep";
> + num-lanes = <1>;
> + reg = <0x48400000 0x400000>,
> + <0x10000000 0x8000000>;
> + reg-names = "dbi", "addr_space";
> + clocks = <&rcc CK_BUS_PCIE>;
> + clock-names = "core";
> + phys = <&combophy PHY_TYPE_PCIE>;
> + phy-names = "pcie-phy";
> + resets = <&rcc PCIE_R>;
> + reset-names = "core";
> + pinctrl-names = "default", "init";
> + pinctrl-0 = <&pcie_pins_a>;
> + pinctrl-1 = <&pcie_init_pins_a>;
> + reset-gpios = <&gpioj 8 GPIO_ACTIVE_LOW>;
> + power-domains = <&CLUSTER_PD>;
> + access-controllers = <&rifsc 68>;
> + };
> --
> 2.34.1
>
next prev parent reply other threads:[~2024-11-15 16:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 16:19 [PATCH 0/5] Add STM32MP25 PCIe drivers Christian Bruel
2024-11-12 16:19 ` [PATCH 1/5] dt-bindings: PCI: Add STM32MP25 PCIe root complex bindings Christian Bruel
2024-11-12 18:28 ` Bjorn Helgaas
2024-11-15 8:27 ` Christian Bruel
2024-11-15 16:36 ` Rob Herring
2024-11-25 15:23 ` Christian Bruel
2024-11-12 16:19 ` [PATCH 2/5] PCI: stm32: Add PCIe host support for STM32MP25 Christian Bruel
2024-11-12 19:32 ` Bjorn Helgaas
2024-11-25 15:00 ` Christian Bruel
2024-11-12 16:19 ` [PATCH 3/5] dt-bindings: PCI: Add STM32MP25 PCIe endpoint bindings Christian Bruel
2024-11-15 16:39 ` Rob Herring [this message]
2024-11-12 16:19 ` [PATCH 4/5] PCI: stm32: Add PCIe endpoint support for STM32MP25 Christian Bruel
2024-11-12 20:38 ` Bjorn Helgaas
2024-11-25 15:28 ` Christian Bruel
2024-11-12 16:19 ` [PATCH 5/5] MAINTAINERS: add entry for ST STM32MP25 PCIe drivers Christian Bruel
2024-11-12 20:39 ` Bjorn Helgaas
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=20241115163941.GA3324312-robh@kernel.org \
--to=robh@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=christian.bruel@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fabrice.gasnier@foss.st.com \
--cc=krzk+dt@kernel.org \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=quic_schintav@quicinc.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