devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Nick Li <nick.li@foursemi.com>
Cc: lgirdwood@gmail.com, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, perex@perex.cz, tiwai@suse.com,
	xiaoming.yang@foursemi.com, danyang.zheng@foursemi.com,
	linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/4] ASoC: codecs: Add FourSemi FS2104/5S audio amplifier driver
Date: Mon, 7 Jul 2025 21:42:07 +0100	[thread overview]
Message-ID: <f2055d69-af5a-46a9-8bb7-46ec3175b790@sirena.org.uk> (raw)
In-Reply-To: <88CC983A5550253C+aGuGe7pQvIBPclfz@foursemi.com>

[-- Attachment #1: Type: text/plain, Size: 1876 bytes --]

On Mon, Jul 07, 2025 at 04:34:03PM +0800, Nick Li wrote:
> On Fri, Jul 04, 2025 at 03:37:32PM +0100, Mark Brown wrote:
> > On Fri, Jul 04, 2025 at 07:12:47PM +0800, Nick Li wrote:
> > > On Thu, Jul 03, 2025 at 03:59:34PM +0100, Mark Brown wrote:
> > > > On Thu, Jul 03, 2025 at 11:56:37AM +0800, Nick wrote:

> > > the volume will be masked in fs210x->vol[2],
> > > we restore the volume when the driver resumes(reinitializes) the deivce.

> > You're not just restoring the values on resume, you're also overwriting
> > them on probe.

> Yes, the volume will be set to the default value at the first time of initialization on probe,
> and it may be updated by volume control later.
> It's a good way to use the regmap cache(REGCACHE_RBTREE) to cache the volumes.

Great.  Note that for new things you should generally use _MAPLE
instead, it's a more modern data structure - _RBTREE can still make
sense for some specialist use cases but this is unlikely to be one of
them.

> > There's not great options here, and you're going to loose the start of
> > playback especially with devices that don't start clocking until audio
> > starts.  You really need the CPU vendors you're working with to
> > implement SND_SOC_DAIFMT_CONT or expose their clocks via the clock API
> > but not all hardware is able to do this.  I think given how limited your
> > hardware is here you really need something in trigger() or some new
> > callback that runs later than that, the delayed work you've got there is
> > trying to fudge things to run after trigger.

> We will start the start_work in dai->trigger if there is no clock bclk
> for us to control, and disable fading in/out in firmware to reduce
> the time consumption if it is needed(As a backup plan).

Great.  You could also make the fade in/out user selectable so the
application can trade off between pops/clicks and cut off audio.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2025-07-07 20:42 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-03  3:56 [PATCH v1 0/4] ASoC: codecs: Add support for FourSemi FS2104/5S Nick
2025-07-03  3:56 ` [PATCH v1 1/4] ASoC: codecs: Add library for FourSemi audio amplifiers Nick
2025-07-03  3:56 ` [PATCH v1 2/4] ASoC: codecs: Add FourSemi FS2104/5S audio amplifier driver Nick
2025-07-03 14:59   ` Mark Brown
2025-07-04 11:12     ` Nick Li
2025-07-04 14:37       ` Mark Brown
2025-07-07  8:34         ` Nick Li
2025-07-07 20:42           ` Mark Brown [this message]
2025-07-03  3:56 ` [PATCH v1 3/4] ASoC: dt-bindings: Add dt bindings for FS2104/5S audio amplifiers Nick
2025-07-03  5:48   ` Rob Herring (Arm)
2025-07-03  6:36   ` Krzysztof Kozlowski
2025-07-04  6:00     ` Nick Li
2025-07-03  7:10   ` Krzysztof Kozlowski
2025-07-03  7:15     ` Krzysztof Kozlowski
2025-07-04  7:26       ` Nick Li
2025-07-04  7:18     ` Nick Li
2025-07-03  3:56 ` [PATCH v1 4/4] dt-bindings: vendor-prefixes: Add Shanghai FourSemi Semiconductor Co.,Ltd Nick
2025-07-03  5:48   ` Rob Herring (Arm)
2025-07-08 11:28 ` [PATCH v2 0/4] ASoC: codecs: Add support for FourSemi FS2104/5S Nick Li
2025-07-08 11:28   ` [PATCH v2 1/4] dt-bindings: vendor-prefixes: Add Shanghai FourSemi Semiconductor Co.,Ltd Nick Li
2025-07-09 10:36     ` Krzysztof Kozlowski
2025-07-08 11:28   ` [PATCH v2 2/4] ASoC: dt-bindings: Add schema for FS2104/5S audio amplifiers Nick Li
2025-07-09 10:40     ` Krzysztof Kozlowski
2025-07-10  8:11       ` Nick Li
2025-07-10  8:27         ` Krzysztof Kozlowski
2025-07-10  9:26           ` Nick Li
2025-07-09 10:42     ` Krzysztof Kozlowski
2025-07-10  8:02       ` Nick Li
2025-07-08 11:29   ` [PATCH v2 3/4] ASoC: codecs: Add library for FourSemi " Nick Li
2025-07-08 11:29   ` [PATCH v2 4/4] ASoC: codecs: Add FourSemi FS2104/5S audio amplifier driver Nick Li
2025-07-09 10:55     ` Krzysztof Kozlowski
2025-07-10  7:56       ` Nick Li
2025-07-10  8:27         ` Krzysztof Kozlowski
2025-07-10 11:20           ` Nick Li
2025-07-09 11:29     ` Mark Brown
2025-07-10  8:57       ` Nick Li
2025-07-10  9:29         ` 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=f2055d69-af5a-46a9-8bb7-46ec3175b790@sirena.org.uk \
    --to=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=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=nick.li@foursemi.com \
    --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;
as well as URLs for NNTP newsgroup(s).