From: Mark Brown <broonie@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Cezary Rojewski <cezary.rojewski@intel.com>,
alsa-devel@alsa-project.org, Jie Yang <yang.jie@linux.intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Bard Liao <bard.liao@intel.com>
Subject: Re: [PATCH 2/5] ASoC: rt5640: Allow snd_soc_component_set_jack() to override the codec IRQ
Date: Fri, 31 Dec 2021 13:22:57 +0000 [thread overview]
Message-ID: <Yc8EMRxc07NphgcR@sirena.org.uk> (raw)
In-Reply-To: <20211227153344.155803-2-hdegoede@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 306 bytes --]
On Mon, Dec 27, 2021 at 04:33:41PM +0100, Hans de Goede wrote:
> On some boards where the firmware/fwnode information is in essence
> read-only (x86 + ACPI boards) the i2c_client for the codec may contain
> the wrong IRQ or no IRQ at all.
This doesn't apply against current code, please check and resend.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-12-31 13:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-27 15:33 [PATCH 1/5] ASoC: rt5640: Change jack_work to a delayed_work Hans de Goede
2021-12-27 15:33 ` [PATCH 2/5] ASoC: rt5640: Allow snd_soc_component_set_jack() to override the codec IRQ Hans de Goede
2021-12-31 13:22 ` Mark Brown [this message]
2022-01-05 12:22 ` Hans de Goede
2021-12-27 15:33 ` [PATCH 3/5] ASoC: rt5640: Add support for boards with an external jack-detect GPIO Hans de Goede
2021-12-27 15:33 ` [PATCH 4/5] ASoC: Intel: bytcr_rt5640: Support retrieving the codec IRQ from the AMCR0F28 ACPI dev Hans de Goede
2021-12-27 15:33 ` [PATCH 5/5] ASoC: Intel: bytcr_rt5640: Add support for external GPIO jack-detect Hans de Goede
2021-12-30 18:56 ` Stephan Gerhold
2021-12-30 19:12 ` Hans de Goede
2021-12-30 19:34 ` Stephan Gerhold
2022-01-06 20:28 ` [PATCH 1/5] ASoC: rt5640: Change jack_work to a delayed_work Mark Brown
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=Yc8EMRxc07NphgcR@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=cezary.rojewski@intel.com \
--cc=hdegoede@redhat.com \
--cc=lgirdwood@gmail.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=yang.jie@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 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.