From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] regulator: Add coupled regulator
Date: Thu, 21 Jan 2016 16:28:02 +0000 [thread overview]
Message-ID: <20160121162802.GL6588@sirena.org.uk> (raw)
In-Reply-To: <20160121154649.GE3997@lukather>
On Thu, Jan 21, 2016 at 04:46:49PM +0100, Maxime Ripard wrote:
> I guess a separate driver would make it easier to deal with cases like
> the one you suggested (shutting down when the load is going to be
> lower). I don't see how we could have a good DT representation of that
> if we're going to use lists.
We can have a driver regardless of what the DT looks like, it's a
question of how things get instantiated.
> 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.
-------------- 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/20160121/32f95c74/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
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: Thu, 21 Jan 2016 16:28:02 +0000 [thread overview]
Message-ID: <20160121162802.GL6588@sirena.org.uk> (raw)
In-Reply-To: <20160121154649.GE3997@lukather>
[-- Attachment #1: Type: text/plain, Size: 560 bytes --]
On Thu, Jan 21, 2016 at 04:46:49PM +0100, Maxime Ripard wrote:
> I guess a separate driver would make it easier to deal with cases like
> the one you suggested (shutting down when the load is going to be
> lower). I don't see how we could have a good DT representation of that
> if we're going to use lists.
We can have a driver regardless of what the DT looks like, it's a
question of how things get instantiated.
> 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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-01-21 16:28 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 [this message]
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
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=20160121162802.GL6588@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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.