Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: [alsa-devel] [PATCH] ASoC: SOF: Intel: add PCI ID for CometLake-S
Date: Wed, 18 Dec 2019 20:07:54 +0000	[thread overview]
Message-ID: <20191218200754.GA21386@sirena.org.uk> (raw)
In-Reply-To: <s5hd0clz9k9.wl-tiwai@suse.de>


[-- Attachment #1.1: Type: text/plain, Size: 341 bytes --]

On Wed, Dec 18, 2019 at 09:02:30PM +0100, Takashi Iwai wrote:

> When looking at the current code, for example, I'm not sure which
> category hits the case of Cometlake-S vs Cometlake-H vs
> Cometlake-LP...

Yeah, it's a bit much at the minute - there's enormous resolution there
with the Intel systems and I'm not 100% sure who's using it.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

      reply	other threads:[~2019-12-18 20:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-26 14:14 [alsa-devel] [PATCH] ASoC: SOF: Intel: add PCI ID for CometLake-S Pierre-Louis Bossart
2019-11-26 14:23 ` Takashi Iwai
2019-12-18  0:50   ` Pierre-Louis Bossart
2019-12-18  6:32     ` Takashi Iwai
2019-12-18 15:21       ` Pierre-Louis Bossart
2019-12-18 16:28         ` Takashi Iwai
2019-12-18 16:42           ` Pierre-Louis Bossart
2019-12-18 18:45             ` Takashi Iwai
2019-12-18 19:01               ` Pierre-Louis Bossart
2019-12-18 20:02                 ` Takashi Iwai
2019-12-18 20:07                   ` Mark Brown [this message]

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=20191218200754.GA21386@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=tiwai@suse.de \
    /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