From: Vinod Koul <vkoul@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: alsa-devel@alsa-project.org,
Kai Vehmanen <kai.vehmanen@linux.intel.com>,
tiwai@suse.de, gregkh@linuxfoundation.org,
Rander Wang <rander.wang@intel.com>,
broonie@kernel.org, Bard liao <yung-chuan.liao@linux.intel.com>,
Bard Liao <bard.liao@intel.com>
Subject: Re: [PATCH 1/2] soundwire: dmi-quirks: add quirk for Intel 'Bishop County' NUC M15
Date: Fri, 23 Jul 2021 11:36:15 +0530 [thread overview]
Message-ID: <YPpcV/dnEbWGtMFv@matsya> (raw)
In-Reply-To: <c86efd0f-b941-f3ff-885d-f1d0d7d46d30@linux.intel.com>
On 22-07-21, 09:25, Pierre-Louis Bossart wrote:
>
>
> On 7/22/21 9:02 AM, Vinod Koul wrote:
> > On 19-07-21, 18:32, Pierre-Louis Bossart wrote:
> >> The same quirk is used for LAPBC510 and LAPBC710 skews who use the
> >> same audio design.
> >>
> >> These devices have the same BIOS issues inherited from the Intel
> >> reference, add the same _ADR remap previously used on HP devices.
> >
> > This fails to apply on rc1, pls rebase or if there are any dependencies,
> > do spell them out
>
> it likely depends on
>
> [PATCH] soundwire: dmi-quirks: add ull suffix for SoundWire _ADR values
As I said above, if there is a dependency, pls spell it out!
> which was sent by Bard when the merge window opened.
--
~Vinod
next prev parent reply other threads:[~2021-07-23 6:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 23:32 [PATCH 0/2] ASoC/soundwire: add quirks for Intel 'Bishop County' NUC M15 Pierre-Louis Bossart
2021-07-19 23:32 ` [PATCH 1/2] soundwire: dmi-quirks: add quirk " Pierre-Louis Bossart
2021-07-22 14:02 ` Vinod Koul
2021-07-22 14:25 ` Pierre-Louis Bossart
2021-07-22 14:29 ` Pierre-Louis Bossart
2021-07-23 6:07 ` Vinod Koul
2021-07-23 6:06 ` Vinod Koul [this message]
2021-07-19 23:32 ` [PATCH 2/2] ASOC: Intel: sof_sdw: " Pierre-Louis Bossart
2021-07-20 18:48 ` (subset) [PATCH 0/2] ASoC/soundwire: add quirks " Mark Brown
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=YPpcV/dnEbWGtMFv@matsya \
--to=vkoul@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rander.wang@intel.com \
--cc=tiwai@suse.de \
--cc=yung-chuan.liao@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: 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.