From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC][PATCH v4? 0/7] Adaptive Body-Bias for OMAP
Date: Tue, 16 Oct 2012 09:32:25 -0700 [thread overview]
Message-ID: <20121016163225.GQ15569@atomide.com> (raw)
In-Reply-To: <20121011222107.2941.62545@nucleus>
* Mike Turquette <mturquette@ti.com> [121011 15:27]:
> Quoting Nishanth Menon (2012-10-11 06:33:04)
> > On 18:26-20121003, Mike Turquette wrote:
> > > From: Mike Turquette <mturquette@linaro.org>
> > [...]
> > >
> > > arch/arm/mach-omap2/Makefile | 8 +-
> > > arch/arm/mach-omap2/abb.c | 322 +++++++++++++++++++++++++
> > > arch/arm/mach-omap2/abb.h | 94 ++++++++
> > [...]
> > > arch/arm/plat-omap/include/plat/voltage.h | 1 +
> > > 18 files changed, 699 insertions(+), 37 deletions(-)
> > > create mode 100644 arch/arm/mach-omap2/abb.c
> > > create mode 100644 arch/arm/mach-omap2/abb.h
> > > create mode 100644 arch/arm/mach-omap2/abb36xx_data.c
> > > create mode 100644 arch/arm/mach-omap2/abb44xx_data.c
> >
> > dumb question: with the request to move everything out of mach-omap2
> > directory, do we still want to add more files into mach-omap2?
> >
>
> Not a dumb question at all. I approached this problem by modeling it
> after existing voltage layer code (in particular the vp and vc drivers).
>
> My hope is to get it merged as-is and then bundle the abb code up with
> the vp/vc migration to drivers/* when that happens some day. People
> using omap36xx and above need this code now, so it seems prudent to take
> this approach today.
This is needed, but makes moving the vc code to drivers a bit
more complex.
So we also need a plan to move this all to drivers in the follow
up patches. And we need a maintainer for the code. Who is going to
be doing all that?
Regards,
Tony
next prev parent reply other threads:[~2012-10-16 16:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 1:26 [RFC][PATCH v4? 0/7] Adaptive Body-Bias for OMAP Mike Turquette
2012-10-04 1:26 ` [PATCH 1/7] ARM: omap: add 3630 PRM register definitions Mike Turquette
2012-10-04 1:26 ` [PATCH 2/7] ARM: omap: add ABB PRM_IRQSTATUS handlers Mike Turquette
2012-10-04 1:26 ` [PATCH 3/7] ARM: omap: Adaptive Body-Bias structures & data Mike Turquette
2012-10-04 1:26 ` [PATCH 4/7] ARM: omap: opp: add ABB data to voltage tables Mike Turquette
2012-10-04 1:26 ` [PATCH 5/7] ARM: omap: voltage: per-voltage domain ABB data Mike Turquette
2012-10-04 1:26 ` [PATCH 6/7] ARM: omap: abb: init & transition functions Mike Turquette
2012-10-04 2:26 ` Dimitar Dimitrov
2012-10-04 1:26 ` [PATCH 7/7] ARM: omap: voltage: add ABB to voltage scaling Mike Turquette
2012-10-11 13:33 ` [RFC][PATCH v4? 0/7] Adaptive Body-Bias for OMAP Nishanth Menon
2012-10-11 22:21 ` Mike Turquette
2012-10-16 16:32 ` Tony Lindgren [this message]
2012-10-16 17:06 ` Mike Turquette
2012-10-16 21:50 ` Kevin Hilman
2012-10-16 21:59 ` Tony Lindgren
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=20121016163225.GQ15569@atomide.com \
--to=tony@atomide.com \
--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 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).