All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrii Tseglytskyi <andrii.tseglytskyi@ti.com>
To: Mike Turquette <mturquette@linaro.org>
Cc: "Nishanth Menon" <nm@ti.com>, "Tero Kristo" <t-kristo@ti.com>,
	"Benoît Cousson" <b-cousson@ti.com>,
	linux-omap@vger.kernel.org, andrii.tseglytskyi@ti.com
Subject: Re: [RFC PATCH 5/6] ARM: OMAP3+: ABB: introduce ABB driver
Date: Tue, 2 Apr 2013 20:35:49 +0300	[thread overview]
Message-ID: <515B16F5.2090708@ti.com> (raw)
In-Reply-To: <20130402171614.8177.68752@quantum>

On 04/02/2013 08:16 PM, Mike Turquette wrote:
> Quoting Nishanth Menon (2013-04-01 20:35:45)
>> On 17:05-20130401, Mike Turquette wrote:
>>> OK, so we're in agreement on what The Future looks like.  What does that
>>> mean for Andrii's patchset?
>> Unless anyone has an fundamental issue with the approach of an "Super
>> regulator" controlling "sub regulators", I think, in-line with your
>> view, we should probably make ABB as an regulator instead of inventing
>> our own API and hooking it around clock notifiers.
> ACK.  Making the ABB code into a regulator driver is the right thing to
> do regardless of whether or not we use a Super Regulator(tm) or just
> chain together Not So Super Regulators(tm).
>
> I'm not an expert at the regulator framework, but I encourage Andrii to
> look into regulator_set_mode(), which might be a more semantically
> accurate alternative than regulator_set_voltage() for the ABB ldo.
>
> Regards,
> Mike
>
>> -- 
>> Regards,
>> Nishanth Menon

Hi,

Agree. It is a good idea in general.
regulator_set_mode() API seems to be good enough for handling ABB mode 
(FBB/RBB/Bypass).
Knowledge about ABB mode on each OPP can be moved from ABB regulator to 
"Super regulator".
Thanks a lot for all your comments.

Regards,
Andrii

  parent reply	other threads:[~2013-04-02 17:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-28 17:16 [PATCH 1/6] ARM: dts: OMAP36xx: add device tree for ABB Andrii Tseglytskyi
2013-03-28 17:16 ` [PATCH 2/6] ARM: dts: OMAP4: " Andrii Tseglytskyi
2013-03-28 17:16 ` [PATCH 3/6] ARM: dts: OMAP5: " Andrii Tseglytskyi
2013-03-28 17:16 ` [PATCH 4/6] ARM: OMAP3+: ABB: add aliases for clocks used in ABB driver Andrii Tseglytskyi
2013-03-28 17:16 ` [PATCH 5/6] ARM: OMAP3+: ABB: introduce " Andrii Tseglytskyi
2013-03-28 21:27   ` Mike Turquette
2013-03-28 22:35     ` Nishanth Menon
2013-04-01 11:04       ` Andrii Tseglytskyi
2013-04-01 11:07       ` Andrii Tseglytskyi
     [not found]       ` <51596725.9060109@ti.com>
2013-04-01 18:10         ` [RFC PATCH " Mike Turquette
2013-04-01 19:28           ` Nishanth Menon
     [not found]             ` <20130401213430.8177.21940@quantum>
2013-04-01 23:00               ` Nishanth Menon
     [not found]                 ` <20130402000545.8177.65252@quantum>
2013-04-02  3:35                   ` Nishanth Menon
2013-04-02 10:15                     ` Grygorii Strashko
2013-04-02 12:49                       ` Nishanth Menon
     [not found]                     ` <20130402171614.8177.68752@quantum>
2013-04-02 17:35                       ` Andrii Tseglytskyi [this message]
2013-04-03  2:00                         ` Nishanth Menon
2013-04-03 20:09                           ` Mike Turquette
2013-03-28 17:16 ` [PATCH 6/6] ARM: OMAP3+: ABB: introduce debugfs entry Andrii Tseglytskyi

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=515B16F5.2090708@ti.com \
    --to=andrii.tseglytskyi@ti.com \
    --cc=b-cousson@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=mturquette@linaro.org \
    --cc=nm@ti.com \
    --cc=t-kristo@ti.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 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.