From: Mark Brown <broonie@kernel.org>
To: Michael Nazzareno Trimarchi <michael@amarulasolutions.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: RFC power domain vs generic supply regulator
Date: Thu, 5 Aug 2021 18:58:43 +0100 [thread overview]
Message-ID: <20210805175843.GS26252@sirena.org.uk> (raw)
In-Reply-To: <CAOf5uw=BZ98KGskd-C4NyHQozi7kpca4ZCQE9c8wxkg-W0Aewg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 749 bytes --]
On Thu, Aug 05, 2021 at 07:39:42PM +0200, Michael Nazzareno Trimarchi wrote:
> So in short you said that if I have a device that has no definition of
> supply in his
> documentation, this device needs to support the supply in his binding
> and make to sense
> to create something like:
> generic-supply = <®ulator_device>;
No, the bindings should use the specific names that the supplies have,
generally whatever the names they are given in the datasheet for the
device. If the device has no actual supplies then it almost certainly
shouldn't be working with the regulator API.
> and let dd to pick them up
No, the driver for the device should handle things. The code is pretty
trivial, though if someone wants to write helpers then sure.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-08-05 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 6:01 Michael Nazzareno Trimarchi
2021-08-05 17:23 ` Mark Brown
2021-08-05 17:39 ` Michael Nazzareno Trimarchi
2021-08-05 17:58 ` Mark Brown [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=20210805175843.GS26252@sirena.org.uk \
--to=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@amarulasolutions.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®