lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <37e0f08b-ce35-450b-9abf-d3be09d2863f@sirena.org.uk>
Date: Thu, 16 Oct 2025 12:27:36 +0100
From: Mark Brown <broonie@...nel.org>
To: Takashi Iwai <tiwai@...e.de>
Cc: Richard Fitzgerald <rf@...nsource.cirrus.com>, tiwai@...e.com,
	linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org,
	patches@...nsource.cirrus.com
Subject: Re: [PATCH 05/11] ALSA: hda/cs35l56: Create sysfs files for factory
 calibration

On Thu, Oct 16, 2025 at 01:01:41PM +0200, Takashi Iwai wrote:
> Richard Fitzgerald wrote:

> > Create sysfs files that can be used to perform factory calibration.

> What kind of data format should be written to calibrate sysfs entry?
> Since those are no trivial files, we may need to document the
> formats.

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.

> Also, the scenario isn't clear -- who should write this sysfs at which
> moment?  e.g. is this supposed to be set up at each boot?

AIUI it's some tooling that gets run in the factory only.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ