All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Agrawal, Akshu" <aagrawal2@amd.com>
To: "Shuming [范書銘]" <shumingf@realtek.com>,
	"Akshu Agrawal" <akshu.agrawal@amd.com>
Cc: Oder Chiou <oder_chiou@realtek.com>,
	"moderated list:SOUND" <alsa-devel@alsa-project.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	open list <linux-kernel@vger.kernel.org>,
	Takashi Iwai <tiwai@suse.com>, Mark Brown <broonie@kernel.org>,
	"yuhsuan@chromium.org" <yuhsuan@chromium.org>,
	"Flove(HsinFu)" <flove@realtek.com>
Subject: Re: [alsa-devel] [PATCH] ASoC: rt5682: Add option to select pulse IRQ in jack detect
Date: Mon, 23 Dec 2019 15:08:18 +0530	[thread overview]
Message-ID: <21ae77ee-c0d1-838f-56e6-a931451b0f6e@amd.com> (raw)
In-Reply-To: <55cbcef1d09e43e0aac057b680c25e17@realtek.com>


On 12/23/2019 1:28 PM, Shuming [范書銘] wrote:
>> Subject: [alsa-devel] [PATCH] ASoC: rt5682: Add option to select pulse IRQ in
>> jack detect
>>
>> Some SoC need to set IRQ type as pulse along with other JD1 options.
> Could you configure GPIO IRQ by edge trigger(both rising/falling) and try again?
> BTW, the modification doesn't make sense to name JD2.

Thanks Shuming, was about to send a mail to abandon this patch request.

The GPIO connected to codec is not a traditional one, but a wake event. 
Hence, it took us time to figure out the way to set it active on both 
the edges.


Regards,

Akshu


      reply	other threads:[~2019-12-23  9:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-20  6:12 [PATCH] ASoC: rt5682: Add option to select pulse IRQ in jack detect Akshu Agrawal
2019-12-20  6:12 ` [alsa-devel] " Akshu Agrawal
2019-12-23  6:26 ` kbuild test robot
2019-12-23  6:26   ` kbuild test robot
2019-12-23  6:26   ` [alsa-devel] " kbuild test robot
2019-12-23  7:58 ` Shuming [范書銘]
2019-12-23  9:38   ` Agrawal, Akshu [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=21ae77ee-c0d1-838f-56e6-a931451b0f6e@amd.com \
    --to=aagrawal2@amd.com \
    --cc=akshu.agrawal@amd.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=flove@realtek.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oder_chiou@realtek.com \
    --cc=shumingf@realtek.com \
    --cc=tiwai@suse.com \
    --cc=yuhsuan@chromium.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.