From: Mark Brown <broonie@kernel.org>
To: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Cc: linux-kernel@vger.kernel.org, Tony Lindgren <tony@atomide.com>,
Liam Girdwood <lgirdwood@gmail.com>,
j-keerthy@ti.com, linux-omap@vger.kernel.org
Subject: Re: [PATCH v2 2/2] regulator: tps65910: Allow supply references to the same chip
Date: Tue, 13 Jun 2017 18:46:28 +0100 [thread overview]
Message-ID: <20170613174628.sv4v76s7torrn5jx@sirena.org.uk> (raw)
In-Reply-To: <053529c206a2afc453b52e2c0f024acd85341a83.1497364762.git.mirq-linux@rere.qmqm.pl>
[-- Attachment #1: Type: text/plain, Size: 510 bytes --]
On Tue, Jun 13, 2017 at 04:41:58PM +0200, Michał Mirosław wrote:
> This allows for (acyclic) references from tps6591x supplies to
> its outputs.
This is clearly not something that should be open coded in individual
drivers, aside from the code duplication it is obviously possible to
have two different chips supplying each other which this wouldn't help
at all. Is this happening for you with current kernels, we have a few
mechanisms for deferring bindings of supplies which should help here.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-06-13 17:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 13:58 [PATCH 1/2] regulator: tps65910: check TPS65910_NUM_REGS at build time Michał Mirosław
2017-06-13 13:58 ` [PATCH 2/2] regulator: tps65910: Allow supply references to the same chip Michał Mirosław
2017-06-13 14:01 ` [PATCH 1/2] regulator: tps65910: check TPS65910_NUM_REGS at build time Keerthy
2017-06-13 14:35 ` Michał Mirosław
2017-06-13 14:41 ` [PATCH v2 " Michał Mirosław
2017-06-13 14:41 ` [PATCH v2 2/2] regulator: tps65910: Allow supply references to the same chip Michał Mirosław
2017-06-13 17:46 ` Mark Brown [this message]
2017-06-13 20:22 ` Michał Mirosław
2017-06-13 20:42 ` Mark Brown
2017-06-14 7:56 ` Javier Martinez Canillas
2017-06-14 12:14 ` Michał Mirosław
2017-06-13 17:44 ` [PATCH v2 1/2] regulator: tps65910: check TPS65910_NUM_REGS at build time 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=20170613174628.sv4v76s7torrn5jx@sirena.org.uk \
--to=broonie@kernel.org \
--cc=j-keerthy@ti.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).