From: steven <steven.eckhoff.opensource@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: [sysfs] Sysfs acceptable paths to custom functionality
Date: Fri, 6 Oct 2017 00:45:11 -0500 [thread overview]
Message-ID: <d2bdfc4c-ffdb-71c2-3b9e-d1957e50a73d@gmail.com> (raw)
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
reply other threads:[~2017-10-06 5:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=d2bdfc4c-ffdb-71c2-3b9e-d1957e50a73d@gmail.com \
--to=steven.eckhoff.opensource@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome