From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: Richard Fitzgerald <rf@opensource.cirrus.com>,
Takashi Iwai <tiwai@suse.de>,
tiwai@suse.com, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org, patches@opensource.cirrus.com
Subject: Re: [PATCH 05/11] ALSA: hda/cs35l56: Create sysfs files for factory calibration
Date: Thu, 16 Oct 2025 14:45:39 +0200 [thread overview]
Message-ID: <87tszz6mmk.wl-tiwai@suse.de> (raw)
In-Reply-To: <d4e94837-6e0b-4b47-896d-d0dd3a59a39b@sirena.org.uk>
On Thu, 16 Oct 2025 14:13:16 +0200,
Mark Brown wrote:
>
> On Thu, Oct 16, 2025 at 12:58:15PM +0100, Richard Fitzgerald wrote:
> > On 16/10/2025 12:27 pm, Mark Brown wrote:
>
> > > This feels like it might be a better fit for debugfs or possibly
> > > configfs? It's not really within the sysfs rules, and especially
> > > debugfs is a lot more relaxed about everything.
>
> > debugfs is an easy change in the driver but more complex for the
> > tooling. Unlike sysfs there's no standard layout or naming convention
> > for the ASoC debugfs tree, so it's more troublesome to locate the amp
> > entries.
>
> > ASoC creates a debugfs root by default if DEBUGFS is enabled. But HDA
> > doesn't have its own debugfs. There is an ALSA debugfs enabled by
> > CONFIG_SND_DEBUG, which is normally disabled. But enabling
> > CONFIG_SND_DEBUG has other side-effects, it enables more than debugfs.
>
> > Or we could create a new debugfs node specifically for Cirrus Logic
> > directly in /sys/kernel/debug.
>
> Dunno about Takashi but for this application I'd be happy for you to
> just put something in the root of debugfs.
I'm fine with debugfs root. The current approach with sysfs looks too
generic for the need of this access, so I find debugfs would be a
better fit, too.
thanks,
Takashi
next prev parent reply other threads:[~2025-10-16 12:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 10:42 [PATCH 00/11] ALSA: cs35l56: Add support for factory calibration Richard Fitzgerald
2025-10-16 10:42 ` [PATCH 01/11] ASoC: cs35l56: Read silicon ID during initialization and save it Richard Fitzgerald
2025-10-16 10:42 ` [PATCH 02/11] ASoC: cs-amp-lib: Add helpers for factory calibration Richard Fitzgerald
2025-10-16 10:42 ` [PATCH 03/11] ASoC: cs35l56: Add common code " Richard Fitzgerald
2025-10-16 10:42 ` [PATCH 04/11] ASoC: cs35l56: Create sysfs files " Richard Fitzgerald
2025-10-16 10:42 ` [PATCH 05/11] ALSA: hda/cs35l56: " Richard Fitzgerald
2025-10-16 11:01 ` Takashi Iwai
2025-10-16 11:27 ` Mark Brown
2025-10-16 11:58 ` Richard Fitzgerald
2025-10-16 12:13 ` Mark Brown
2025-10-16 12:45 ` Takashi Iwai [this message]
2025-10-16 10:42 ` [PATCH 06/11] ASoC: cs-amp-lib-test: Add cases for factory calibration helpers Richard Fitzgerald
2025-10-16 10:42 ` [PATCH 07/11] ASoC: cs-amp-lib: Return attributes from cs_amp_get_efi_variable() Richard Fitzgerald
2025-10-16 10:42 ` [PATCH 08/11] ASoC: cs-amp-lib: Add function to write calibration to EFI Richard Fitzgerald
2025-10-16 10:42 ` [PATCH 09/11] ASoC: cs35l56: Add calibration command to store into UEFI Richard Fitzgerald
2025-10-16 10:42 ` [PATCH 10/11] ALSA: hda/cs35l56: Set cal_index to the amp index Richard Fitzgerald
2025-10-16 10:42 ` [PATCH 11/11] ASoC: cs-amp-lib-test: Add test cases for cs_amp_set_efi_calibration_data() Richard Fitzgerald
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=87tszz6mmk.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=rf@opensource.cirrus.com \
--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