From: Hans de Goede <hdegoede@redhat.com> To: Lee Jones <lee.jones@linaro.org>, Cezary Rojewski <cezary.rojewski@intel.com>, Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>, Liam Girdwood <liam.r.girdwood@linux.intel.com>, Jie Yang <yang.jie@linux.intel.com>, Mark Brown <broonie@kernel.org> Cc: Hans de Goede <hdegoede@redhat.com>, patches@opensource.cirrus.com, linux-kernel@vger.kernel.org, Andy Shevchenko <andy.shevchenko@gmail.com>, Charles Keepax <ckeepax@opensource.cirrus.com>, alsa-devel@alsa-project.org Subject: [PATCH v2 00/12] MFD/extcon/ASoC: Rework arizona codec jack-detect support Date: Sun, 17 Jan 2021 17:05:43 +0100 [thread overview] Message-ID: <20210117160555.78376-1-hdegoede@redhat.com> (raw) Hi All, This series reworks the arizona codec jack-detect support to use the snd_soc_jack helpers instead of direct extcon reporting. This is done by reworking the extcon driver into an arizona-jackdet library and then modifying the codec drivers to use that directly, replacing the old separate extcon child-devices and extcon-driver. This brings the arizona-codec jack-detect handling inline with how all other ASoC codec driver do this. This was developed and tested on a Lenovo Yoga Tablet 1051L with a WM5102 codec. The MFD, ASoC and extcon parts can be merged independent from each-other although that could lead to a case where both the extcon driver and the new arizona-jackdet library will try to do jack-detection. If we end up with a git tree in that state then one of the 2 will fail to load because the other will already have claimed the IRQs, so this is not a problem really. Or the entire series could be merged through the MFD tree if people prefer that. Note that this series also paves the way for some further cleanups, removing some jackdetect related variables like hp_ena and hp_clamp from the arizona data struct shared between all the MFD child devices. I've deliberately not done that cleanup as part of this patch-series, since IMHO the series is big enough as is. These cleanups can be done in a follow-up series once this series has landed. Regards, Hans
WARNING: multiple messages have this Message-ID (diff)
From: Hans de Goede <hdegoede@redhat.com> To: Lee Jones <lee.jones@linaro.org>, Cezary Rojewski <cezary.rojewski@intel.com>, Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>, Liam Girdwood <liam.r.girdwood@linux.intel.com>, Jie Yang <yang.jie@linux.intel.com>, Mark Brown <broonie@kernel.org> Cc: alsa-devel@alsa-project.org, Charles Keepax <ckeepax@opensource.cirrus.com>, patches@opensource.cirrus.com, linux-kernel@vger.kernel.org, Hans de Goede <hdegoede@redhat.com>, Andy Shevchenko <andy.shevchenko@gmail.com> Subject: [PATCH v2 00/12] MFD/extcon/ASoC: Rework arizona codec jack-detect support Date: Sun, 17 Jan 2021 17:05:43 +0100 [thread overview] Message-ID: <20210117160555.78376-1-hdegoede@redhat.com> (raw) Hi All, This series reworks the arizona codec jack-detect support to use the snd_soc_jack helpers instead of direct extcon reporting. This is done by reworking the extcon driver into an arizona-jackdet library and then modifying the codec drivers to use that directly, replacing the old separate extcon child-devices and extcon-driver. This brings the arizona-codec jack-detect handling inline with how all other ASoC codec driver do this. This was developed and tested on a Lenovo Yoga Tablet 1051L with a WM5102 codec. The MFD, ASoC and extcon parts can be merged independent from each-other although that could lead to a case where both the extcon driver and the new arizona-jackdet library will try to do jack-detection. If we end up with a git tree in that state then one of the 2 will fail to load because the other will already have claimed the IRQs, so this is not a problem really. Or the entire series could be merged through the MFD tree if people prefer that. Note that this series also paves the way for some further cleanups, removing some jackdetect related variables like hp_ena and hp_clamp from the arizona data struct shared between all the MFD child devices. I've deliberately not done that cleanup as part of this patch-series, since IMHO the series is big enough as is. These cleanups can be done in a follow-up series once this series has landed. Regards, Hans
next reply other threads:[~2021-01-17 16:07 UTC|newest] Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-17 16:05 Hans de Goede [this message] 2021-01-17 16:05 ` [PATCH v2 00/12] MFD/extcon/ASoC: Rework arizona codec jack-detect support Hans de Goede 2021-01-17 16:05 ` [PATCH v2 01/12] mfd: arizona: Drop arizona-extcon cells Hans de Goede 2021-01-17 16:05 ` Hans de Goede 2021-01-17 16:05 ` [PATCH v2 02/12] ASoC: arizona-jack: Add arizona-jack.c Hans de Goede 2021-01-17 16:05 ` Hans de Goede 2021-01-18 11:57 ` Andy Shevchenko 2021-01-18 11:57 ` Andy Shevchenko 2021-01-17 16:05 ` [PATCH v2 03/12] ASoC: arizona-jack: Fix some issues when HPDET IRQ fires after the jack has been unplugged Hans de Goede 2021-01-17 16:05 ` Hans de Goede 2021-01-18 12:47 ` Mark Brown 2021-01-18 12:47 ` Mark Brown 2021-01-21 15:58 ` Hans de Goede 2021-01-21 15:58 ` Hans de Goede 2021-01-22 11:07 ` Charles Keepax 2021-01-22 11:07 ` Charles Keepax 2021-01-17 16:05 ` [PATCH v2 04/12] ASoC: arizona-jack: Fix various races on driver unbind Hans de Goede 2021-01-17 16:05 ` Hans de Goede 2021-01-17 16:05 ` [PATCH v2 05/12] ASoC: arizona-jack: Fix flags parameter to the gpiod_get("wlf,micd-pol") call Hans de Goede 2021-01-17 16:05 ` [PATCH v2 05/12] ASoC: arizona-jack: Fix flags parameter to the gpiod_get("wlf, micd-pol") call Hans de Goede 2021-01-17 16:05 ` [PATCH v2 06/12] ASoC: arizona-jack: Move jack-detect variables to struct arizona_priv Hans de Goede 2021-01-17 16:05 ` Hans de Goede 2021-01-18 12:01 ` Andy Shevchenko 2021-01-18 12:01 ` Andy Shevchenko 2021-01-22 11:12 ` Charles Keepax 2021-01-22 11:12 ` Charles Keepax 2021-01-17 16:05 ` [PATCH v2 07/12] ASoC: arizona-jack: Use arizona->dev for runtime-pm Hans de Goede 2021-01-17 16:05 ` Hans de Goede 2021-01-18 12:02 ` Andy Shevchenko 2021-01-18 12:02 ` Andy Shevchenko 2021-01-22 0:03 ` Hans de Goede 2021-01-22 0:03 ` Hans de Goede 2021-01-22 9:38 ` Andy Shevchenko 2021-01-22 9:38 ` Andy Shevchenko 2021-01-22 13:56 ` Hans de Goede 2021-01-22 13:56 ` Hans de Goede 2021-01-17 16:05 ` [PATCH v2 08/12] ASoC: arizona-jack: convert into a helper library for codec drivers Hans de Goede 2021-01-17 16:05 ` Hans de Goede 2021-01-18 17:24 ` Andy Shevchenko 2021-01-18 17:24 ` Andy Shevchenko 2021-01-19 9:51 ` Richard Fitzgerald 2021-01-19 9:51 ` Richard Fitzgerald 2021-01-21 16:55 ` Hans de Goede 2021-01-21 16:55 ` Hans de Goede 2021-01-22 11:26 ` Charles Keepax 2021-01-22 11:26 ` Charles Keepax 2021-01-22 12:23 ` Hans de Goede 2021-01-22 12:23 ` Hans de Goede 2021-01-22 13:04 ` Charles Keepax 2021-01-22 13:04 ` Charles Keepax 2021-01-22 13:36 ` Hans de Goede 2021-01-22 13:36 ` Hans de Goede 2021-01-22 13:21 ` Charles Keepax 2021-01-22 13:21 ` Charles Keepax 2021-01-17 16:05 ` [PATCH v2 09/12] ASoC: arizona-jack: Use snd_soc_jack to report jack events Hans de Goede 2021-01-17 16:05 ` Hans de Goede 2021-01-17 16:05 ` [PATCH v2 10/12] ASoC: arizona: Make the wm5102, wm5110, wm8997 and wm8998 drivers use the new jack library Hans de Goede 2021-01-17 16:05 ` Hans de Goede 2021-01-17 16:05 ` [PATCH v2 11/12] ASoC: Intel: bytcr_wm5102: Add jack detect support Hans de Goede 2021-01-17 16:05 ` Hans de Goede 2021-01-17 16:05 ` [PATCH v2 12/12] extcon: arizona: Drop the arizona extcon driver Hans de Goede 2021-01-17 16:05 ` Hans de Goede 2021-01-18 12:13 ` Andy Shevchenko 2021-01-18 12:13 ` Andy Shevchenko 2021-01-18 9:55 ` [PATCH v2 00/12] MFD/extcon/ASoC: Rework arizona codec jack-detect support Lee Jones 2021-01-18 9:55 ` Lee Jones 2021-01-18 10:28 ` Hans de Goede 2021-01-18 10:28 ` Hans de Goede 2021-01-18 10:47 ` Lee Jones 2021-01-18 10:47 ` Lee Jones
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=20210117160555.78376-1-hdegoede@redhat.com \ --to=hdegoede@redhat.com \ --cc=alsa-devel@alsa-project.org \ --cc=andy.shevchenko@gmail.com \ --cc=broonie@kernel.org \ --cc=cezary.rojewski@intel.com \ --cc=ckeepax@opensource.cirrus.com \ --cc=lee.jones@linaro.org \ --cc=liam.r.girdwood@linux.intel.com \ --cc=linux-kernel@vger.kernel.org \ --cc=patches@opensource.cirrus.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: linkBe 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.