From: Mike Rapoport <mike.rapoport@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: 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: Fri, 5 Feb 2010 22:45:09 +0200 [thread overview]
Message-ID: <f870da181002051245t2f37065duae595fee391e7fd9@mail.gmail.com> (raw)
In-Reply-To: <20100204162155.GB29982@rakim.wolfsonmicro.main>
On Thu, Feb 4, 2010 at 6:21 PM, Mark Brown
<broonie@opensource.wolfsonmicro.com> wrote:
> On Thu, Feb 04, 2010 at 04:52:26PM +0200, Grazvydas Ignotas wrote:
>> On Thu, Feb 4, 2010 at 4:24 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...
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" 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.
--
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
next prev parent reply other threads:[~2010-02-05 20:45 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 [this message]
2010-02-08 11:30 ` Mark Brown
2010-02-09 8:55 ` Mike Rapoport
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=f870da181002051245t2f37065duae595fee391e7fd9@mail.gmail.com \
--to=mike.rapoport@gmail.com \
--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=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