linux-kernel - [sysfs] Sysfs acceptable paths to custom functionality

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>] [day] [month] [year] [list]

Message-ID: <d2bdfc4c-ffdb-71c2-3b9e-d1957e50a73d@gmail.com>
Date:   Fri, 6 Oct 2017 00:45:11 -0500
From:   steven <steven.eckhoff.opensource@...il.com>
To:     linux-kernel@...r.kernel.org
Subject: [sysfs] Sysfs acceptable paths to custom functionality

I am developing a driver for an audio codec that has fixed DSP 
functionality. On the device there are coefficients that can be 
programmed to implement different types of filters that can be used to 
implement an EQ or 3D sound effects.

Based on what I have seen in the Kernel so far our device is the only 
one that has this type of feature, but I do believe others exist. Due to 
this I would like to generalize this as much as possible so user space 
applications can take advantage of it.

1. Where under /sys/ should I expose these features?

My initial thought for the interface would look something like this:

some_device/
..features/
....eq1/
......band1/
........coefficient_a1
........coefficient_a2
....eq2/
....3dbass/
....3dtreb/

2. Do you see anything wrong with this approach?

Please CC me in your responses.

Regards,

Steven