From: Takashi Iwai <tiwai@suse.de>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: Takashi Iwai <tiwai@suse.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>, Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] sound updates for 4.21
Date: Mon, 31 Dec 2018 19:15:02 +0100 [thread overview]
Message-ID: <s5ho991k1g9.wl-tiwai@suse.de> (raw)
In-Reply-To: <acbc8f2d-c112-550d-1028-b4c234df4c1b@linux.intel.com>
On Mon, 31 Dec 2018 11:24:41 +0100,
Pierre-Louis Bossart wrote:
>
>
> On 12/31/18 2:11 AM, Takashi Iwai wrote:
> > On Mon, 31 Dec 2018 00:17:58 +0100,
> > Pierre-Louis Bossart wrote:
> >>> BTW, one thing I'd really like to avoid is to rearrange the probe
> >>> procedure of the legacy HDA driver (so that we can get codec_mask
> >>> during pci probe() call). The async probe is the result of the many
> >>> struggles with the various and complex configurations. Moving the
> >>> codec probe to the beginning isn't trivial and quite risky to break
> >>> something else.
> >> Agree, mucking with the probe isn't something we should look into,
> >> especially with this Skylake driver being eventually deprecated once
> >> SOF is at feature parity. This set of autodetection patches for 4.21
> >> was really targeting CFL/WHL+ devices, where the DSP usage is
> >> mandatory when directly-attached digital microphones are used. For
> >> Skylake and kabylake using the legacy by default is just fine.
> > OK, then how about applying the PCI class check only for such ones
> > like the patch below? The macro isn't sexy and can be replaced with
> > another way, but you have an idea.
>
> The two patches which added the PCI class checks were supposed to be a
> simple bullet-proof way of detecting the DSP presence and solving a
> problem of coexistence between two drivers. At this point if we start
> adding quirks and still have unclear issues with HDMI support which
> isn't different for CFL+, it may be wiser to revert them to let the
> 4.21 merge window progress? It's frustrating but I'd rather solve this
> problem the right way than with multiple iterations rushed because of
> the merge window timing.
Fair enough, let's revert them for now. I'm going to submit the
revert patch.
thanks,
Takashi
next prev parent reply other threads:[~2018-12-31 18:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 15:38 [GIT PULL] sound updates for 4.21 Takashi Iwai
2018-12-25 23:20 ` pr-tracker-bot
2018-12-27 3:31 ` Linus Torvalds
2018-12-28 12:43 ` Ingo Molnar
2018-12-28 17:07 ` Takashi Iwai
2018-12-28 19:04 ` Linus Torvalds
2018-12-30 9:21 ` Takashi Iwai
[not found] ` <82bb7f60-c3c2-4715-a0a0-f1f2a8b14c74@linux.intel.com>
2018-12-31 0:19 ` Linus Torvalds
2018-12-31 0:54 ` Pierre-Louis Bossart
2018-12-31 8:11 ` Takashi Iwai
2018-12-31 10:24 ` Pierre-Louis Bossart
2018-12-31 18:15 ` Takashi Iwai [this message]
2018-12-31 20:10 ` Pierre-Louis Bossart
2018-12-31 21:02 ` Hans de Goede
2018-12-31 13:43 ` Azat Khuzhin
2018-12-31 15:22 ` Pierre-Louis Bossart
2019-01-05 0:34 ` Azat Khuzhin
2019-01-05 2:12 ` Pierre-Louis Bossart
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=s5ho991k1g9.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=torvalds@linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox