From: Hans de Goede <hdegoede@redhat.com> To: Mark Brown <broonie@kernel.org> Cc: Charles Keepax <ckeepax@opensource.cirrus.com>, Lee Jones <lee.jones@linaro.org>, MyungJoo Ham <myungjoo.ham@samsung.com>, Chanwoo Choi <cw00.choi@samsung.com>, 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>, patches@opensource.cirrus.com, linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org Subject: Re: [PATCH 01/14] mfd: arizona: Add jack pointer to struct arizona Date: Fri, 1 Jan 2021 14:24:34 +0100 [thread overview] Message-ID: <fca91ed2-408b-bb31-f6e8-4391f06b0ccc@redhat.com> (raw) In-Reply-To: <20201230133803.GC4428@sirena.org.uk> Hi, On 12/30/20 2:38 PM, Mark Brown wrote: > On Tue, Dec 29, 2020 at 04:33:09PM +0100, Hans de Goede wrote: >> On 12/29/20 4:08 PM, Mark Brown wrote: <snip> >>> The whole purpose of creating sound/core/jack.c is to abstract away the >>> userspace interfaces from the drivers, most audio devices shouldn't be >>> working with extcon directly just as they shouldn't be creating input >>> devices or ALSA controls directly. The missing bit there is to add >>> extcon into jack.c. > >> So what you are suggesting is making sound/core/jack.c register the >> extcon device and then have arizona-extcon.c talk to sound/core/jack.c >> and no longer do any extcon stuff itself. > > Yes. Ok, so this seems to be the same solution as which the opensource.cirrus.com folks want in that both you and the opensource.cirrus.com people want to change the arizona-extcon.c driver to be changed to stop reporting extcon info directly itself and instead do all the reporting through sound/core/jack.c. Where the thoughts on this seem to differ is that the opensource.cirrus.com folks seem to be fine with dropping extcon support, where as you suggest to extend sound/core/jack.c to register an extcon device and have it report extcon events. I'm with the opensource.cirrus.com folks here that ATM it seems best to just drop extcon support since the only user is Android, which also supports the input_dev API. If the need arises we can always add extcon-support to sound/core/jack.c later. So I'll start on reworking this patch-series to change the arizona-extcon.c driver to stop it reporting extcon info directly itself and instead do all the reporting through sound/core/jack.c. Regards, Hans
WARNING: multiple messages have this Message-ID (diff)
From: Hans de Goede <hdegoede@redhat.com> To: Mark Brown <broonie@kernel.org> Cc: Cezary Rojewski <cezary.rojewski@intel.com>, Charles Keepax <ckeepax@opensource.cirrus.com>, alsa-devel@alsa-project.org, patches@opensource.cirrus.com, Jie Yang <yang.jie@linux.intel.com>, Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>, linux-kernel@vger.kernel.org, Liam Girdwood <liam.r.girdwood@linux.intel.com>, Chanwoo Choi <cw00.choi@samsung.com>, MyungJoo Ham <myungjoo.ham@samsung.com>, Lee Jones <lee.jones@linaro.org> Subject: Re: [PATCH 01/14] mfd: arizona: Add jack pointer to struct arizona Date: Fri, 1 Jan 2021 14:24:34 +0100 [thread overview] Message-ID: <fca91ed2-408b-bb31-f6e8-4391f06b0ccc@redhat.com> (raw) In-Reply-To: <20201230133803.GC4428@sirena.org.uk> Hi, On 12/30/20 2:38 PM, Mark Brown wrote: > On Tue, Dec 29, 2020 at 04:33:09PM +0100, Hans de Goede wrote: >> On 12/29/20 4:08 PM, Mark Brown wrote: <snip> >>> The whole purpose of creating sound/core/jack.c is to abstract away the >>> userspace interfaces from the drivers, most audio devices shouldn't be >>> working with extcon directly just as they shouldn't be creating input >>> devices or ALSA controls directly. The missing bit there is to add >>> extcon into jack.c. > >> So what you are suggesting is making sound/core/jack.c register the >> extcon device and then have arizona-extcon.c talk to sound/core/jack.c >> and no longer do any extcon stuff itself. > > Yes. Ok, so this seems to be the same solution as which the opensource.cirrus.com folks want in that both you and the opensource.cirrus.com people want to change the arizona-extcon.c driver to be changed to stop reporting extcon info directly itself and instead do all the reporting through sound/core/jack.c. Where the thoughts on this seem to differ is that the opensource.cirrus.com folks seem to be fine with dropping extcon support, where as you suggest to extend sound/core/jack.c to register an extcon device and have it report extcon events. I'm with the opensource.cirrus.com folks here that ATM it seems best to just drop extcon support since the only user is Android, which also supports the input_dev API. If the need arises we can always add extcon-support to sound/core/jack.c later. So I'll start on reworking this patch-series to change the arizona-extcon.c driver to stop it reporting extcon info directly itself and instead do all the reporting through sound/core/jack.c. Regards, Hans
next prev parent reply other threads:[~2021-01-01 13:26 UTC|newest] Thread overview: 106+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-27 21:12 [PATCH 00/14] MFD/extcon/ASoC: Add support for Intel Bay Trail boards with WM5102 codec Hans de Goede 2020-12-27 21:12 ` Hans de Goede 2020-12-27 21:12 ` [PATCH 01/14] mfd: arizona: Add jack pointer to struct arizona Hans de Goede 2020-12-27 21:12 ` Hans de Goede 2020-12-28 12:21 ` Mark Brown 2020-12-28 12:21 ` Mark Brown 2020-12-28 13:16 ` Hans de Goede 2020-12-28 13:16 ` Hans de Goede 2020-12-28 16:28 ` Mark Brown 2020-12-28 16:28 ` Mark Brown 2020-12-29 13:06 ` Charles Keepax 2020-12-29 13:06 ` Charles Keepax 2020-12-29 13:57 ` Hans de Goede 2020-12-29 13:57 ` Hans de Goede 2020-12-29 15:06 ` Charles Keepax 2020-12-29 15:06 ` Charles Keepax 2020-12-29 15:15 ` Mark Brown 2020-12-29 15:15 ` Mark Brown 2020-12-29 15:40 ` Hans de Goede 2020-12-29 15:40 ` Hans de Goede 2020-12-29 16:51 ` Richard Fitzgerald 2020-12-29 16:51 ` Richard Fitzgerald 2020-12-30 11:04 ` Hans de Goede 2020-12-30 11:04 ` Hans de Goede 2020-12-30 11:23 ` Richard Fitzgerald 2020-12-30 11:23 ` Richard Fitzgerald 2020-12-30 12:01 ` Hans de Goede 2020-12-30 12:01 ` Hans de Goede 2020-12-30 13:16 ` Mark Brown 2020-12-30 13:16 ` Mark Brown 2020-12-29 16:43 ` Richard Fitzgerald 2020-12-29 16:43 ` Richard Fitzgerald 2020-12-29 15:08 ` Mark Brown 2020-12-29 15:08 ` Mark Brown 2020-12-29 15:33 ` Hans de Goede 2020-12-29 15:33 ` Hans de Goede 2020-12-30 13:38 ` Mark Brown 2020-12-30 13:38 ` Mark Brown 2021-01-01 13:24 ` Hans de Goede [this message] 2021-01-01 13:24 ` Hans de Goede 2020-12-27 21:12 ` [PATCH 02/14] mfd: arizona: Add MODULE_SOFTDEP("pre: arizona_ldo1") Hans de Goede 2020-12-27 21:12 ` Hans de Goede 2020-12-29 11:40 ` Charles Keepax 2020-12-29 11:40 ` Charles Keepax 2020-12-27 21:12 ` [PATCH 03/14] mfd: arizona: Add support for ACPI enumeration of WM5102 connected over SPI Hans de Goede 2020-12-27 21:12 ` Hans de Goede 2020-12-28 1:21 ` kernel test robot 2020-12-28 1:21 ` kernel test robot 2020-12-28 1:21 ` [RFC PATCH] mfd: arizona: ldoena_gpios can be static kernel test robot 2020-12-28 1:21 ` kernel test robot 2020-12-28 14:14 ` [PATCH 03/14] mfd: arizona: Add support for ACPI enumeration of WM5102 connected over SPI Andy Shevchenko 2020-12-28 14:14 ` Andy Shevchenko 2021-01-16 14:46 ` Hans de Goede 2021-01-16 14:46 ` Hans de Goede 2020-12-28 22:11 ` kernel test robot 2020-12-28 22:11 ` kernel test robot 2020-12-28 22:29 ` kernel test robot 2020-12-28 22:29 ` kernel test robot 2020-12-27 21:12 ` [PATCH 04/14] mfd: arizona: Allow building arizona MFD-core as module Hans de Goede 2020-12-27 21:12 ` Hans de Goede 2020-12-29 12:00 ` Charles Keepax 2020-12-29 12:00 ` Charles Keepax 2021-01-11 19:12 ` Hans de Goede 2021-01-11 19:12 ` Hans de Goede 2020-12-27 21:12 ` [PATCH 05/14] extcon: arizona: Fix some issues when HPDET IRQ fires after the jack has been unplugged Hans de Goede 2020-12-27 21:12 ` Hans de Goede 2020-12-27 21:12 ` [PATCH 06/14] extcon: arizona: Fix various races on driver unbind Hans de Goede 2020-12-27 21:12 ` Hans de Goede 2020-12-29 12:10 ` Charles Keepax 2020-12-29 12:10 ` Charles Keepax 2020-12-27 21:12 ` [PATCH 07/14] extcon: arizona: Fix modalias Hans de Goede 2020-12-27 21:12 ` Hans de Goede 2020-12-29 12:10 ` Charles Keepax 2020-12-29 12:10 ` Charles Keepax 2020-12-27 21:12 ` [PATCH 08/14] extcon: arizona: Fix flags parameter to the gpiod_get("wlf,micd-pol") call Hans de Goede 2020-12-27 21:12 ` [PATCH 08/14] extcon: arizona: Fix flags parameter to the gpiod_get("wlf, micd-pol") call Hans de Goede 2020-12-29 12:12 ` [PATCH 08/14] extcon: arizona: Fix flags parameter to the gpiod_get("wlf,micd-pol") call Charles Keepax 2020-12-29 12:12 ` Charles Keepax 2020-12-27 21:12 ` [PATCH 09/14] extcon: arizona: Add arizona_set_extcon_state() helper Hans de Goede 2020-12-27 21:12 ` Hans de Goede 2020-12-29 12:57 ` Charles Keepax 2020-12-29 12:57 ` Charles Keepax 2020-12-27 21:12 ` [PATCH 10/14] extcon: arizona: Also report jack state through snd_soc_jack_report() Hans de Goede 2020-12-27 21:12 ` Hans de Goede 2020-12-28 14:16 ` Andy Shevchenko 2020-12-28 14:16 ` Andy Shevchenko 2020-12-27 21:12 ` [PATCH 11/14] extcon: arizona: Use ASoC jack input-device when available Hans de Goede 2020-12-27 21:12 ` Hans de Goede 2020-12-27 21:12 ` [PATCH 12/14] ASoC: Intel: Add DMI quirk table to soc_intel_is_byt_cr() Hans de Goede 2020-12-27 21:12 ` Hans de Goede 2021-01-11 17:52 ` Pierre-Louis Bossart 2021-01-11 17:52 ` Pierre-Louis Bossart 2020-12-27 21:12 ` [PATCH 13/14] ASoC: Intel: bytcr_wm5102: Add machine driver for BYT/WM5102 Hans de Goede 2020-12-27 21:12 ` Hans de Goede 2020-12-29 13:58 ` Charles Keepax 2020-12-29 13:58 ` Charles Keepax 2021-01-11 17:54 ` Pierre-Louis Bossart 2021-01-11 17:54 ` Pierre-Louis Bossart 2021-01-16 16:49 ` Hans de Goede 2021-01-16 16:49 ` Hans de Goede 2020-12-27 21:12 ` [PATCH 14/14] ASoC: Intel: bytcr_wm5102: Add jack detect support Hans de Goede 2020-12-27 21:12 ` Hans de Goede 2020-12-28 14:19 ` [PATCH 00/14] MFD/extcon/ASoC: Add support for Intel Bay Trail boards with WM5102 codec Andy Shevchenko 2020-12-28 14:19 ` Andy Shevchenko 2021-01-11 18:54 ` Hans de Goede 2021-01-11 18:54 ` Hans de Goede
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=fca91ed2-408b-bb31-f6e8-4391f06b0ccc@redhat.com \ --to=hdegoede@redhat.com \ --cc=alsa-devel@alsa-project.org \ --cc=broonie@kernel.org \ --cc=cezary.rojewski@intel.com \ --cc=ckeepax@opensource.cirrus.com \ --cc=cw00.choi@samsung.com \ --cc=lee.jones@linaro.org \ --cc=liam.r.girdwood@linux.intel.com \ --cc=linux-kernel@vger.kernel.org \ --cc=myungjoo.ham@samsung.com \ --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.