From: Mark Brown <broonie@kernel.org>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: Doug Anderson <dianders@chromium.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
Liam Girdwood <lgirdwood@gmail.com>,
patches@opensource.cirrus.com
Subject: Re: [PATCH] regulator: wm8994: Use PROBE_FORCE_SYNCHRONOUS
Date: Thu, 23 Mar 2023 17:49:28 +0000 [thread overview]
Message-ID: <beeef631-943a-40db-af09-753c96b5b140@sirena.org.uk> (raw)
In-Reply-To: <20230323174531.GM68926@ediswmail.ad.cirrus.com>
[-- Attachment #1: Type: text/plain, Size: 701 bytes --]
On Thu, Mar 23, 2023 at 05:45:31PM +0000, Charles Keepax wrote:
> I think really the best place to look at this would be at the
> regulator level. It is fine if mfd_add_devices passes, the problem
> really is that the regulator core doesn't realise the regulator is
> going to be arriving, and thus returns a dummy regulator, rather
> than returning EPROBE_DEFER. If it did the MFD driver would probe
> defer at the point of requesting the regulator, which would all
> make sense.
You need the MFD to tell the regulator subsystem that there's a
regulator bound there, or to force all the users to explicitly do the
mapping of the regulator in their firmwares (which isn't really a
viable approach).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-03-23 17:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230323083330eucas1p1f7e3f9beb5ba168c6b13374d74c158f0@eucas1p1.samsung.com>
2023-03-23 8:33 ` Marek Szyprowski
2023-03-23 11:40 ` Charles Keepax
2023-03-23 16:53 ` Doug Anderson
2023-03-23 16:57 ` Mark Brown
2023-03-23 17:45 ` Charles Keepax
2023-03-23 17:49 ` Mark Brown [this message]
2023-03-24 9:21 ` Charles Keepax
2023-03-23 18:00 ` Doug Anderson
2023-03-24 9:23 ` Charles Keepax
2023-03-24 15:06 ` Doug Anderson
2023-03-24 15:44 ` Charles Keepax
2023-03-23 13:49 ` 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=beeef631-943a-40db-af09-753c96b5b140@sirena.org.uk \
--to=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=dianders@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=patches@opensource.cirrus.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®