From: Marek Vasut <marek.vasut@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Eric Miao <eric.y.miao@gmail.com>,
alsa-devel@alsa-project.org,
Russell King - ARM Linux <linux@arm.linux.org.uk>
Subject: Re: [PATCH] Fix possibly incorrect offset in wm97xx-core
Date: Thu, 4 Jun 2009 22:05:48 +0200 [thread overview]
Message-ID: <200906042205.48277.marek.vasut@gmail.com> (raw)
In-Reply-To: <20090604110609.GH6983@rakim.wolfsonmicro.main>
[-- Attachment #1: Type: text/plain, Size: 600 bytes --]
On Thursday 04 of June 2009 13:06:09 Mark Brown wrote:
> On Thu, Jun 04, 2009 at 11:59:02AM +0200, Marek Vasut wrote:
> > On Thursday 04 of June 2009 10:46:03 Mark Brown wrote:
> > > Nack, the existing code reflects the behaviour of the silicon.
> >
> > The patch above reflects the behavior of my silicon (WM9712G) :-/
>
> Could you expand on the behaviour you're seeing, please? Also, what are
> the full markings on the chip?
Actually, after discussing this on IRC with you, I come with the following
patch (it should be applied on top of the mainstone accelerated touch patch
which follows).
[-- Attachment #2: 0002-Add-possibility-to-control-the-GPIO_STATUS-shift.patch --]
[-- Type: text/x-diff, Size: 3449 bytes --]
From cb511c67296ed0cbb7b82a690cd4a027511b149b 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.
Signed-off-by: Marek Vasut <marek.vasut@gmail.com>
---
drivers/input/touchscreen/mainstone-wm97xx.c | 2 ++
drivers/input/touchscreen/wm97xx-core.c | 19 +++++++++----------
include/linux/wm97xx.h | 1 +
3 files changed, 12 insertions(+), 10 deletions(-)
diff --git a/drivers/input/touchscreen/mainstone-wm97xx.c b/drivers/input/touchscreen/mainstone-wm97xx.c
index 60bda9a..7ed54f5 100644
--- a/drivers/input/touchscreen/mainstone-wm97xx.c
+++ b/drivers/input/touchscreen/mainstone-wm97xx.c
@@ -200,6 +200,8 @@ static int wm97xx_acc_startup(struct wm97xx *wm)
if (machine_is_palmt5() || machine_is_palmtx() || machine_is_palmld()) {
pen_int = 1;
irq = 27;
+ wm->gpio_offset = 0; /* interestingly, on Palm hardware, the
+ * GPIO_STATUS shift doesn't occur */
} else if (machine_is_mainstone() && pen_int)
irq = 4;
diff --git a/drivers/input/touchscreen/wm97xx-core.c b/drivers/input/touchscreen/wm97xx-core.c
index 69af838..cada765 100644
--- a/drivers/input/touchscreen/wm97xx-core.c
+++ b/drivers/input/touchscreen/wm97xx-core.c
@@ -204,10 +204,7 @@ void wm97xx_set_gpio(struct wm97xx *wm, u32 gpio,
else
reg &= ~gpio;
- if (wm->id == WM9712_ID2)
- wm97xx_reg_write(wm, AC97_GPIO_STATUS, reg << 1);
- else
- wm97xx_reg_write(wm, AC97_GPIO_STATUS, reg);
+ wm97xx_reg_write(wm, AC97_GPIO_STATUS, reg << wm->gpio_offset);
mutex_unlock(&wm->codec_mutex);
}
EXPORT_SYMBOL_GPL(wm97xx_set_gpio);
@@ -307,12 +304,8 @@ static void wm97xx_pen_irq_worker(struct work_struct *work)
WM97XX_GPIO_13);
}
- if (wm->id == WM9712_ID2)
- wm97xx_reg_write(wm, AC97_GPIO_STATUS, (status &
- ~WM97XX_GPIO_13) << 1);
- else
- wm97xx_reg_write(wm, AC97_GPIO_STATUS, status &
- ~WM97XX_GPIO_13);
+ wm97xx_reg_write(wm, AC97_GPIO_STATUS, (status &
+ ~WM97XX_GPIO_13) << wm->gpio_offset);
mutex_unlock(&wm->codec_mutex);
}
@@ -582,6 +575,12 @@ static int wm97xx_probe(struct device *dev)
wm->id = wm97xx_reg_read(wm, AC97_VENDOR_ID2);
+ /* On some versions of WM9712, the GPIO_STATUS register is shifted */
+ if (wm->id == WM9712_ID2)
+ wm->gpio_offset = 1;
+ else
+ wm->gpio_offset = 0;
+
dev_info(wm->dev, "detected a wm97%02x codec\n", wm->id & 0xff);
switch (wm->id & 0xff) {
diff --git a/include/linux/wm97xx.h b/include/linux/wm97xx.h
index 6f69968..c6dc15b 100644
--- a/include/linux/wm97xx.h
+++ b/include/linux/wm97xx.h
@@ -283,6 +283,7 @@ struct wm97xx {
unsigned pen_is_down:1; /* Pen is down */
unsigned aux_waiting:1; /* aux measurement waiting */
unsigned pen_probably_down:1; /* used in polling mode */
+ unsigned gpio_offset:1; /* gpio register offset */
u16 suspend_mode; /* PRP in suspend mode */
};
--
1.6.2.1
[-- Attachment #3: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2009-06-04 20:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 21:44 [PATCH] Fix possibly incorrect offset in wm97xx-core Marek Vasut
2009-06-04 8:46 ` Mark Brown
2009-06-04 9:59 ` Marek Vasut
2009-06-04 11:06 ` Mark Brown
2009-06-04 20:05 ` Marek Vasut [this message]
2009-06-05 8:51 ` 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=200906042205.48277.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=eric.y.miao@gmail.com \
--cc=linux@arm.linux.org.uk \
/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.