From: Nick <nick.li@foursemi.com>
To: lgirdwood@gmail.com, broonie@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, perex@perex.cz,
tiwai@suse.com, nick.li@foursemi.com
Cc: xiaoming.yang@foursemi.com, danyang.zheng@foursemi.com,
like.xy@foxmail.com, linux-sound@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/4] ASoC: codecs: Add support for FourSemi FS2104/5S
Date: Fri, 18 Jul 2025 20:12:17 +0800 [thread overview]
Message-ID: <20250718121221.76957-1-nick.li@foursemi.com> (raw)
v2 -> v3:
.../foursemi,fs2105s.yaml(patch 0002)
- Drop "schema for " in the patch subject
- Delete the description of the property reg
- Restore the property clocks to v1
- Keep the same order as in list of properties
.../Kconfig(patch 0004)
- Write the help of config symbol with at least 4 lines
.../fs210x.c/h(patch 0004)
- Update entries comment to C++ style
- Use linux/gpio/consumer.h instead of linux/of_gpio.h
- Use a private lock instead of a global one
- Delete driver version and log
- Drop checking of pval in fs210x_reg_read
- Drop most of the debug logs and unused codes
- Drop registers dumping in monitor
- Use fsleep instead of usleep_range
- Update mixer to a standard control:
PCM Playback Volume
- Add 2 new standard controls:
DAC Mute Switch: Mute/Unmute
DAC Fade Switch: Fade enable/disable
- Fix errors reported by mixer-test in mixer:
Effect Scene
- Integrate the operation of reset(sdz) pin into chip init/reset
- Add DAPM event for playback:
Start/stop device in DAPM instead of mute_stream
Start/stop delay works in mute_stream only
- Drop use_pmdown_time in component driver for DAPM event
- Add dai ops startup:
Report format&sample rates in constraints
- Add dai ops trigger:
Start device in trigger when we can't obtain/control the bclk clock
- Use description words: PROVIDER, comsumer
- Add a sysfs node for monitor period(fs210x->check_interval_ms)
- Do the initialisations of delayed works and clock in i2c probe
- Prevent new work after the device is suspended
- Update regmap cache type to MAPLE
Define volatile registers
- Simplify the logic of getting and setting clock
- Simplify the logic of getting and setting reset gpio
- Use dev_err_probe for error logs
- Remove fs210x_parse_platdata and use fs210x_parse_dts in fs210x_init
- Drop null checking for regmap in i2c probe
- Add a suffix(instances id) to dai name
- Drop compatible of "foursemi,fs2104"
- Drop ifdef CONFIG_OF and of_match_ptr
Nick Li (4):
dt-bindings: vendor-prefixes: Add Shanghai FourSemi Semiconductor
Co.,Ltd
ASoC: dt-bindings: Add FS2104/5S audio amplifiers
ASoC: codecs: Add library for FourSemi audio amplifiers
ASoC: codecs: Add FourSemi FS2104/5S audio amplifier driver
.../bindings/sound/foursemi,fs2105s.yaml | 99 ++
.../devicetree/bindings/vendor-prefixes.yaml | 2 +
sound/soc/codecs/Kconfig | 14 +
sound/soc/codecs/Makefile | 4 +
sound/soc/codecs/fs-amp-lib.c | 265 +++
sound/soc/codecs/fs-amp-lib.h | 150 ++
sound/soc/codecs/fs210x.c | 1574 +++++++++++++++++
sound/soc/codecs/fs210x.h | 75 +
8 files changed, 2183 insertions(+)
create mode 100644 Documentation/devicetree/bindings/sound/foursemi,fs2105s.yaml
create mode 100644 sound/soc/codecs/fs-amp-lib.c
create mode 100644 sound/soc/codecs/fs-amp-lib.h
create mode 100644 sound/soc/codecs/fs210x.c
create mode 100644 sound/soc/codecs/fs210x.h
base-commit: ed73a24357531e1747a6e140c329015da6429629
--
2.39.5
next reply other threads:[~2025-07-18 12:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 12:12 Nick [this message]
2025-07-18 12:12 ` [PATCH v3 1/4] dt-bindings: vendor-prefixes: Add Shanghai FourSemi Semiconductor Co.,Ltd Nick
2025-07-21 0:38 ` Rob Herring
2025-07-18 12:12 ` [PATCH v3 2/4] ASoC: dt-bindings: Add FS2104/5S audio amplifiers Nick
2025-07-21 0:39 ` Rob Herring (Arm)
2025-07-18 12:12 ` [PATCH v3 3/4] ASoC: codecs: Add library for FourSemi " Nick
2025-07-18 12:12 ` [PATCH v3 4/4] ASoC: codecs: Add FourSemi FS2104/5S audio amplifier driver Nick
2025-07-18 22:40 ` kernel test robot
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=20250718121221.76957-1-nick.li@foursemi.com \
--to=nick.li@foursemi.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=danyang.zheng@foursemi.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=like.xy@foxmail.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 \
--cc=xiaoming.yang@foursemi.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
all inboxes | Powered by JetHome®