devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Lübbe" <jlu@pengutronix.de>
To: Russ Dill <Russ.Dill@ti.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>,
	devicetree@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 0/4] ARM: OMAP2+: AM33XX: VDD CORE OPP50 support
Date: Thu, 15 Aug 2013 10:00:40 +0200	[thread overview]
Message-ID: <1376553640.3889.70.camel@coredoba.hi.pengutronix.de> (raw)
In-Reply-To: <CA+Bv8XYe0UzBkjqtO7bNkgNVTQtxiM7Hv93BOu8Lw1=pESOwLA@mail.gmail.com>

On Wed, 2013-08-14 at 15:21 -0700, Russ Dill wrote:
> > The CM3 driver needs to figure out where the core regulator is connected
> > using using either DT or the regulator framework and ask the TPS (via a
> > new interface) for register writes for sleep/wake sequences. Then those
> > sequences will actually match the correct voltages configured using
> > DT/DVFS.
> 
> That seems like it'd add a lot of complexity to the regulator
> subsystem, as well as all the PMIC and other I2C regulators that any
> users of these device tree properties may end up using for not a lot
> of gain. There would be two separate code paths for any used
> I2C regulator or PMIC for setting voltages.

Yes, it would be additional complexity, but it would avoid duplicating
information which is already in the DT (location&address of the PMIC,
type of pmic) and in the kernel (how to program voltages for a given
regulator). As DT is supposed to describe the hardware, duplicate
information should be unnecessary.

One different way to look at this is that the CM3 firmware is a separate
consumer of the DT. DT being OS-indepentent, the CM3 firmware should be
able to get all the information it needs from the DT (maybe with help
from the CM3 driver).

Regards,
Jan 

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |


  reply	other threads:[~2013-08-15  8:00 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-13 22:20 [PATCH v4 0/4] ARM: OMAP2+: AM33XX: VDD CORE OPP50 support Russ Dill
2013-08-13 22:20 ` [PATCH v4 1/4] ARM: OMAP2+: AM33XX: I2C Sleep/wake sequence support Russ Dill
2013-08-14 10:18   ` Gururaja Hebbar
2013-08-14 22:34     ` Russ Dill
2013-08-16  7:16       ` Gururaja Hebbar
2013-08-19  5:49       ` Gururaja Hebbar
2013-08-20 16:33         ` Russ Dill
2013-08-21  8:29           ` Gururaja Hebbar
2013-08-13 22:20 ` [PATCH v4 2/4] ARM: dts: add AM33XX vdd core opp50 suspend for Beaglebone Russ Dill
2013-08-14  8:59   ` Gururaja Hebbar
2013-08-14 22:21     ` Russ Dill
2013-08-13 22:20 ` [PATCH v4 3/4] ARM: dts: add AM33XX vdd core opp50 suspend for AM335X GP EVM Russ Dill
2013-08-13 22:20 ` [PATCH v4 4/4] ARM: dts: AM33XX vdd core opp50 suspend for EVM-SK Russ Dill
2013-08-14 13:38 ` [PATCH v4 0/4] ARM: OMAP2+: AM33XX: VDD CORE OPP50 support Jan Lübbe
2013-08-14 22:21   ` Russ Dill
2013-08-15  8:00     ` Jan Lübbe [this message]
2013-08-27 22:44     ` Kevin Hilman
2013-08-28  1:05       ` Russ Dill
2013-08-29 11:05         ` Mark Brown
2013-08-29 15:29           ` Kevin Hilman
2013-08-29 15:49             ` Mark Brown
2013-08-29 16:31               ` Russ Dill
2013-08-29 17:30                 ` Mark Brown
2013-08-29 17:47                   ` Russ Dill
2013-08-29 18:03                     ` Mark Brown
2013-08-29 18:28                       ` Russ Dill
2013-08-29 15:42           ` Russ Dill
2013-08-29 18:01             ` Mark Brown
2013-08-29 18:25               ` Russ Dill
2013-08-29 19:10                 ` Mark Brown
2013-09-03 14:06                   ` Russ Dill
2013-09-03 14:39                     ` Mark Brown
2013-08-29 15:17         ` Kevin Hilman
2013-08-29 16:10           ` Russ Dill
2013-08-29 19:11             ` Kevin Hilman
2013-08-29 20:09               ` Vaibhav Bedia
2013-08-29 21:33                 ` Kevin Hilman
2013-08-30  0:25                   ` Russ Dill
2013-08-30 16:06                     ` Kevin Hilman
2013-09-03 18:55                       ` Russ Dill
2013-09-03 19:07                         ` Kevin Hilman
2013-08-30 17:57                   ` Vaibhav Bedia

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=1376553640.3889.70.camel@coredoba.hi.pengutronix.de \
    --to=jlu@pengutronix.de \
    --cc=Russ.Dill@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=devicetree@vger.kernel.org \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.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).