From: Stefan Binding <sbinding@opensource.cirrus.com>
To: <linux-firmware@kernel.org>
Cc: "patches@opensource.cirrus.com" <patches@opensource.cirrus.com>
Subject: [PULL v1 linux-firmware] Add firmware for Cirrus Smart Amp CS35L41 for Lenovo Legion 7i gen7 laptop (16IAX7)
Date: Fri, 16 Feb 2024 16:19:16 +0000 [thread overview]
Message-ID: <b8e9a2a8-1524-4358-9e23-27875a4b3243@opensource.cirrus.com> (raw)
We would like to add firmware files to support Cirrus Logic Smart Amp
CS35L41 for Lenovo Legion 7i gen7 laptop (16IAX7)
Thanks,
Stefan Binding
The following changes since commit f0e2f70ceb682d38604d88343dfc7f80cc46a694:
Merge branch 'robot/patch-0-1708082607' into 'main' (2024-02-16
11:29:57 +0000)
are available in the Git repository at:
https://github.com/CirrusLogic/linux-firmware/ Lenovo16IAX7
for you to fetch changes up to d9fa75944debb977e635a302a1ccd94932fe7cea:
linux-firmware: Add CS35L41 firmware for Lenovo Legion 7i gen7 laptop
(16IAX7) (2024-02-16 14:26:27 +0000)
----------------------------------------------------------------
Stefan Binding (1):
linux-firmware: Add CS35L41 firmware for Lenovo Legion 7i gen7
laptop (16IAX7)
WHENCE | 5 +++++
cirrus/cs35l41-dsp1-spk-cali-17aa386f.bin | Bin 0 -> 1580 bytes
cirrus/cs35l41-dsp1-spk-prot-17aa386f-l0.bin | Bin 0 -> 4808 bytes
cirrus/cs35l41-dsp1-spk-prot-17aa386f-r0.bin | Bin 0 -> 4812 bytes
4 files changed, 5 insertions(+)
create mode 100755 cirrus/cs35l41-dsp1-spk-cali-17aa386f.bin
create mode 100755 cirrus/cs35l41-dsp1-spk-prot-17aa386f-l0.bin
create mode 100755 cirrus/cs35l41-dsp1-spk-prot-17aa386f-r0.bin
next reply other threads:[~2024-02-16 16:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 16:19 Stefan Binding [this message]
2024-02-19 12:46 ` [PULL v1 linux-firmware] Add firmware for Cirrus Smart Amp CS35L41 for Lenovo Legion 7i gen7 laptop (16IAX7) Josh Boyer
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=b8e9a2a8-1524-4358-9e23-27875a4b3243@opensource.cirrus.com \
--to=sbinding@opensource.cirrus.com \
--cc=linux-firmware@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).