From: Mark Brown <broonie@kernel.org>
To: Rob Herring <robh+dt@kernel.org>
Cc: Doug Anderson <dianders@chromium.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Chen-Yu Tsai <wenst@chromium.org>,
linux-input@vger.kernel.org, Jiri Kosina <jikos@kernel.org>,
Hsin-Yi Wang <hsinyi@chromium.org>,
linux-gpio@vger.kernel.org, linus.walleij@linaro.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Johan Hovold <johan+linaro@kernel.org>,
andriy.shevchenko@linux.intel.com, frowand.list@gmail.com,
gregkh@linuxfoundation.org, hdegoede@redhat.com,
james.clark@arm.com, james@equiv.tech, keescook@chromium.org,
linux-kernel@vger.kernel.org, rafael@kernel.org,
tglx@linutronix.de
Subject: Re: [RFC PATCH] of: device: Support 2nd sources of probeable but undiscoverable devices
Date: Fri, 22 Sep 2023 20:28:21 +0100 [thread overview]
Message-ID: <785c1e6e-8d6c-49fa-b9eb-a58e4e6cf435@sirena.org.uk> (raw)
In-Reply-To: <CAL_JsqKJyRJmwJzB1yew71Ld7BeMMat+rzhX9XtDtiFE8Dbvcw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 431 bytes --]
On Fri, Sep 22, 2023 at 02:08:08PM -0500, Rob Herring wrote:
> You could always make the driver probe smarter where if your supply
> was already powered on, then don't delay. Then something else could
> ensure that the supply is enabled. I'm not sure if regulators have the
> same issue as clocks where the clock might be on from the bootloader,
> then a failed probe which gets then puts the clock turns it off.
That'll happen.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-09-22 19:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 17:24 Douglas Anderson
2023-09-22 14:14 ` Rob Herring
2023-09-22 17:40 ` Doug Anderson
2023-09-22 19:08 ` Rob Herring
2023-09-22 19:28 ` Mark Brown [this message]
2023-09-23 0:11 ` Doug Anderson
2023-09-27 2:36 ` Jeff LaBundy
2023-09-27 23:50 ` Doug Anderson
2023-09-28 20:37 ` Rob Herring
2023-09-28 23:21 ` Doug Anderson
2023-09-28 20:11 ` Rob Herring
2023-09-28 23:21 ` Doug Anderson
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=785c1e6e-8d6c-49fa-b9eb-a58e4e6cf435@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=benjamin.tissoires@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=hsinyi@chromium.org \
--cc=james.clark@arm.com \
--cc=james@equiv.tech \
--cc=jikos@kernel.org \
--cc=johan+linaro@kernel.org \
--cc=keescook@chromium.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=wenst@chromium.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
all inboxes | Powered by JetHome®