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 2/4] OMAP: OPP: twl/tps: Introduce TWL/TPS-specific code
Date: Thu, 16 Sep 2010 10:16:00 -0700	[thread overview]
Message-ID: <874odpbodr.fsf@deeprootsystems.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB03294424F5@dbde02.ent.ti.com> (Thara Gopinath's message of "Thu, 16 Sep 2010 16:10:06 +0530")

"Gopinath, Thara" <thara@ti.com> writes:

[...]

>>>From: Paul Walmsley <paul@pwsan.com>
>>>
>>>The OPP layer code should be independent of the PMIC,
>>>introduce the TWL/TPS-specific code out to its own file.
>
> Hello Kevin,
>
> I have been using this code for a while now. I really do not think wee
> need a separate file for implementing the vsel to voltage in (uV) and
> vice versa formulas. Today only voltage layer is interested in these
> conversions. Voltage layer has a structure that can be populated with
> the information required from the PMIC. We only need to add two more
> function pointers to this structure. This info can then be passed from
> the actual PMIC driver file. This will make it much more simpler for
> OMAP4 where we have different formulas between different revisions of
> PMIC. Also in the omap voltage code we will no longer have to hard
> code omap_twl_vsel_to_uv and omap_twl_uv_to_vsel. 

Feel free to post an RFC series for what you're proposing.  

IMHO, even the voltage layer should not care about these conversions.
The voltage layer should care about voltages, and the PMIC layer should
handle these conversions.  IOW, this stuff is best abstracted in the
PMIC code, or board- or SoC-specific hooks that can be registered with
the PMIC.

> So please consider dropping this patch from this series.

If you pick this up as part of your voltage series (or more likely as a
pre-requisite of your voltage series) we can surely drop it from this
series, at it doesn't really belong with the OPP series.

There are no upstream users of this yet, so dropping it is easy. :)

Kevin

  parent reply	other threads:[~2010-09-16 17:16 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
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 [this message]
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=874odpbodr.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).