From: Grazvydas Ignotas <notasas@gmail.com>
To: Steve Sakoman <sakoman@gmail.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH v2] Input: ads7846: add regulator support
Date: Tue, 20 Apr 2010 22:21:57 +0300 [thread overview]
Message-ID: <j2p6ed0b2681004201221y6ae69bedp649845f94de64896@mail.gmail.com> (raw)
In-Reply-To: <p2j5e088bd91004200931ucbf1eedvc710bebf8236dc1a@mail.gmail.com>
On Tue, Apr 20, 2010 at 7:31 PM, Steve Sakoman <sakoman@gmail.com> wrote:
> On Sat, Feb 13, 2010 at 9:31 AM, Grazvydas Ignotas <notasas@gmail.com> wrote:
>> The ADS7846/TSC2046 touchscreen controllers can (and usually are)
>> connected to various regulators for power, so add regulator support.
>>
>> Valid regulator will now be required, so boards without complete
>> regulator setup should either disable regulator framework or enable
>> CONFIG_REGULATOR_DUMMY.
>
> I'd prefer not to completely disable the regulator framework and my
> 2.6.33 kernel tree doesn't seem to have the CONFIG_REGULATOR_DUMMY
> option.
Then how did this patch reach your tree? I don't see this in mainline 2.6.33.
> Is there a simple way to handle the case (as exists with the Gumstix
> Overo) where the ADS7846 is supplied by a fixed regulator with no
> software controls?
Not without patching I guess. Otherwise you can set up
reg-fixed-voltage platform device in board file (see
arch/arm/mach-pxa/raumfeld.c for an example), add dummy regulator
patches from mainline of just revert this patch.
>
> Steve
>
prev parent reply other threads:[~2010-04-20 19:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-13 16:31 [PATCH v2] Input: ads7846: add regulator support Grazvydas Ignotas
2010-02-13 18:49 ` Mark Brown
2010-02-25 10:01 ` Dmitry Torokhov
2010-02-13 19:40 ` Mike Rapoport
2010-02-13 19:52 ` Mark Brown
2010-04-20 16:31 ` Steve Sakoman
2010-04-20 19:21 ` Grazvydas Ignotas [this message]
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=j2p6ed0b2681004201221y6ae69bedp649845f94de64896@mail.gmail.com \
--to=notasas@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=sakoman@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