From: Mark Brown <broonie@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: [PATCH 1/2] ASoC: Add support for Conexant CX2072X CODEC
Date: Wed, 8 May 2019 17:59:53 +0900 [thread overview]
Message-ID: <20190508085953.GF14916@sirena.org.uk> (raw)
In-Reply-To: <s5hk1f1nyyh.wl-tiwai@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 938 bytes --]
On Wed, May 08, 2019 at 10:16:06AM +0200, Takashi Iwai wrote:
> Mark Brown wrote:
> > The GPIO/IRQ equivalence thing should just be a purely Linux internal
> > thing - looking at the driver it appears that there's no need to look at
> > the GPIO status, Linux can tell if something is plugged in purely by
> > reading the chip registers so the jack status function could directly be
> > the interrupt handler.
> But it can't see the button status or detect the headset type without
> reading the codec's magic registers... So some help from the codec
> side is required, and the irq handler isn't in the codec side because
The whole thing should be in the CODEC side.
> there is no i2c irq assigned but only ACPI gpio, as far as I checked.
You can map through an ACPI GPIO to an interrupt without worrying about
the fact that it's mapped as a GPIO in ACPI IIRC - if you can't there's
lots of other drivers are going to have issues.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2019-05-08 9:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 14:13 [PATCH 0/2] ASoC: CX2072X codec support (revised) Takashi Iwai
2019-04-23 14:13 ` [PATCH 1/2] ASoC: Add support for Conexant CX2072X CODEC Takashi Iwai
2019-04-27 17:59 ` Mark Brown
2019-05-02 7:04 ` Takashi Iwai
2019-05-02 7:52 ` Takashi Iwai
2019-05-03 6:52 ` Mark Brown
[not found] ` <20190503064729.GF14916@sirena.org.uk>
2019-05-03 7:18 ` Takashi Iwai
[not found] ` <20190506042625.GK14916@sirena.org.uk>
2019-05-06 9:55 ` Takashi Iwai
2019-05-06 14:05 ` Mark Brown
2019-05-06 15:26 ` Takashi Iwai
2019-05-08 8:10 ` Mark Brown
2019-05-08 8:16 ` Takashi Iwai
2019-05-08 8:59 ` Mark Brown [this message]
2019-05-08 9:16 ` Takashi Iwai
2019-05-08 10:10 ` Mark Brown
2019-05-03 8:05 ` Takashi Iwai
2019-04-23 14:13 ` [PATCH 2/2] ASoC: Intel: Add machine driver for CX2072X on BYT/CHT platforms Takashi Iwai
2019-04-23 19:20 ` Pierre-Louis Bossart
2019-04-23 19:39 ` Takashi Iwai
2019-04-24 13:08 ` Takashi Iwai
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=20190508085953.GF14916@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=pierre-louis.bossart@linux.intel.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.