From: Shawn Guo <shawnguo@kernel.org>
To: Alexander Stein <alexander.stein@ew.tq-group.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Markus Niebel <Markus.Niebel@ew.tq-group.com>,
Matthias Schiffer <matthias.schiffer@ew.tq-group.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] ARM: dts: imx6qdl-mba6: Add missing pvcie-supply regulator
Date: Sun, 14 May 2023 21:03:22 +0800 [thread overview]
Message-ID: <20230514130322.GW727834@dragon> (raw)
In-Reply-To: <20230503113112.1751886-1-alexander.stein@ew.tq-group.com>
On Wed, May 03, 2023 at 01:31:10PM +0200, Alexander Stein wrote:
> This worked before by coincidence, as the regulator was probed and enabled
> before PCI RC probe. But probe order changed since commit 259b93b21a9f
> ("regulator: Set PROBE_PREFER_ASYNCHRONOUS for drivers that existed in
> 4.14") and PCIe supply is enabled after RC.
> Fix this by adding the regulator to RC node.
>
> The PCIe vaux regulator still needs to be enabled unconditionally for
> Mini-PCIe USB-only devices.
>
> Fixes: ef3846247b41 ("ARM: dts: imx6qdl: add TQ-Systems MBa6x device trees")
> Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
Applied, thanks!
prev parent reply other threads:[~2023-05-14 13:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 11:31 [PATCH 1/3] ARM: dts: imx6qdl-mba6: Add missing pvcie-supply regulator Alexander Stein
2023-05-03 11:31 ` Alexander Stein
2023-05-03 11:31 ` [PATCH 2/3] ARM: dts: imx6qdl-mba6: add mac address for USB ethernet controller Alexander Stein
2023-05-03 11:31 ` Alexander Stein
2023-05-14 13:04 ` Shawn Guo
2023-05-03 11:31 ` [PATCH 3/3] ARM: dts: imx6qdl-mba6: Add missing supply regulator for lm75 and at24 Alexander Stein
2023-05-03 11:31 ` Alexander Stein
2023-06-16 9:42 ` Alexander Stein
2023-06-16 9:42 ` Alexander Stein
2023-07-16 13:39 ` Shawn Guo
2023-07-16 13:39 ` Shawn Guo
2023-05-14 13:03 ` Shawn Guo [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=20230514130322.GW727834@dragon \
--to=shawnguo@kernel.org \
--cc=Markus.Niebel@ew.tq-group.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=matthias.schiffer@ew.tq-group.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
/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.