Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: linux-input@vger.kernel.org, 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:11:59 +0100	[thread overview]
Message-ID: <20090717121159.GA20904@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <200907171353.59356.marek.vasut@gmail.com>

On Fri, Jul 17, 2009 at 01:53:59PM +0200, Marek Vasut wrote:
> Dne Pá 17. července 2009 13:43:12 Mark Brown napsal(a):

> > The same way your current patch does it.  I'm just saying you should
> > change the way the configuration is passed in so that it is clear that
> > this is only useful for WM1613.

> But there might appear some other chips that have this issue.

Then they can get handled the same way - it might be an idea to have the
data that's passed in be a chip number to allow for this.
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-07-17 12:11 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
2009-07-17 11:43         ` Mark Brown
2009-07-17 11:53           ` Marek Vasut
2009-07-17 12:11             ` Mark Brown [this message]
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=20090717121159.GA20904@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=dmitry.torokhov@gmail.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