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 v3 0/5] MFD/ASoC: Add support for Intel Bay Trail boards with WM5102 codec Date: Sun, 17 Jan 2021 22:22:47 +0100 [thread overview] Message-ID: <20210117212252.206115-1-hdegoede@redhat.com> (raw) Hi All, Here is v3 of my series to add support for Intel Bay Trail based devices which use a WM5102 codec for audio output/input. New in v3 is that the compile error when CONFIG_ACPI is unset should be gone. Everything else is the same as in v2, see the cover-letter of v2 below: This was developed and tested on a Lenovo Yoga Tablet 1051L. The biggest difference from v1 is that, based on all the discussions about the jack-detect stuff, I've decided to split this into 2 series. One series adding the basic support for this setup, which is this series. And a second series which reworks the extcon driver into an arizona-jackdet library and then modifies the codec drivers to use that directly, replacing the old separate extcon child-device and extcon-driver. The are 2 reasons for the split: 1. With the new jack-det rework, the series really address 2 separate (but related) enhancements. 2. I expect this series to be ready for merging, while the jack-det stuff likely will need a couple more revisions. Other then the split there are some minor changes addressing various review comments, see the individual patch changelogs. The MFD and ASoC parts can be merged independent from each-other (both must be merged to get working sound on these boards, but that is only a runtime dependency and a part missing won't have any bad side-effects). Or the entire series could be merged through the MFD tree if people prefer that. 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 v3 0/5] MFD/ASoC: Add support for Intel Bay Trail boards with WM5102 codec Date: Sun, 17 Jan 2021 22:22:47 +0100 [thread overview] Message-ID: <20210117212252.206115-1-hdegoede@redhat.com> (raw) Hi All, Here is v3 of my series to add support for Intel Bay Trail based devices which use a WM5102 codec for audio output/input. New in v3 is that the compile error when CONFIG_ACPI is unset should be gone. Everything else is the same as in v2, see the cover-letter of v2 below: This was developed and tested on a Lenovo Yoga Tablet 1051L. The biggest difference from v1 is that, based on all the discussions about the jack-detect stuff, I've decided to split this into 2 series. One series adding the basic support for this setup, which is this series. And a second series which reworks the extcon driver into an arizona-jackdet library and then modifies the codec drivers to use that directly, replacing the old separate extcon child-device and extcon-driver. The are 2 reasons for the split: 1. With the new jack-det rework, the series really address 2 separate (but related) enhancements. 2. I expect this series to be ready for merging, while the jack-det stuff likely will need a couple more revisions. Other then the split there are some minor changes addressing various review comments, see the individual patch changelogs. The MFD and ASoC parts can be merged independent from each-other (both must be merged to get working sound on these boards, but that is only a runtime dependency and a part missing won't have any bad side-effects). Or the entire series could be merged through the MFD tree if people prefer that. Regards, Hans
next reply other threads:[~2021-01-17 21:24 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-17 21:22 Hans de Goede [this message] 2021-01-17 21:22 ` [PATCH v3 0/5] MFD/ASoC: Add support for Intel Bay Trail boards with WM5102 codec Hans de Goede 2021-01-17 21:22 ` [PATCH v3 1/5] mfd: arizona: Add MODULE_SOFTDEP("pre: arizona_ldo1") Hans de Goede 2021-01-17 21:22 ` Hans de Goede 2021-01-17 21:22 ` [PATCH v3 2/5] mfd: arizona: Replace arizona_of_get_type() with device_get_match_data() Hans de Goede 2021-01-17 21:22 ` Hans de Goede 2021-01-18 11:51 ` Andy Shevchenko 2021-01-18 11:51 ` Andy Shevchenko 2021-01-20 10:02 ` Charles Keepax 2021-01-20 10:02 ` Charles Keepax 2021-01-17 21:22 ` [PATCH v3 3/5] mfd: arizona: Add support for ACPI enumeration of WM5102 connected over SPI Hans de Goede 2021-01-17 21:22 ` Hans de Goede 2021-01-18 13:02 ` Mark Brown 2021-01-18 13:02 ` Mark Brown 2021-01-18 13:13 ` Hans de Goede 2021-01-18 13:13 ` Hans de Goede 2021-01-18 13:34 ` Mark Brown 2021-01-18 13:34 ` Mark Brown 2021-01-18 13:38 ` Hans de Goede 2021-01-18 13:38 ` Hans de Goede 2021-01-20 19:18 ` Hans de Goede 2021-01-20 19:18 ` Hans de Goede 2021-01-20 19:59 ` Andy Shevchenko 2021-01-20 19:59 ` Andy Shevchenko 2021-01-20 21:38 ` Hans de Goede 2021-01-20 21:38 ` Hans de Goede 2021-01-17 21:22 ` [PATCH v3 4/5] ASoC: Intel: Add DMI quirk table to soc_intel_is_byt_cr() Hans de Goede 2021-01-17 21:22 ` Hans de Goede 2021-01-17 21:22 ` [PATCH v3 5/5] ASoC: Intel: bytcr_wm5102: Add machine driver for BYT/WM5102 Hans de Goede 2021-01-17 21:22 ` 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=20210117212252.206115-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.