From: Manivannan Sadhasivam <mani@kernel.org>
To: frank.li@nxp.com, jingoohan1@gmail.com, l.stach@pengutronix.de,
lpieralisi@kernel.org, kwilczynski@kernel.org, robh@kernel.org,
bhelgaas@google.com, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, Richard Zhu <hongxing.zhu@nxp.com>
Cc: linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
imx@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/2] PCI: imx6: Add a method to handle CLKREQ# override
Date: Thu, 25 Sep 2025 22:35:04 +0530 [thread overview]
Message-ID: <175881990427.392988.6937520327985325506.b4-ty@kernel.org> (raw)
In-Reply-To: <20250923073913.2722668-1-hongxing.zhu@nxp.com>
On Tue, 23 Sep 2025 15:39:11 +0800, Richard Zhu wrote:
> The CLKREQ# is an open drain, active low signal that is driven low by
> the card to request reference clock. It's an optional signal added in
> PCIe CEM r4.0, sec 2. Thus, this signal wouldn't be driven low if it's
> reserved.
>
> Since the reference clock controlled by CLKREQ# may be required by i.MX
> PCIe host too. To make sure this clock is ready even when the CLKREQ#
> isn't driven low by the card(e.x the scenario described above), force
> CLKREQ# override active low for i.MX PCIe host during initialization.
>
> [...]
Applied, thanks!
[1/2] PCI: dwc: Invoke post_init in dw_pcie_resume_noirq()
commit: 27afd094ea4be542594058d685c7af4654ab8de7
[2/2] PCI: imx6: Add a method to handle CLKREQ# override active low
commit: dc853fb85d6b90e0805660c1dbb38ef7641af839
Best regards,
--
Manivannan Sadhasivam <mani@kernel.org>
prev parent reply other threads:[~2025-09-25 17:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 7:39 [PATCH v5 0/2] PCI: imx6: Add a method to handle CLKREQ# override Richard Zhu
2025-09-23 7:39 ` [PATCH v5 1/2] PCI: dwc: Invoke post_init in dw_pcie_resume_noirq() Richard Zhu
2025-09-23 7:39 ` [PATCH v5 2/2] PCI: imx6: Add a method to handle CLKREQ# override active low Richard Zhu
2025-09-25 21:57 ` Bjorn Helgaas
2025-09-26 2:19 ` Hongxing Zhu
2025-09-25 22:04 ` Bjorn Helgaas
2025-09-26 2:19 ` Hongxing Zhu
2025-09-26 2:44 ` Bjorn Helgaas
2025-09-26 3:08 ` Hongxing Zhu
2025-09-26 20:25 ` Bjorn Helgaas
2025-09-26 22:46 ` Frank Li
2025-10-03 17:21 ` Bjorn Helgaas
2025-09-26 3:23 ` Hongxing Zhu
2025-09-26 20:24 ` Bjorn Helgaas
2025-09-26 22:58 ` Frank Li
2025-09-25 17:05 ` Manivannan Sadhasivam [this message]
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=175881990427.392988.6937520327985325506.b4-ty@kernel.org \
--to=mani@kernel.org \
--cc=bhelgaas@google.com \
--cc=festevam@gmail.com \
--cc=frank.li@nxp.com \
--cc=hongxing.zhu@nxp.com \
--cc=imx@lists.linux.dev \
--cc=jingoohan1@gmail.com \
--cc=kernel@pengutronix.de \
--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=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--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