From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] regulator/fixed: set constraints.apply_uV to 0
Date: Mon, 2 Jan 2012 14:39:05 +0000 [thread overview]
Message-ID: <20120102143904.GQ4300@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAH8gqwXopRx7_-wSq9djb_np+XeZE0w1HJ1XxZozGOBCF8Z+ZQ@mail.gmail.com>
On Mon, Jan 02, 2012 at 09:46:01PM +0800, Richard Zhao wrote:
> On 1 January 2012 05:59, Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:
> > It's not code which is specific to the fixed regulator, it's generic
> > code that's used by all regulators.
> The original patch is in fixed regulator driver.
Your original patch made no mention of device tree, it just had the
driver modify its constraints which is clearly not good - aside from the
design issue what happens if we make const data read only? Any boards
that have their constraints marked const will start oopsing. Your new
patch makes it impossible to apply a voltage to *any* regulator on a
device tree which is going to break any system that needs to apply a
voltage.
You really need to take a step back, think about the consequences of the
changes you're making and make changes that also make sense at a design
level. You can't think only about the one board that you're currently
working on, it's important that you consider the wider effects of your
change.
To repeat my previous suggestions you could either make the system more
forgiving of silly constraints where that makes sense (and remember that
one of the reasons the core rejects silly constraints is that it wants
to make absolutely clear that the user wrote what they meant) or make
sure that silly constraints aren't written in the first place. For
example, why not make this a device tree specific change?
> >> Could you please past some code to show your suggested solution,
> >> or you send out a patch to fix it?
> > Not in the immediate future.
> It's a __bug__ blocking others to use fixed regulator with dt binding.
There's some fairly clear and obvious directions to look at and simply
demanding that I drop everything and implement them for you too isn't
really inspiring me to do so.
next prev parent reply other threads:[~2012-01-02 14:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 6:06 [PATCH 1/1] regulator/fixed: set constraints.apply_uV to 0 Richard Zhao
2011-12-30 10:30 ` Mark Brown
2011-12-30 10:38 ` Richard Zhao
2011-12-30 10:48 ` Mark Brown
2011-12-30 11:08 ` Richard Zhao
2011-12-31 1:02 ` Mark Brown
2011-12-31 1:26 ` Richard Zhao
2011-12-31 21:59 ` Mark Brown
2012-01-02 13:46 ` Richard Zhao
2012-01-02 14:39 ` Mark Brown [this message]
2012-01-04 2:47 ` Richard Zhao
2011-12-31 12:51 ` [PATCH 1/1] regulator/fixed: pass regulator_register of_node Richard Zhao
2012-01-02 12:46 ` Mark Brown
2012-01-02 13:22 ` Richard Zhao
2012-01-04 3:07 ` [PATCH v2 1/1] regulator: set constraints.apply_uV to 0 in of_get_fixed_voltage_config Richard Zhao
2012-01-04 3:07 ` Richard Zhao
2012-01-06 9:51 ` Richard Zhao
2012-01-06 9:51 ` Richard Zhao
2012-01-06 18:43 ` Mark Brown
2012-01-06 18:43 ` Mark Brown
2012-01-06 19:01 ` Mark Brown
2012-01-06 19:01 ` Mark Brown
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=20120102143904.GQ4300@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.