From: Svyatoslav Ryhel <clamor95@gmail.com>
To: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Svyatoslav Ryhel <clamor95@gmail.com>
Cc: linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] ASoC: codecs: Add support for Fortemedia FM34NE DSP
Date: Mon, 19 Oct 2026 13:13:54 +0300 [thread overview]
Message-ID: <20261019101357.117462-1-clamor95@gmail.com> (raw)
The Fortemedia FM34NE is digital sound processing chip used for
active noise suppression mainly on ASUS Transformers.
---
Changes in v2:
- remove ports from schema
- schema moved to dsp
- add return value check in fm34ne_dsp_set_config()
- dropped unused headers
---
Svyatoslav Ryhel (2):
ASoC: dt-bindings: Document FM34NE DSP
ASoC: codecs: Add support for Fortemedia FM34NE DSP
.../bindings/dsp/asus,tf201-dsp.yaml | 77 ++
sound/soc/codecs/Kconfig | 12 +
sound/soc/codecs/Makefile | 2 +
sound/soc/codecs/fm34ne-dsp.c | 390 +++++++
sound/soc/codecs/fm34ne-dsp.h | 1030 +++++++++++++++++
5 files changed, 1511 insertions(+)
create mode 100644 Documentation/devicetree/bindings/dsp/asus,tf201-dsp.yaml
create mode 100644 sound/soc/codecs/fm34ne-dsp.c
create mode 100644 sound/soc/codecs/fm34ne-dsp.h
--
2.53.0
next reply other threads:[~2026-10-19 10:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 10:13 Svyatoslav Ryhel [this message]
2026-10-19 10:13 ` [PATCH v2 1/2] ASoC: dt-bindings: Document FM34NE DSP Svyatoslav Ryhel
2026-10-19 10:17 ` sashiko-bot
2026-10-20 15:12 ` Rob Herring (Arm)
2026-10-19 10:13 ` [PATCH v2 2/2] ASoC: codecs: Add support for Fortemedia " Svyatoslav Ryhel
2026-10-19 10:29 ` sashiko-bot
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=20261019101357.117462-1-clamor95@gmail.com \
--to=clamor95@gmail.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=robh@kernel.org \
--cc=tiwai@suse.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