All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: linux-input@vger.kernel.org
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	alsa-devel@alsa-project.org,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: [PATCH 2/2] Add possibility to control the GPIO_STATUS shift
Date: Fri, 17 Jul 2009 13:12:15 +0200	[thread overview]
Message-ID: <200907171312.15548.marek.vasut@gmail.com> (raw)
In-Reply-To: <20090717103253.GF3439@rakim.wolfsonmicro.main>

[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]

Dne Pá 17. července 2009 12:32:53 Mark Brown napsal(a):
> 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...

About the mailer, same here, sending as attachment, sorry.

The CPU used is pxa270c5 and pxa270c0. The chip is WM1613 (seems to report 
itself as WM9712 though). Maybe it's correction in that chip? There's no 
datasheet available to it though.


[-- Attachment #2: 0002-Add-possibility-to-control-the-GPIO_STATUS-shift.patch --]
[-- Type: text/x-patch, Size: 3449 bytes --]

From e7179d9d34b0a6078324fbe2c3666937937c0fde 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 de02f87..7b95741 100644
--- a/drivers/input/touchscreen/mainstone-wm97xx.c
+++ b/drivers/input/touchscreen/mainstone-wm97xx.c
@@ -198,6 +198,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 2957d48..6621c0e 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.3.3


  reply	other threads:[~2009-07-17 11:12 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 ` [PATCH 2/2] Add possibility to control the GPIO_STATUS shift Mark Brown
2009-07-17 11:12   ` Marek Vasut [this message]
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=200907171312.15548.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    /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.