All of lore.kernel.org
 help / color / mirror / Atom feed
From: Francesco Dolcini <francesco@dolcini.it>
To: Sherry Sun <sherry.sun@nxp.com>
Cc: hongxing.zhu@nxp.com, l.stach@pengutronix.de,
	lpieralisi@kernel.org, kw@linux.com, robh@kernel.org,
	bhelgaas@google.com, krzysztof.kozlowski+dt@linaro.org,
	conor+dt@kernel.org, shawnguo@kernel.org, s.hauer@pengutronix.de,
	kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
	linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 2/4] dt-bindings: imx6q-pcie: Add wake-gpios property
Date: Fri, 4 Apr 2025 11:41:30 +0200	[thread overview]
Message-ID: <20250404094130.GA35433@francesco-nb> (raw)
In-Reply-To: <20231213092850.1706042-3-sherry.sun@nxp.com>

Hello

On Wed, Dec 13, 2023 at 05:28:48PM +0800, Sherry Sun wrote:
> Add wake-gpios property that can be used to wakeup the host
> processor.
> 
> Signed-off-by: Sherry Sun <sherry.sun@nxp.com>
> Reviewed-by: Richard Zhu <hongxing.zhu@nxp.com>
> ---
>  Documentation/devicetree/bindings/pci/fsl,imx6q-pcie.yaml | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/pci/fsl,imx6q-pcie.yaml b/Documentation/devicetree/bindings/pci/fsl,imx6q-pcie.yaml
> index 81bbb8728f0f..fba757d937e1 100644
> --- a/Documentation/devicetree/bindings/pci/fsl,imx6q-pcie.yaml
> +++ b/Documentation/devicetree/bindings/pci/fsl,imx6q-pcie.yaml
> @@ -72,6 +72,12 @@ properties:
>        L=operation state) (optional required).
>      type: boolean
>  
> +  wake-gpios:
> +    description: If present this property specifies WAKE# sideband signaling
> +      to implement wakeup functionality. This is an input GPIO pin for the Root
> +      Port mode here. Host drivers will wakeup the host using the IRQ
> +      corresponding to the passed GPIO.
> +

From what I know it is possible to share the same WAKE# signal for
multiple root ports. Is this going to work fine with this binding? Same
question on the driver.

We do have design exactly like that, so it's not a theoretical question.

Francesco




  reply	other threads:[~2025-04-04  9:44 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-13  9:28 [PATCH V2 0/4] PCI: imx6: Add pci host wakeup support Sherry Sun
2023-12-13  9:28 ` Sherry Sun
2023-12-13  9:28 ` [PATCH V2 1/4] PCI: imx6: Add pci host wakeup support on imx platforms Sherry Sun
2023-12-13  9:28   ` Sherry Sun
2023-12-13 19:57   ` Bjorn Helgaas
2023-12-13 19:57     ` Bjorn Helgaas
2023-12-14  4:08     ` Sherry Sun
2023-12-14  4:08       ` Sherry Sun
2023-12-13 21:03   ` kernel test robot
2023-12-13 21:03     ` kernel test robot
2023-12-14  9:56   ` kernel test robot
2023-12-14  9:56     ` kernel test robot
2023-12-14 10:06   ` kernel test robot
2023-12-14 10:06     ` kernel test robot
2023-12-13  9:28 ` [PATCH V2 2/4] dt-bindings: imx6q-pcie: Add wake-gpios property Sherry Sun
2023-12-13  9:28   ` Sherry Sun
2025-04-04  9:41   ` Francesco Dolcini [this message]
2025-04-07  7:18     ` Sherry Sun
2025-04-07  7:23       ` Francesco Dolcini
2025-04-07  9:38         ` Sherry Sun
2023-12-13  9:28 ` [PATCH V2 3/4] arm64: dts: imx8mp-evk: add wake-gpios property for pci bus Sherry Sun
2023-12-13  9:28   ` Sherry Sun
2023-12-13  9:28 ` [PATCH V2 4/4] arm64: dts: imx8mq-evk: " Sherry Sun
2023-12-13  9:28   ` Sherry Sun
2023-12-14  5:13 ` [PATCH V2 0/4] PCI: imx6: Add pci host wakeup support Manivannan Sadhasivam
2023-12-14  5:13   ` Manivannan Sadhasivam
2023-12-14 10:03   ` Sherry Sun
2023-12-14 10:03     ` Sherry Sun
2023-12-14 10:15     ` Manivannan Sadhasivam
2023-12-14 10:15       ` Manivannan Sadhasivam

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=20250404094130.GA35433@francesco-nb \
    --to=francesco@dolcini.it \
    --cc=bhelgaas@google.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=hongxing.zhu@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kw@linux.com \
    --cc=l.stach@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --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 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.