From: Mark Brown <broonie@kernel.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: "Christian Kohlschütter" <christian@kohlschutter.com>,
heiko@sntech.de, lgirdwood@gmail.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org,
linux-rockchip@lists.infradead.org, m.reichl@fivetechno.de,
robin.murphy@arm.com, vincent.legoll@gmail.com, wens@kernel.org
Subject: Re: [PATCH v4] regulator: core: Resolve supply name earlier to prevent double-init
Date: Thu, 25 Aug 2022 13:21:13 +0100 [thread overview]
Message-ID: <YwdpOX0xCzYwhjmx@sirena.org.uk> (raw)
In-Reply-To: <58b92e75-f373-dae7-7031-8abd465bb874@samsung.com>
[-- Attachment #1.1: Type: text/plain, Size: 1062 bytes --]
On Thu, Aug 25, 2022 at 01:32:50PM +0200, Marek Szyprowski wrote:
> This patch landed recently in linux next as commit 8a866d527ac0
> ("regulator: core: Resolve supply name earlier to prevent double-init").
> Unfortunately it breaks booting of Samsung Exynos 5800 based Peach-Pi
> (arch/arm/boot/dts/exynos5800-peach-pi.dts) and Peach-Pit
> (arch/arm/boot/dts/exynos5420-peach-pit.dts) Chromebooks. The last
> message in the kernel log is a message about disabling 'vdd_1v2'
> regulator. This regulator is not used directly, however it is a supply
> for other critical regulators.
This suggests that supplies are ending up not getting bound. Could you
perhaps add logging to check that we're attempting to resolve the supply
(in the
+ if ((rdev->supply_name && !rdev->supply) &&
+ (rdev->constraints->always_on ||
+ rdev->constraints->boot_on)) {
block)? I'd also note that it's useful to paste the actual error
messages you're seeing rather than just a description of them.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-08-25 12:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEwRq=qe+Frwpe=Zr4n_8A6vjOJnV3noegdnHSN7NTazkKejBA@mail.gmail.com>
2022-08-04 10:44 ` [PATCH v3] regulator: core: Resolve supply name earlier to prevent double-init Christian Kohlschütter
2022-08-15 11:17 ` Mark Brown
2022-08-18 12:46 ` [PATCH v4] " Christian Kohlschütter
2022-08-18 15:23 ` Mark Brown
2022-08-25 11:32 ` Marek Szyprowski
2022-08-25 12:21 ` Mark Brown [this message]
2022-08-25 14:23 ` Marek Szyprowski
2022-08-25 15:18 ` Christian Kohlschütter
2022-08-25 21:28 ` [PATCH v5] " Christian Kohlschütter
2022-08-25 21:35 ` Christian Kohlschütter
2022-08-26 5:55 ` Marek Szyprowski
2022-08-29 15:43 ` Mark Brown
2022-08-29 17:01 ` Christian Kohlschütter
2023-02-17 23:22 ` Saravana Kannan
2023-02-17 23:33 ` Christian Kohlschütter
2023-02-17 23:46 ` Saravana Kannan
2023-02-18 0:01 ` Christian Kohlschütter
2023-02-18 0:05 ` Saravana Kannan
2022-08-18 15:22 ` [PATCH v3] " Mark Brown
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=YwdpOX0xCzYwhjmx@sirena.org.uk \
--to=broonie@kernel.org \
--cc=christian@kohlschutter.com \
--cc=heiko@sntech.de \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=m.reichl@fivetechno.de \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.com \
--cc=vincent.legoll@gmail.com \
--cc=wens@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