All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Bard Liao <bardliao@realtek.com>
Cc: "Oder Chiou" <oder_chiou@realtek.com>,
	"Jack Yu" <jack.yu@realtek.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"lars@metafoo.de" <lars@metafoo.de>,
	"Takashi Iwai" <tiwai@suse.de>,
	"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
	"Shuming [范書銘]" <shumingf@realtek.com>, Flove <flove@realtek.com>
Subject: Re: [PATCH] ASoC: rt5670: add HS ground control
Date: Sat, 4 Feb 2017 17:11:14 +0100	[thread overview]
Message-ID: <20170204161114.v2cifi66qbybyizi@sirena.org.uk> (raw)
In-Reply-To: <ABFD875FF5FB574BA706497D987D48D70124DF38@RTITMBSV03.realtek.com.tw>


[-- Attachment #1.1: Type: text/plain, Size: 390 bytes --]

On Thu, Feb 02, 2017 at 02:38:55AM +0000, Bard Liao wrote:

> It is a codec GPIO, indeed. But we don't register it to gpiolib.
> So there is no other way to touch the GPIO. We are using it to
> do headset ground control and we should control its level according
> to if headset is using. That's why we control it by a DAPM event.

So one option here would be to register it with gpiolib...

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



      parent reply	other threads:[~2017-02-04 16:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-29  8:23 [PATCH] ASoC: rt5670: add HS ground control Bard Liao
2017-01-02 12:03 ` Takashi Iwai
2017-01-30  9:58 ` Takashi Iwai
2017-02-01 11:47   ` Mark Brown
2017-02-01 12:52     ` Takashi Iwai
2017-02-01 14:59       ` Mark Brown
2017-02-01 15:32         ` Takashi Iwai
2017-02-01 17:43           ` Mark Brown
     [not found]             ` <ABFD875FF5FB574BA706497D987D48D70124DF38@RTITMBSV03.realtek.com.tw>
2017-02-04 16:11               ` Mark Brown [this message]

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=20170204161114.v2cifi66qbybyizi@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=bardliao@realtek.com \
    --cc=flove@realtek.com \
    --cc=jack.yu@realtek.com \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    --cc=oder_chiou@realtek.com \
    --cc=shumingf@realtek.com \
    --cc=tiwai@suse.de \
    /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.