From: Mark Brown <broonie@kernel.org>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: Rob Herring <robh@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Liam Girdwood <lgirdwood@gmail.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] regulator: Add coupled regulator
Date: Fri, 5 Feb 2016 15:32:58 +0000 [thread overview]
Message-ID: <20160205153258.GW4455@sirena.org.uk> (raw)
In-Reply-To: <20160205143328.GD31506@lukather>
[-- Attachment #1: Type: text/plain, Size: 689 bytes --]
On Fri, Feb 05, 2016 at 03:33:28PM +0100, Maxime Ripard wrote:
> On Thu, Jan 21, 2016 at 04:28:02PM +0000, Mark Brown wrote:
> > On Thu, Jan 21, 2016 at 04:46:49PM +0100, Maxime Ripard wrote:
> > > Anyway, I'm fine with both approaches, just let me know what you
> > > prefer.
> > Without seeing an implementation of the lists it's hard to say.
> Just to make sure we're on the same page: you want to keep the
> regulator, but instead of giving the parent through vinX-supplies
> properties, you want to have a single *-supply property, with a list
> of regulators, right?
Either that or an explicit regulator describing the merge. Rob wants
the list I think but I really don't care.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Maxime Ripard
<maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
Cc: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Chen-Yu Tsai <wens-jdAy2FN1RRM@public.gmane.org>,
Liam Girdwood <lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2 1/2] regulator: Add coupled regulator
Date: Fri, 5 Feb 2016 15:32:58 +0000 [thread overview]
Message-ID: <20160205153258.GW4455@sirena.org.uk> (raw)
In-Reply-To: <20160205143328.GD31506@lukather>
[-- Attachment #1: Type: text/plain, Size: 689 bytes --]
On Fri, Feb 05, 2016 at 03:33:28PM +0100, Maxime Ripard wrote:
> On Thu, Jan 21, 2016 at 04:28:02PM +0000, Mark Brown wrote:
> > On Thu, Jan 21, 2016 at 04:46:49PM +0100, Maxime Ripard wrote:
> > > Anyway, I'm fine with both approaches, just let me know what you
> > > prefer.
> > Without seeing an implementation of the lists it's hard to say.
> Just to make sure we're on the same page: you want to keep the
> regulator, but instead of giving the parent through vinX-supplies
> properties, you want to have a single *-supply property, with a list
> of regulators, right?
Either that or an explicit regulator describing the merge. Rob wants
the list I think but I really don't care.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] regulator: Add coupled regulator
Date: Fri, 5 Feb 2016 15:32:58 +0000 [thread overview]
Message-ID: <20160205153258.GW4455@sirena.org.uk> (raw)
In-Reply-To: <20160205143328.GD31506@lukather>
On Fri, Feb 05, 2016 at 03:33:28PM +0100, Maxime Ripard wrote:
> On Thu, Jan 21, 2016 at 04:28:02PM +0000, Mark Brown wrote:
> > On Thu, Jan 21, 2016 at 04:46:49PM +0100, Maxime Ripard wrote:
> > > Anyway, I'm fine with both approaches, just let me know what you
> > > prefer.
> > Without seeing an implementation of the lists it's hard to say.
> Just to make sure we're on the same page: you want to keep the
> regulator, but instead of giving the parent through vinX-supplies
> properties, you want to have a single *-supply property, with a list
> of regulators, right?
Either that or an explicit regulator describing the merge. Rob wants
the list I think but I really don't care.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160205/d5a0c1d4/attachment.sig>
next prev parent reply other threads:[~2016-02-05 15:33 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 13:37 [PATCH v2 0/2] regulator: Add support for parallel regulators Maxime Ripard
2016-01-12 13:37 ` Maxime Ripard
2016-01-12 13:37 ` [PATCH v2 1/2] regulator: Add coupled regulator Maxime Ripard
2016-01-12 13:37 ` Maxime Ripard
2016-01-12 14:31 ` Rob Herring
2016-01-12 14:31 ` Rob Herring
2016-01-15 8:57 ` Maxime Ripard
2016-01-15 8:57 ` Maxime Ripard
2016-01-17 0:04 ` Rob Herring
2016-01-17 0:04 ` Rob Herring
2016-01-17 0:04 ` Rob Herring
2016-01-18 16:25 ` Mark Brown
2016-01-18 16:25 ` Mark Brown
2016-01-18 16:25 ` Mark Brown
2016-01-21 15:46 ` Maxime Ripard
2016-01-21 15:46 ` Maxime Ripard
2016-01-21 16:28 ` Mark Brown
2016-01-21 16:28 ` Mark Brown
2016-02-05 14:33 ` Maxime Ripard
2016-02-05 14:33 ` Maxime Ripard
2016-02-05 14:33 ` Maxime Ripard
2016-02-05 15:32 ` Mark Brown [this message]
2016-02-05 15:32 ` Mark Brown
2016-02-05 15:32 ` Mark Brown
2016-11-07 15:47 ` Maxime Ripard
2016-11-07 15:47 ` Maxime Ripard
2016-11-07 15:47 ` Maxime Ripard
2016-11-11 16:46 ` Mark Brown
2016-11-11 16:46 ` Mark Brown
2016-01-12 13:37 ` [PATCH v2 2/2] ARM: sunxi: chip: Add Wifi chip Maxime Ripard
2016-01-12 13:37 ` Maxime Ripard
2016-01-12 13:37 ` Maxime Ripard
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=20160205153258.GW4455@sirena.org.uk \
--to=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=robh@kernel.org \
--cc=wens@csie.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.