linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: khilman@deeprootsystems.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] OMAP: introduce OPP layer for device-specific OPPs
Date: Thu, 16 Sep 2010 08:48:23 -0700	[thread overview]
Message-ID: <87vd65bsfs.fsf@deeprootsystems.com> (raw)
In-Reply-To: <4C92386F.2070600@ti.com> (Nishanth Menon's message of "Thu, 16 Sep 2010 10:31:59 -0500")

Nishanth Menon <nm@ti.com> writes:

> Kevin Hilman had written, on 09/16/2010 10:08 AM, the following:
> [..]
>>> more than that you name
>>> some functions omap_*, and how hard would it be to put it under
>>> arch/arm/common/*.c
>>> arch/arm/include/asm/*.h
>>>
>>> Possible even higher up in the directory hiearchy in include/linux/opp.h
>>> for the header and drivers/opp/*.c, because I think SuperH and power
>>> are not that different in this respect.
>>
>> Yeah, I guess this isn't ARM specific either, so should be at a higher
>> level. 
>>
>> Nishanth, can take my hack below and continue this evolution?  As I
>> demonstrate with this hack, this won't really change anything for us.
>
> thanks..  The only contention ahead is: where do we want this?
> Is drivers/opp/opp_core.c the right place? Given that this is just a
> support library and not really a driver? for some reason lib/opp.c
> does'nt sound just right either :(

Well, since it's not really a driver, I don't think drivers/* is
appropriate.

lib/opp/* seems more appropriate to me with the header at
include/linux/opp.h as Linus suggested.

Kevin

  reply	other threads:[~2010-09-16 15:48 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-15 21:56 [PATCH 0/4] OMAP OPP layer for 2.6.37 Kevin Hilman
2010-09-15 21:56 ` [PATCH 1/4] OMAP: introduce OPP layer for device-specific OPPs Kevin Hilman
2010-09-16 10:25   ` Gopinath, Thara
2010-09-16 10:32     ` Menon, Nishanth
2010-09-16 10:33       ` Gopinath, Thara
2010-09-16 12:19   ` Linus Walleij
2010-09-16 12:40     ` Nishanth Menon
2010-09-16 13:24       ` Linus Walleij
2010-09-16 15:08     ` Kevin Hilman
2010-09-16 15:31       ` Nishanth Menon
2010-09-16 15:48         ` Kevin Hilman [this message]
2010-09-16 17:07           ` Linus Walleij
2010-09-16 17:10             ` Nishanth Menon
2010-09-16 17:13               ` Shilimkar, Santosh
2010-09-16 18:01                 ` Kevin Hilman
2010-09-16 13:54   ` Roger Quadros
2010-09-16 14:01     ` Nishanth Menon
2010-09-16 14:20       ` Roger Quadros
2010-09-16 14:43         ` Nishanth Menon
2010-09-15 21:56 ` [PATCH 2/4] OMAP: OPP: twl/tps: Introduce TWL/TPS-specific code Kevin Hilman
2010-09-16 10:40   ` Gopinath, Thara
2010-09-16 12:15     ` Nishanth Menon
2010-09-16 13:51       ` Gopinath, Thara
2010-09-16 14:06         ` Nishanth Menon
2010-09-17 14:57           ` Gopinath, Thara
2010-09-17 15:03             ` Nishanth Menon
2010-09-16 17:16     ` Kevin Hilman
2010-09-17 15:11       ` Gopinath, Thara
2010-09-15 21:56 ` [PATCH 3/4] OMAP3: remove OPP interfaces from OMAP PM layer Kevin Hilman
2010-09-15 21:56 ` [PATCH 4/4] OMAP3: OPP: add OPP table data and initialization Kevin Hilman

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=87vd65bsfs.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.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).