From: Bard Liao <yung-chuan.liao@linux.intel.com>
To: alsa-devel@alsa-project.org, vkoul@kernel.org
Cc: vinod.koul@linaro.org, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org, srinivas.kandagatla@linaro.org,
rander.wang@linux.intel.com, hui.wang@canonical.com,
pierre-louis.bossart@linux.intel.com, sanyog.r.kale@intel.com,
bard.liao@intel.com
Subject: [PATCH v2 0/3] soundwire: add DMI quirks for overridind addr
Date: Tue, 2 Mar 2021 15:51:02 +0800 [thread overview]
Message-ID: <20210302075105.11515-1-yung-chuan.liao@linux.intel.com> (raw)
Platform firmware may have incorrect _ADR values causing the driver
probes to fail. Adding the override_ops allows people to override the
addr values.
v2:
- Add the override_adr ops
- Move DMI quirks to a new file
Pierre-Louis Bossart (2):
soundwire: Intel: introduce DMI quirks for HP Spectre x360 Convertible
soundwire: Intel: add DMI quirk for Dell SKU 0A3E
Vinod Koul (1):
soundwire: add override addr ops
drivers/soundwire/Makefile | 2 +-
drivers/soundwire/bus.h | 2 +
drivers/soundwire/dmi-quirks.c | 96 ++++++++++++++++++++++++++++++++++
drivers/soundwire/intel.c | 1 +
drivers/soundwire/slave.c | 8 ++-
include/linux/soundwire/sdw.h | 4 +-
6 files changed, 110 insertions(+), 3 deletions(-)
create mode 100644 drivers/soundwire/dmi-quirks.c
--
2.17.1
next reply other threads:[~2021-03-02 8:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 7:51 Bard Liao [this message]
2021-03-02 7:51 ` [PATCH v2 1/3] soundwire: add override addr ops Bard Liao
2021-03-02 7:51 ` [PATCH v2 2/3] soundwire: Intel: introduce DMI quirks for HP Spectre x360 Convertible Bard Liao
2021-04-12 21:37 ` Dave Hansen
2021-04-14 4:08 ` Vinod Koul
2021-04-14 15:21 ` Pierre-Louis Bossart
2021-03-02 7:51 ` [PATCH v2 3/3] soundwire: Intel: add DMI quirk for Dell SKU 0A3E Bard Liao
2021-03-22 12:03 ` [PATCH v2 0/3] soundwire: add DMI quirks for overridind addr Vinod Koul
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=20210302075105.11515-1-yung-chuan.liao@linux.intel.com \
--to=yung-chuan.liao@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hui.wang@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rander.wang@linux.intel.com \
--cc=sanyog.r.kale@intel.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=vinod.koul@linaro.org \
--cc=vkoul@kernel.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
all inboxes | Powered by JetHome®