From: Kevin Hilman <khilman@deeprootsystems.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: Todd Fischer <todd.fischer@ridgerun.com>,
davinci-linux-open-source@linux.davincidsp.com,
lrg@slimlogic.co.uk, broonie@opensource.wolfsonmicro.com,
linux-input@vger.kernel.org
Subject: Re: [PATCH 0/2]-V2 Add touch screen input driver for TPS6507x family of multi-function chips.
Date: Wed, 07 Apr 2010 09:10:06 -0700 [thread overview]
Message-ID: <874ojnfdlt.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20100407084644.GB2962@sortiz.org> (Samuel Ortiz's message of "Wed\, 7 Apr 2010 10\:46\:45 +0200")
Samuel Ortiz <sameo@linux.intel.com> writes:
> Hi Todd, hi Kevin,
>
> On Mon, Apr 05, 2010 at 05:53:11PM -0600, Todd Fischer wrote:
>>
>> This is the second posting of the TPS6507x touch screen driver. I have
>> incorporated Kevin Hilman's request to split the board specific changes
>> into a separate patch.
>>
>> The TPS6507x family of Texas Instruments power management ICs (pmic)
>> are multi-function chips that include voltage regulation and touch
>> screen controller capabilities. This patch adds a touch screen
>> input driver for the TPS6507x pmic. There was an existing regulator
>> driver. Before the touch screen driver can be added, a multi-function
>> device (MFD) driver was needed and the regulator driver modified to
>> use the MDF driver. Patches for these changes have been posted and
>> reviewed. The TPS6507x touch screen driver applies cleanly to the
>> MFD GIT repo after the above referenced patches are applied. If I
>> should use a different approach, please let me know.
>>
>> The TPS6507x pmic supports interrupting on touch detection.
>> Unfortuntaly, the hardware used for driver development didn't have
>> the interrupt signal properly connected. When TPS6507x pmic interrupt
>> capable hardware is in hand, another patch will be posted adding
>> interrupt support.
>
> I've applied patch #1 of this patchset. Kevin, would you please take patch #2?
Thanks. Yes, patch #2 will be queued for linux-next and 2.6.35.
Kevin
next prev parent reply other threads:[~2010-04-07 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 23:53 [PATCH 0/2]-V2 Add touch screen input driver for TPS6507x family of multi-function chips Todd Fischer
2010-04-05 23:53 ` [PATCH 1/2] Touch " Todd Fischer
2010-04-05 23:53 ` [PATCH 2/2] TPS6507x touch screen driver board specific initialization values Todd Fischer
2010-04-07 8:46 ` [PATCH 0/2]-V2 Add touch screen input driver for TPS6507x family of multi-function chips Samuel Ortiz
2010-04-07 16:10 ` Kevin Hilman [this message]
2010-04-07 16:24 ` Kevin Hilman
2010-04-08 9:32 ` Samuel Ortiz
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=874ojnfdlt.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=linux-input@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=sameo@linux.intel.com \
--cc=todd.fischer@ridgerun.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 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.