From: Mike Rapoport <mike@compulab.co.il>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Mike Rapoport <mike.rapoport@gmail.com>,
Grazvydas Ignotas <notasas@gmail.com>,
linux-input@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-omap@vger.kernel.org, lrg@slimlogic.co.uk
Subject: Re: [PATCH] Input: ads7846: add regulator support
Date: Tue, 09 Feb 2010 10:55:41 +0200 [thread overview]
Message-ID: <4B71230D.1000900@compulab.co.il> (raw)
In-Reply-To: <20100208113028.GA15630@rakim.wolfsonmicro.main>
Mark Brown wrote:
> On Fri, Feb 05, 2010 at 10:45:09PM +0200, Mike Rapoport wrote:
>> On Thu, Feb 4, 2010 at 6:21 PM, Mark Brown
>
>>> The bodge I'm thinking of would do something like log an error and
>>> substitute in a dummy regulator when regulator_get() would have failed
>>> so that the driver sees behaviour equivalent to the stubbed regulator
>>> API if the bodge is active. A central thing seems much more sensible
>>> here - there's nothing specific to this driver going on here and having
>>> the API behave in a consistent manner seems good.
>
>> I agree that such approach have more sense than checking for -ENODEV
>> in each and every driver that uses the regulator framework. I just
>> wonder, if there should be some mechanism that can switch the
>> substitution of the dummy regulators on and off. And if yes, how
>> should the platform code communicate with the regulator core the need
>> for such dummy regulators...
>
> So, having thought about this a bit more we actually have two different
> use cases here. One is where you've got a system which has software
> controllable regulators for everything but may not have plumbed in all
> the supplies, the other is for systems where only a very few supplies
> are on software controlled regulators which are just trying to save the
> hassle of hooking up the bulk of the supplies to fixed voltage
> regulators. These two use cases should probably be handled differently
> - the first one is really expected to have all the supplies hooked up
> and so should warn when using the bodge regulator but the warning isn't
> helpful in the second case.
Sounds right to me.
> We already have some support for boards to set up the API in the form of
> regulator_set_full_constraints() so we could do something similar for
> dummy regulators, or create a new single API to set a bunch of options
> via a struct which is probably less hassle going forward.
Struct sounds more reasonable that just a call to e.g.
regulator_warn_dummy_fixed_regulator :)
> --
> To unsubscribe from this list: send the line "unsubscribe linux-input" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2010-02-09 8:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 13:39 [PATCH] Input: ads7846: add regulator support Grazvydas Ignotas
2010-02-04 14:24 ` Mark Brown
2010-02-04 14:52 ` Grazvydas Ignotas
2010-02-04 16:21 ` Mark Brown
2010-02-04 18:08 ` Dmitry Torokhov
2010-02-04 18:59 ` Mark Brown
2010-02-05 20:45 ` Mike Rapoport
2010-02-08 11:30 ` Mark Brown
2010-02-09 8:55 ` Mike Rapoport [this message]
2010-02-04 15:08 ` Mike Rapoport
2010-02-04 16:03 ` 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=4B71230D.1000900@compulab.co.il \
--to=mike@compulab.co.il \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=mike.rapoport@gmail.com \
--cc=notasas@gmail.com \
/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