All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jisheng Zhang <jszhang@marvell.com>
To: Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	<linux-arm-kernel@lists.infradead.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: "coupled" regulator support
Date: Fri, 15 Jul 2016 20:01:13 +0800	[thread overview]
Message-ID: <20160715200113.0f3cd823@xhacker> (raw)

Hi,

I dunno how to name this kind of regulator, my situation is:

multiple devices connects to one voltage regulator_dev, e.g devA and devB connects
to regR, regR only support two voltage v1 and v2, let's say v1 < v2

regR can only be set to v1 if devA and devB all call for set voltage to v1
regR can set to v2 if devA or devB call for set voltage to v2

To support this situation, I'd like to add flag to regulator structure and
patch regulator_check_consumers() to check whether we are safe to set the vol

Is this patch acceptable or we already have elegant solution?

Thanks in advance,
Jisheng

WARNING: multiple messages have this Message-ID (diff)
From: jszhang@marvell.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: "coupled" regulator support
Date: Fri, 15 Jul 2016 20:01:13 +0800	[thread overview]
Message-ID: <20160715200113.0f3cd823@xhacker> (raw)

Hi,

I dunno how to name this kind of regulator, my situation is:

multiple devices connects to one voltage regulator_dev, e.g devA and devB connects
to regR, regR only support two voltage v1 and v2, let's say v1 < v2

regR can only be set to v1 if devA and devB all call for set voltage to v1
regR can set to v2 if devA or devB call for set voltage to v2

To support this situation, I'd like to add flag to regulator structure and
patch regulator_check_consumers() to check whether we are safe to set the vol

Is this patch acceptable or we already have elegant solution?

Thanks in advance,
Jisheng

             reply	other threads:[~2016-07-15 12:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-15 12:01 Jisheng Zhang [this message]
2016-07-15 12:01 ` "coupled" regulator support Jisheng Zhang
2016-07-15 12:50 ` Mark Brown
2016-07-15 12:50   ` Mark Brown
2016-07-18  6:44   ` Jisheng Zhang
2016-07-18  6:44     ` Jisheng Zhang
2016-07-18 18:05     ` Mark Brown
2016-07-18 18:05       ` Mark Brown
2016-07-21 10:45       ` Jisheng Zhang
2016-07-21 10:45         ` Jisheng Zhang

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=20160715200113.0f3cd823@xhacker \
    --to=jszhang@marvell.com \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.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.