From: Conor Dooley <conor@kernel.org>
To: Richard Zhu <hongxing.zhu@nxp.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
shawnguo@kernel.org, l.stach@pengutronix.de,
devicetree@vger.kernel.org, linux-pci@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@pengutronix.de,
imx@lists.linux.dev
Subject: Re: [PATCH v1 1/4] dt-bindings: imx6q-pcie: Add reg-name "dbi2" and "atu" for i.MX8M PCIe Endpoint
Date: Mon, 22 Jul 2024 17:37:14 +0100 [thread overview]
Message-ID: <20240722-displace-amusable-a884352e0ff9@spud> (raw)
In-Reply-To: <1721634979-1726-2-git-send-email-hongxing.zhu@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 1723 bytes --]
On Mon, Jul 22, 2024 at 03:56:16PM +0800, Richard Zhu wrote:
> Add reg-name: "dbi2", "atu" for i.MX8M PCIe Endpoint.
>
> Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
> ---
> .../devicetree/bindings/pci/fsl,imx6q-pcie-ep.yaml | 13 +++++++++----
> 1 file changed, 9 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/pci/fsl,imx6q-pcie-ep.yaml b/Documentation/devicetree/bindings/pci/fsl,imx6q-pcie-ep.yaml
> index a06f75df8458..309e8953dc91 100644
> --- a/Documentation/devicetree/bindings/pci/fsl,imx6q-pcie-ep.yaml
> +++ b/Documentation/devicetree/bindings/pci/fsl,imx6q-pcie-ep.yaml
> @@ -65,11 +65,13 @@ allOf:
> then:
> properties:
> reg:
> - minItems: 2
> - maxItems: 2
> + minItems: 4
> + maxItems: 4
> reg-names:
> items:
> - const: dbi
> + - const: dbi2
> + - const: atu
New properties in the middle of the list is potentially an ABI break.
Why not add them at the end?
> - const: addr_space
>
> - if:
> @@ -129,8 +131,11 @@ examples:
>
> pcie_ep: pcie-ep@33800000 {
> compatible = "fsl,imx8mp-pcie-ep";
> - reg = <0x33800000 0x000400000>, <0x18000000 0x08000000>;
> - reg-names = "dbi", "addr_space";
> + reg = <0x33800000 0x100000>,
> + <0x33900000 0x100000>,
> + <0x33b00000 0x100000>,
> + <0x18000000 0x8000000>;
> + reg-names = "dbi", "dbi2", "atu", "addr_space";
> clocks = <&clk IMX8MP_CLK_HSIO_ROOT>,
> <&clk IMX8MP_CLK_HSIO_AXI>,
> <&clk IMX8MP_CLK_PCIE_ROOT>;
> --
> 2.37.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-07-22 16:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 7:56 [PATCH v1 0/4] Add dbi2 and atu for i.MX8M PCIe EP Richard Zhu
2024-07-22 7:56 ` [PATCH v1 1/4] dt-bindings: imx6q-pcie: Add reg-name "dbi2" and "atu" for i.MX8M PCIe Endpoint Richard Zhu
2024-07-22 16:37 ` Conor Dooley [this message]
2024-07-22 20:47 ` Frank Li
2024-07-23 14:35 ` Conor Dooley
2024-07-23 20:39 ` Frank Li
2024-07-22 7:56 ` [PATCH v1 2/4] dts: arm64: imx8mq: Add dbi2 and atu reg for i.MX8MQ PCIe EP Richard Zhu
2024-07-22 7:56 ` [PATCH v1 3/4] dts: arm64: imx8mp: Add dbi2 and atu reg for i.MX8MP " Richard Zhu
2024-07-22 7:56 ` [PATCH v1 4/4] dts: arm64: imx8mm: Add dbi2 and atu reg for i.MX8MM " Richard Zhu
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=20240722-displace-amusable-a884352e0ff9@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hongxing.zhu@nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=robh@kernel.org \
--cc=shawnguo@kernel.org \
/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).