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

Dne Pá 17. července 2009 13:22:15 Mark Brown napsal(a):
> On Fri, Jul 17, 2009 at 01:12:15PM +0200, Marek Vasut wrote:
> > 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.
>
> Ah, that is crucial information which you hadn't previously provided.
> If you rework the patch as adding support for WM1613 with the interface
> being one that enables a WM1613 mode rather than tweaking the GPIO
> offset that'd be OK.

But how the heck am I supposed to detect it's wm1613 if it reports itself as 
wm9712 ? Apparently, on treo680 it reports itself as wm9713 (even better).
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2009-07-17 11:26 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
2009-07-17 11:22     ` Mark Brown
2009-07-17 11:26       ` Marek Vasut [this message]
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=200907171326.08512.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.