From: Kevin Hilman <khilman@linaro.org>
To: Andrii Tseglytskyi <andrii.tseglytskyi@ti.com>
Cc: linux-omap@vger.kernel.org, "Benoît Cousson" <b-cousson@ti.com>,
"Tero Kristo" <t-kristo@ti.com>,
"Mike Turquette" <mturquette@linaro.org>
Subject: Re: [RFC PATCH v2 0/6] ARM: OMAP3+: Introduce ABB driver
Date: Mon, 15 Apr 2013 14:53:44 -0700 [thread overview]
Message-ID: <87sj2rbguv.fsf@linaro.org> (raw)
In-Reply-To: <1366032491-4162-1-git-send-email-andrii.tseglytskyi@ti.com> (Andrii Tseglytskyi's message of "Mon, 15 Apr 2013 16:28:05 +0300")
Andrii Tseglytskyi <andrii.tseglytskyi@ti.com> writes:
> From: "Andrii.Tseglytskyi" <andrii.tseglytskyi@ti.com>
>
> Following patch series introduces the Adaptive Body-Bias
> LDO driver, which handles LDOs voltage during OPP change routine.
> Current implementation is based on patch series from
> Mike Turquette:
>
> http://marc.info/?l=linux-omap&m=134931341818379&w=2
>
> ABB transition is a part of OPP changing sequence.
> ABB can operate in the following modes:
> - Bypass mode: Activated when ABB is not required
> - FBB mode: Fast Body Bias mode, used on fast OPPs
Fast? I thought the 'F' was for Forward?
> - RBB mode: Reverse Body Bias mode, used on slow OPPs
>
> In current implementation ABB is converted to regulator.
> Standalone OPP table is used to store ABB mode, it is defined
> in device tree for each ABB regulator. It has the following format:
>
> operating-points = <
> /* uV ABB (0 - Bypass, 1 - FBB, 2 - RBB) */
> 880000 0
> 1060000 1
> 1250000 1
> 1260000 1
>>;
>
> ABB regulator is linked to regulator chain
In addition to Mike's comments (which I completely agree with), it would
be very helfpul to see how this is actually used. e.g, how the
regulators are chained together, how the proper ordering is managed,
etc. etc.
IOW, This series gives a bunch of low-level details without
demonstrating the actual use case and showing the regulator API usage
that would make this work.
Kevin
next prev parent reply other threads:[~2013-04-15 21:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 13:28 [RFC PATCH v2 0/6] ARM: OMAP3+: Introduce ABB driver Andrii Tseglytskyi
2013-04-15 13:28 ` [RFC PATCH v2 1/6] ARM: dts: OMAP36xx: add device tree for ABB Andrii Tseglytskyi
2013-04-15 13:28 ` [RFC PATCH v2 2/6] ARM: dts: OMAP4: " Andrii Tseglytskyi
2013-04-15 13:28 ` [RFC PATCH v2 3/6] ARM: dts: OMAP5: " Andrii Tseglytskyi
2013-04-15 13:28 ` [RFC PATCH v2 4/6] ARM: OMAP3+: ABB: add aliases for sysclk used in ABB driver Andrii Tseglytskyi
2013-04-15 13:28 ` [RFC PATCH v2 5/6] ARM: OMAP3+: ABB: introduce " Andrii Tseglytskyi
2013-04-15 16:43 ` Mike Turquette
2013-04-16 11:28 ` Andrii Tseglytskyi
2013-04-15 13:28 ` [RFC PATCH v2 6/6] ARM: OMAP3+: ABB: introduce debugfs entry Andrii Tseglytskyi
2013-04-15 21:53 ` Kevin Hilman [this message]
2013-04-16 12:40 ` [RFC PATCH v2 0/6] ARM: OMAP3+: Introduce ABB driver Andrii Tseglytskyi
2013-04-16 19:07 ` Mike Turquette
2013-04-18 12:47 ` Grygorii Strashko
2013-04-16 19:18 ` Kevin Hilman
2013-04-18 10:55 ` 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=87sj2rbguv.fsf@linaro.org \
--to=khilman@linaro.org \
--cc=andrii.tseglytskyi@ti.com \
--cc=b-cousson@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@linaro.org \
--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 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).