From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: Simon Trimmer <simont@opensource.cirrus.com>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com, tiwai@suse.de
Subject: Re: [PATCH 2/2] ALSA: hda: cs35l56: Log tuning unique identifiers during firmware load
Date: Wed, 14 May 2025 10:51:53 +0200 [thread overview]
Message-ID: <877c2jval2.wl-tiwai@suse.de> (raw)
In-Reply-To: <aCRUgeFcG4iubmSV@finisterre.sirena.org.uk>
On Wed, 14 May 2025 10:29:53 +0200,
Mark Brown wrote:
>
> On Tue, May 13, 2025 at 01:39:24PM +0000, Simon Trimmer wrote:
> > The cs35l56 smart amplifier has some informational firmware controls
> > that are populated by a tuning bin file to unique values - logging these
> > during firmware load identifies the specific configuration being used on
> > that device instance.
>
> Adding Takashi since this is an ALSA patch (and not deleting context for
> him), Takashi is this OK to go via ASoC?
Sure, it's a simple logging, feel free to pick it up.
Acked-by: Takashi Iwai <tiwai@suse.de>
thanks,
Takashi
> As documented in submitting-patches.rst please send patches to the
> maintainers for the code you would like to change. The normal kernel
> workflow is that people apply patches from their inboxes, if they aren't
> copied they are likely to not see the patch at all and it is much more
> difficult to apply patches.
>
> >
> > Signed-off-by: Simon Trimmer <simont@opensource.cirrus.com>
> > ---
> > sound/pci/hda/cs35l56_hda.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/sound/pci/hda/cs35l56_hda.c b/sound/pci/hda/cs35l56_hda.c
> > index b6fecf119261..aed7d7284231 100644
> > --- a/sound/pci/hda/cs35l56_hda.c
> > +++ b/sound/pci/hda/cs35l56_hda.c
> > @@ -676,6 +676,8 @@ static void cs35l56_hda_fw_load(struct cs35l56_hda *cs35l56)
> > if (ret)
> > cs_dsp_stop(&cs35l56->cs_dsp);
> >
> > + cs35l56_log_tuning(&cs35l56->base, &cs35l56->cs_dsp);
> > +
> > err_powered_up:
> > if (!cs35l56->base.fw_patched)
> > cs_dsp_power_down(&cs35l56->cs_dsp);
> > --
> > 2.43.0
> >
> Verifying...
next prev parent reply other threads:[~2025-05-14 8:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 13:39 [PATCH 0/2] cs35l56: Log tuning unique identifiers during firmware load Simon Trimmer
2025-05-13 13:39 ` [PATCH 1/2] ASoC: " Simon Trimmer
2025-05-13 13:39 ` [PATCH 2/2] ALSA: hda: " Simon Trimmer
2025-05-14 8:29 ` Mark Brown
2025-05-14 8:51 ` Takashi Iwai [this message]
2025-05-15 12:08 ` [PATCH 0/2] " 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=877c2jval2.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=simont@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.