From: Mark Brown <broonie@kernel.org>
To: Hyun-Uk Son <hyunuk.son@irondevice.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Ki-Seok Jo <kiseok.jo@irondevice.com>,
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>,
"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] ASoC: codecs: Add driver for Iron Device MA5311
Date: Mon, 16 Nov 2026 20:44:20 +0000 [thread overview]
Message-ID: <435b0669-1870-42c2-a1ac-d2e9a409ac7d@sirena.org.uk> (raw)
In-Reply-To: <SE2P216MB24235412B165FEA906C3D24FFF7C2@SE2P216MB2423.KORP216.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 1517 bytes --]
On Mon, Nov 16, 2026 at 04:57:11AM +0000, Hyun-Uk Son wrote:
> > > The values of these parameters in reg_defaults match the hardware
> > factory defaults.
> > Right, those are what the driver should nromally use.
> When you say "these parameters", are you referring specifically to
> gain-related settings, such as speaker volume, ADC gain, and PGA gain,
> or does this also include data path and output format settings?
Data path yes normally, but see below. Output format I guess so, though
that will essentially always be overwritten by the machine driver in the
normal course of affairs so it's rare to actually get the default
register values in practice.
> To make sure I understand your recommendation correctly, should
> the driver leave the data path and output format settings at their
> factory defaults as well?
> Or would it be acceptable to initialize the data path and output
> format settings while keeping sensitive parameters, such as speaker
> volume and ADC/PGA gain, at their factory defaults?
For the output format it's probably fine to change it, though like I say
I'm not sure that the setting would actually end up getting used. For
the data path usually we'd go with the hardware default unless there is
a very strong reason - for example drivers with DSP support might adjust
routing to/from the DSP as part of integrate handling for the DSP. If
it's just basic routing of the DAC to an ouput or whatever that's
usually left under user control.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-11-16 20:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 9:32 [PATCH v2 0/2] ASoC: Add Iron Device MA5311 support Hyunuk Son
2026-10-27 9:32 ` [PATCH v2 1/2] ASoC: dt-bindings: Add Iron Device MA5311 Hyunuk Son
2026-10-28 12:26 ` Krzysztof Kozlowski
2026-10-27 9:32 ` [PATCH v2 2/2] ASoC: codecs: Add driver for " Hyunuk Son
2026-10-28 11:25 ` Mark Brown
2026-11-10 8:41 ` Hyun-Uk Son
2026-11-10 13:50 ` Mark Brown
2026-11-12 0:40 ` Hyun-Uk Son
2026-11-12 19:37 ` Mark Brown
2026-11-16 4:57 ` Hyun-Uk Son
2026-11-16 20:44 ` Mark Brown [this message]
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=435b0669-1870-42c2-a1ac-d2e9a409ac7d@sirena.org.uk \
--to=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hyunuk.son@irondevice.com \
--cc=kiseok.jo@irondevice.com \
--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
all inboxes | Powered by JetHome®