All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Richard Zhu <hongxing.zhu@nxp.com>,
	bhelgaas@google.com, l.stach@pengutronix.de
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	linux-imx@nxp.com, linux-arm-kernel@lists.infradead.org,
	kernel@pengutronix.de, linux-kernel@vger.kernel.org,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH v2] PCI: imx6: Assert i.MX8MM CLKREQ# even if no device present
Date: Thu, 17 Mar 2022 09:01:18 +0000	[thread overview]
Message-ID: <164750763778.14330.2374977117097314236.b4-ty@arm.com> (raw)
In-Reply-To: <1645672013-8949-1-git-send-email-hongxing.zhu@nxp.com>

On Thu, 24 Feb 2022 11:06:53 +0800, Richard Zhu wrote:
> The CLKREQ# signal is an open drain, active low signal that is driven
> low by the remote Endpoint device. But it might not be driven low if no
> Endpoint device is connected.
> 
> On i.MX8MM PCIe, phy_init() may fail and system boot may hang if no
> Endpoint is connected to assert CLKREQ#.
> 
> [...]

Applied to pci/imx6, thanks!

[1/1] PCI: imx6: Assert i.MX8MM CLKREQ# even if no device present
      https://git.kernel.org/lpieralisi/pci/c/45514f78c6

Thanks,
Lorenzo

WARNING: multiple messages have this Message-ID (diff)
From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Richard Zhu <hongxing.zhu@nxp.com>,
	bhelgaas@google.com, l.stach@pengutronix.de
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	linux-imx@nxp.com, linux-arm-kernel@lists.infradead.org,
	kernel@pengutronix.de, linux-kernel@vger.kernel.org,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH v2] PCI: imx6: Assert i.MX8MM CLKREQ# even if no device present
Date: Thu, 17 Mar 2022 09:01:18 +0000	[thread overview]
Message-ID: <164750763778.14330.2374977117097314236.b4-ty@arm.com> (raw)
In-Reply-To: <1645672013-8949-1-git-send-email-hongxing.zhu@nxp.com>

On Thu, 24 Feb 2022 11:06:53 +0800, Richard Zhu wrote:
> The CLKREQ# signal is an open drain, active low signal that is driven
> low by the remote Endpoint device. But it might not be driven low if no
> Endpoint device is connected.
> 
> On i.MX8MM PCIe, phy_init() may fail and system boot may hang if no
> Endpoint is connected to assert CLKREQ#.
> 
> [...]

Applied to pci/imx6, thanks!

[1/1] PCI: imx6: Assert i.MX8MM CLKREQ# even if no device present
      https://git.kernel.org/lpieralisi/pci/c/45514f78c6

Thanks,
Lorenzo

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-03-17  9:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24  3:06 [PATCH v2] PCI: imx6: Assert i.MX8MM CLKREQ# even if no device present Richard Zhu
2022-02-24  3:06 ` Richard Zhu
2022-03-16  0:13 ` Hongxing Zhu
2022-03-16  0:13   ` Hongxing Zhu
2022-03-16  9:29 ` Lucas Stach
2022-03-16  9:29   ` Lucas Stach
2022-03-17  9:01 ` Lorenzo Pieralisi [this message]
2022-03-17  9:01   ` Lorenzo Pieralisi

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=164750763778.14330.2374977117097314236.b4-ty@arm.com \
    --to=lorenzo.pieralisi@arm.com \
    --cc=bhelgaas@google.com \
    --cc=hongxing.zhu@nxp.com \
    --cc=kernel@pengutronix.de \
    --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 \
    /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.