From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH 2/2] Add possibility to control the GPIO_STATUS shift
Date: Fri, 17 Jul 2009 11:32:53 +0100 [thread overview]
Message-ID: <20090717103253.GF3439@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <200907171001.16889.marek.vasut@gmail.com>
On Fri, Jul 17, 2009 at 10:01:16AM +0200, Marek Vasut wrote:
> 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.
Again, this isn't an ALSA patch.
I've done some checking internally and I'm very suspicous that what's
going on here is actually the masking of some other bug elsewhere in the
system. Which CPU are the systems you're observing this on using?
There is at least one special case in the current code for GPIO register
readbacks in the PXA AC97 driver code and there have been a number of
interoperabilty issues in that area...
next parent reply other threads:[~2009-07-17 10:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200907171001.16889.marek.vasut@gmail.com>
2009-07-17 10:32 ` Mark Brown [this message]
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
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=20090717103253.GF3439@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.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 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.