All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Krzysztof Wilczyński" <kw@linux.com>
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 v5 1/4] dt-bindings: imx6q-pcie: Add reg-name "dbi2" and "atu" for i.MX8M PCIe Endpoint
Date: Fri, 6 Sep 2024 15:31:10 +0900	[thread overview]
Message-ID: <20240906063110.GA679795@rocinante> (raw)
In-Reply-To: <1723534943-28499-2-git-send-email-hongxing.zhu@nxp.com>

Hello,

> Add reg-name: "dbi2", "atu" for i.MX8M PCIe Endpoint.
> 
> For i.MX8M PCIe EP, the dbi2 and atu addresses are pre-defined in the
> driver. This method is not good.
> 
> In commit b7d67c6130ee ("PCI: imx6: Add iMX95 Endpoint (EP) support"),
> Frank suggests to fetch the dbi2 and atu from DT directly. This commit is
> preparation to do that for i.MX8M PCIe EP.
> 
> These changes wouldn't break driver function. When "dbi2" and "atu"
> properties are present, i.MX PCIe driver would fetch the according base
> addresses from DT directly. If only two reg properties are provided, i.MX
> PCIe driver would fall back to the old method.

Applied to dt-bindings, thank you!

[1/1] dt-bindings: PCI: imx6q-pcie: Add reg-name "dbi2" and "atu" for i.MX8M PCIe Endpoint
      https://git.kernel.org/pci/pci/c/2f309c988b7c

	Krzysztof

  parent reply	other threads:[~2024-09-06  6:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-13  7:42 [PATCH v5 0/4] Add dbi2 and atu for i.MX8M PCIe EP Richard Zhu
2024-08-13  7:42 ` [PATCH v5 1/4] dt-bindings: imx6q-pcie: Add reg-name "dbi2" and "atu" for i.MX8M PCIe Endpoint Richard Zhu
2024-08-13  8:52   ` Krzysztof Kozlowski
2024-08-13 16:32   ` Rob Herring (Arm)
2024-08-14  1:49     ` Hongxing Zhu
2024-08-31 12:59       ` Shawn Guo
2024-09-02  2:08         ` Hongxing Zhu
2024-09-04 13:38           ` Frank Li
2024-09-06  6:31   ` Krzysztof Wilczyński [this message]
2024-10-09 15:00   ` Niklas Cassel
2024-10-10  2:17     ` Hongxing Zhu
2024-10-10  9:33       ` Niklas Cassel
2024-08-13  7:42 ` [PATCH v5 2/4] arm64: dts: imx8mq: Add dbi2 and atu reg for i.MX8MQ PCIe EP Richard Zhu
2024-08-13  8:54   ` Krzysztof Kozlowski
2024-08-13  8:55     ` Krzysztof Kozlowski
2024-08-13  7:42 ` [PATCH v5 3/4] arm64: dts: imx8mp: Add dbi2 and atu reg for i.MX8MP " Richard Zhu
2024-08-13  7:42 ` [PATCH v5 4/4] arm64: dts: imx8mm: Add dbi2 and atu reg for i.MX8MM " Richard Zhu
2024-08-31 13:02 ` [PATCH v5 0/4] Add dbi2 and atu for i.MX8M " Shawn Guo
2024-09-04  9:38   ` Shawn Guo
2024-09-09  1:43     ` Hongxing Zhu
2024-09-25  3:39       ` Hongxing Zhu
2024-09-25  3:45       ` Hongxing Zhu
2024-09-25  4:03     ` Hongxing Zhu
2024-10-08  8:30       ` Shawn Guo

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=20240906063110.GA679795@rocinante \
    --to=kw@linux.com \
    --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 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.