From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>,
Cezary Rojewski <cezary.rojewski@intel.com>
Cc: alsa-devel@alsa-project.org, tiwai@suse.com, lgirdwood@gmail.com
Subject: Re: [RESEND PATCH v2 0/7] ASoC: Intel: Skylake: Driver fundaments overhaul
Date: Tue, 23 Jul 2019 13:07:31 -0500 [thread overview]
Message-ID: <cac0d84e-61d3-5379-cbce-10f8d637310d@linux.intel.com> (raw)
In-Reply-To: <20190723154449.GJ5365@sirena.org.uk>
On 7/23/19 10:44 AM, Mark Brown wrote:
> On Tue, Jul 23, 2019 at 04:58:47PM +0200, Cezary Rojewski wrote:
>> Skylake driver is divided into two modules:
>> - snd_soc_skl
>> - snd_soc_skl_ipc
>
> Pierre?
Sorry I was traveling and while I saw this series I never found the time
to review it.
I have really mixed feelings here and would like to make sure we are all
aligned on how we deal with the Skylake driver.
On one side I see that Cezary's team has done a genuine effort to
clean-up the code, show their technical skills, provide and listen to
review feedback, and improve the quality of upstream code. It wouldn't
be fair to shoot down well-intended developers who are making an honest
effort after years of embarrassing contributions. Intel and the Linux
community also have a shared interest in making sure newer kernel
versions improve quality and conversely that existing solutions can be
upgraded to improve security while also improving audio.
On the other hand, I still see an opaque design (no obvious
core/platform split, mind-boggling use of topology with closed tools,
IPC that I still don't get), limited information on testing. I don't
think anyone challenges the fact that this driver is what it is, and not
the foundation for future upstream work. And there are about 100
additional clean-up/updates patches to be submitted for this driver,
which I don't personally have the time to look into since I am already
fully-booked on SoundWire work.
Overall my recommendations would be to:
- give Cezary's team the benefit of the doubt for their Skylake reworks,
and add him as mandatory reviewer for the skylake parts. That doesn't
mean merging blindly but recognizing that no one else at Intel has a
better understanding of this code.
- add CI support w/ Skylake devices so that we can have a better feel
for compilation/testing support. we've talked about having upstream
automatic build/hardware tests, maybe now is the time to do something
about it.
- draw the line at "no new features" after e.g. 5.5 and "no new
platforms when SOF provides a solution". SOF was expected to reach
feature parity by the end of 2019 so it's not a random date I just made up.
- I am even tempted to recommend de-featuring HDaudio codec support in
the Skylake driver since we already know of a broken probe that was
found on Linus' laptop and a slew of changes applied to SOF/legacy that
are missing in this driver.
Comments and feedback welcome.
-Pierre
next prev parent reply other threads:[~2019-07-23 18:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 14:58 [RESEND PATCH v2 0/7] ASoC: Intel: Skylake: Driver fundaments overhaul Cezary Rojewski
2019-07-23 14:58 ` [RESEND PATCH v2 1/7] ASoC: Intel: Skylake: Merge skl_sst and skl into skl_dev struct Cezary Rojewski
2019-07-24 19:17 ` Applied "ASoC: Intel: Skylake: Merge skl_sst and skl into skl_dev struct" to the asoc tree Mark Brown
2019-07-23 14:58 ` [RESEND PATCH v2 2/7] ASoC: Intel: Skylake: Combine snd_soc_skl_ipc and snd_soc_skl Cezary Rojewski
2019-07-23 14:58 ` [RESEND PATCH v2 3/7] ASoC: Intel: Skylake: Remove MCPS available check Cezary Rojewski
2019-07-24 19:17 ` Applied "ASoC: Intel: Skylake: Remove MCPS available check" to the asoc tree Mark Brown
2019-07-23 14:58 ` [RESEND PATCH v2 4/7] ASoC: Intel: Skylake: Remove memory available check Cezary Rojewski
2019-07-24 19:17 ` Applied "ASoC: Intel: Skylake: Remove memory available check" to the asoc tree Mark Brown
2019-07-23 14:58 ` [RESEND PATCH v2 5/7] ASoC: Intel: Skylake: Do not disable FW notifications Cezary Rojewski
2019-07-23 14:58 ` [RESEND PATCH v2 6/7] ASoC: Intel: Skylake: Make MCPS and CPS params obsolete Cezary Rojewski
2019-07-24 19:17 ` Applied "ASoC: Intel: Skylake: Make MCPS and CPS params obsolete" to the asoc tree Mark Brown
2019-07-23 14:58 ` [RESEND PATCH v2 7/7] ASoC: Intel: Skylake: Cleanup skl_module_cfg declaration Cezary Rojewski
2019-07-24 19:17 ` Applied "ASoC: Intel: Skylake: Cleanup skl_module_cfg declaration" to the asoc tree Mark Brown
2019-07-23 15:44 ` [RESEND PATCH v2 0/7] ASoC: Intel: Skylake: Driver fundaments overhaul Mark Brown
2019-07-23 18:07 ` Pierre-Louis Bossart [this message]
2019-07-24 16:50 ` Mark Brown
2019-07-24 17:14 ` Cezary Rojewski
2019-07-24 18:10 ` Mark Brown
2019-07-24 12:39 ` Vinod Koul
2019-07-24 12:42 ` Vinod Koul
2019-07-26 11:31 ` Cezary Rojewski
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=cac0d84e-61d3-5379-cbce-10f8d637310d@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=lgirdwood@gmail.com \
--cc=tiwai@suse.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.