public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: <broonie@kernel.org>
Cc: <alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>,
	<patches@opensource.cirrus.com>,
	Richard Fitzgerald <rf@opensource.cirrus.com>
Subject: [PATCH v2 0/2] ASoC: cs35l56: Update ACPI HID and property
Date: Thu, 17 Aug 2023 12:27:10 +0100	[thread overview]
Message-ID: <20230817112712.16637-1-rf@opensource.cirrus.com> (raw)

These two patches add an ACPI HID and update the way the platform-
specific firmware identifier is extracted from the ACPI.

CHANGES SINCE V1:
- Rebased to apply on v6.4 and v6.5.
- Change kstrdup() to devm_kstrdup()

To apply on v6.6 a 1-line change is needed:

static int cs35l56_get_firmware_uid(struct cs35l56_private *cs35l56)
{
-       struct device *dev = cs35l56->dev;
+       struct device *dev = cs35l56->base.dev;

Maciej Strozek (1):
  ASoC: cs35l56: Read firmware uuid from a device property instead of
    _SUB

Simon Trimmer (1):
  ASoC: cs35l56: Add an ACPI match table

 sound/soc/codecs/cs35l56-i2c.c |  9 +++++++++
 sound/soc/codecs/cs35l56-spi.c |  9 +++++++++
 sound/soc/codecs/cs35l56.c     | 31 ++++++++++++-------------------
 3 files changed, 30 insertions(+), 19 deletions(-)

-- 
2.30.2


             reply	other threads:[~2023-08-17 11:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-17 11:27 Richard Fitzgerald [this message]
2023-08-17 11:27 ` [PATCH v2 1/2] ASoC: cs35l56: Read firmware uuid from a device property instead of _SUB Richard Fitzgerald
2023-08-17 11:27 ` [PATCH v2 2/2] ASoC: cs35l56: Add an ACPI match table Richard Fitzgerald
2023-08-17 22:36 ` [PATCH v2 0/2] ASoC: cs35l56: Update ACPI HID and property 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=20230817112712.16637-1-rf@opensource.cirrus.com \
    --to=rf@opensource.cirrus.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@opensource.cirrus.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox