From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Marek Vasut <marek.vasut@gmail.com>,
linux-input@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH 2/2] Add possibility to control the GPIO_STATUS shift
Date: Mon, 20 Jul 2009 22:45:36 -0700 [thread overview]
Message-ID: <20090721054536.GA4671@dtor-d630.eng.vmware.com> (raw)
In-Reply-To: <20090717145203.GA15061@rakim.wolfsonmicro.main>
On Fri, Jul 17, 2009 at 03:52:03PM +0100, Mark Brown wrote:
> On Fri, Jul 17, 2009 at 04:45:21PM +0200, Marek Vasut wrote:
>
> > From 1ea286d088993e05b5b374a08ee6f933242d3561 Mon Sep 17 00:00:00 2001
> > From: Marek Vasut <marek.vasut@gmail.com>
> > Date: Thu, 4 Jun 2009 21:56:59 +0200
> > Subject: [PATCH 2/2] Add possibility to control the GPIO_STATUS shift
> >
> > This patch allows tweaking the behaviour of GPIO_STATUS register
> > shift quirk that's in wm97xx-core. The problem with GPIO_STATUS
> > register being shifted by one doesn't appear on all hardware it
> > seems and causes problems with accelerated touchscreen drivers on
> > Palm hardware. Therefore an accelerated touchscreen driver can select
> > if the shift is/isn't happening on the hardware.
>
> Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
>
Applied both patches to 'next', thank you Marek.
--
Dmitry
prev parent reply other threads:[~2009-07-21 5:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200907171001.16889.marek.vasut@gmail.com>
[not found] ` <20090717103253.GF3439@rakim.wolfsonmicro.main>
2009-07-17 11:12 ` [PATCH 2/2] Add possibility to control the GPIO_STATUS shift Marek Vasut
2009-07-17 11:22 ` Mark Brown
2009-07-17 11:26 ` Marek Vasut
2009-07-17 11:43 ` Mark Brown
2009-07-17 11:53 ` Marek Vasut
2009-07-17 12:11 ` Mark Brown
2009-07-17 14:45 ` Marek Vasut
2009-07-17 14:52 ` Mark Brown
2009-07-21 5:45 ` Dmitry Torokhov [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=20090721054536.GA4671@dtor-d630.eng.vmware.com \
--to=dmitry.torokhov@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-input@vger.kernel.org \
--cc=marek.vasut@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;
as well as URLs for NNTP newsgroup(s).