[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130205120134.GY4720@opensource.wolfsonmicro.com>
Date: Tue, 5 Feb 2013 12:01:35 +0000
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Lee Jones <lee.jones@...aro.org>, linux-kernel@...r.kernel.org,
Bengt Jonsson <bengt.g.jonsson@...ricsson.com>,
Ulf Hansson <ulf.hansson@...aro.org>
Subject: Re: [PATCH 05/73] ARM: ux500: Vsmps3 controlled by SysClkReq1
On Mon, Feb 04, 2013 at 10:21:36PM +0100, Linus Walleij wrote:
> What is needed is some way to model that
> electronic relationship into both the regulator
> and clock subsystems (Ulf Hansson is working on
> the ABx500 clocks as we speak.)
> Maybe the actual place to have it would be
> somewhere like drivers/mfd/ab8500-core.c.
> Have you seen similar stuff in other PMICs?
Yes, it's fairly common to at least have hardware enable signals. If
what was going on was actually understood by the driver in some way it
might be better but right now... Especially in a series like this it's
really bad to just see loads of patches which boil down to "change the
semi-documented magic value" - this just makes the series depressing to
read.
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists