From: Bjorn Helgaas <helgaas@kernel.org>
To: Sherry Sun <sherry.sun@nxp.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
Frank.Li@nxp.com, s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, lpieralisi@kernel.org,
kwilczynski@kernel.org, mani@kernel.org, bhelgaas@google.com,
hongxing.zhu@nxp.com, l.stach@pengutronix.de,
imx@lists.linux.dev, linux-pci@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V13 02/12] PCI: host-generic: Add common helpers for parsing Root Port properties
Date: Thu, 16 Apr 2026 15:39:05 -0500 [thread overview]
Message-ID: <20260416203905.GA29913@bhelgaas> (raw)
In-Reply-To: <20260416111422.183860-3-sherry.sun@nxp.com>
On Thu, Apr 16, 2026 at 07:14:12PM +0800, Sherry Sun wrote:
> Introduce generic helper functions to parse Root Port device tree nodes
> and extract common properties like reset GPIOs. This allows multiple
> PCI host controller drivers to share the same parsing logic.
>
> Define struct pci_host_port to hold common Root Port properties
> (currently only reset GPIO descriptor) and add
> pci_host_common_parse_ports() to parse Root Port nodes from device tree.
Are the Root Port and the RC the only possible places for 'reset' GPIO
descriptions in DT? I think PERST# routing is outside the PCIe spec,
so it seems like a system could provide a PERST# GPIO routed to any
Switch Upstream Port or Endpoint (I assume a PERST# connected to a
switch would apply to both the upstream port and the downstream
ports).
next prev parent reply other threads:[~2026-04-16 20:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 11:14 [PATCH V13 00/12] pci-imx6: Add support for parsing the reset property in new Root Port binding Sherry Sun
2026-04-16 11:14 ` [PATCH V13 01/12] dt-bindings: PCI: fsl,imx6q-pcie: Add reset GPIO in Root Port node Sherry Sun
2026-04-16 11:14 ` [PATCH V13 02/12] PCI: host-generic: Add common helpers for parsing Root Port properties Sherry Sun
2026-04-16 20:39 ` Bjorn Helgaas [this message]
2026-04-17 3:17 ` Sherry Sun
2026-04-17 19:55 ` Bjorn Helgaas
2026-04-16 11:14 ` [PATCH V13 03/12] PCI: imx6: Assert PERST# before enabling regulators Sherry Sun
2026-04-16 11:14 ` [PATCH V13 04/12] PCI: imx6: Add support for parsing the reset property in new Root Port binding Sherry Sun
2026-04-16 11:14 ` [PATCH V13 05/12] arm: dts: imx6qdl: Add Root Port node and PERST property Sherry Sun
2026-04-16 11:14 ` [PATCH V13 06/12] arm: dts: imx6sx: " Sherry Sun
2026-04-16 11:14 ` [PATCH V13 07/12] arm: dts: imx7d: " Sherry Sun
2026-04-16 11:14 ` [PATCH V13 08/12] arm64: dts: imx8mm: " Sherry Sun
2026-04-16 11:14 ` [PATCH V13 09/12] arm64: dts: imx8mp: " Sherry Sun
2026-04-16 11:14 ` [PATCH V13 10/12] arm64: dts: imx8mq: " Sherry Sun
2026-04-16 11:14 ` [PATCH V13 11/12] arm64: dts: imx8dxl/qm/qxp: " Sherry Sun
2026-04-16 11:14 ` [PATCH V13 12/12] arm64: dts: imx95: " Sherry Sun
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=20260416203905.GA29913@bhelgaas \
--to=helgaas@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=hongxing.zhu@nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=kwilczynski@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=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sherry.sun@nxp.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