From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
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, 08 May 2019 11:16:18 +0200 [thread overview]
Message-ID: <s5h5zqlnw65.wl-tiwai@suse.de> (raw)
In-Reply-To: <20190508085953.GF14916@sirena.org.uk>
On Wed, 08 May 2019 10:59:53 +0200,
Mark Brown wrote:
>
> 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.
But what gives a benefit? It needs more plumbing between codec and
machine driver. The i2c probe doesn't give the irq, so you'd need and
extra stuff to enable the irq in a different route if you'd need to
implement the handler in the codec driver.
Actually, my latest patchset already eliminates the exported stuff by
moving to set_jack callback like some other drivers do. If you have
an idea for further simplification / fixes, let me know.
I haven't submitted because of the merge window. The patch is found
at topic/soc-cx2072x-5.2 branch, the commit is
https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?h=topic/soc-cx2072x-5.2&id=ca7f4eee5ecbefcf347f5a4984c0a17629360186
thanks,
Takashi
next prev parent reply other threads:[~2019-05-08 9:16 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
2019-05-08 9:16 ` Takashi Iwai [this message]
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=s5h5zqlnw65.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=pierre-louis.bossart@linux.intel.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