From: Sebastien Guiriec <sebastien.guiriec@intel.com>
To: alsa-devel@alsa-project.org, vinod.koul@intel.com,
pierre-louis.bossart@linux.intel.com,
liam.r.girdwood@linux.intel.com, broonie@kernel.org
Cc: Sebastien Guiriec <sebastien.guiriec@intel.com>
Subject: [PATCH v4 4/4] Documentation: ABI: Add ASoC Intel SST Atom sysfs description
Date: Thu, 24 Nov 2016 09:49:22 +0100 [thread overview]
Message-ID: <20161124084922.9623-5-sebastien.guiriec@intel.com> (raw)
In-Reply-To: <20161124084922.9623-1-sebastien.guiriec@intel.com>
For ASoC Intel SST Atom based devices a sysfs entry is created
in order to track FW version. The FW version is useful in order to
check the different Version of LPE DSP FW across Intel SoCs.
Signed-off-by: Sebastien Guiriec <sebastien.guiriec@intel.com>
---
Documentation/ABI/testing/sysfs-platform-sst-atom | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
create mode 100644 Documentation/ABI/testing/sysfs-platform-sst-atom
diff --git a/Documentation/ABI/testing/sysfs-platform-sst-atom b/Documentation/ABI/testing/sysfs-platform-sst-atom
new file mode 100644
index 0000000..abb131e
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-platform-sst-atom
@@ -0,0 +1,18 @@
+What: /sys/devices/platform/8086%x:00/firmware_version
+Date: November 2016
+KernelVersion: 4.10
+Contact: "Sebastien Guiriec" <sebastien.guiriec@intel.com>
+Description:
+ LPE Firmware version for SST driver on all atom
+ plaforms (BYT/CHT/Merrifield/BSW).
+ If the FW has never been loaded it will display:
+ "FW not yet loaded"
+ If FW has been loaded it will display:
+ "v01.aa.bb.cc"
+ aa: Major version is reflecting SoC version:
+ 0d: BYT FW
+ 0b: BSW FW
+ 07: Merrifield FW
+ bb: Minor version
+ cc: Build version
+
--
2.9.3
---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number: 302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
next prev parent reply other threads:[~2016-11-24 8:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 8:49 [PATCH v4 0/4] ASoC: intel: atom: Add FW version information Sebastien Guiriec
2016-11-24 8:49 ` [PATCH v4 1/4] ASoC: intel: atom: Add debug information related to FW version Sebastien Guiriec
2016-11-30 18:17 ` Mark Brown
2016-12-01 8:56 ` Sebastien Guiriec
2016-12-01 20:17 ` Mark Brown
2016-11-24 8:49 ` [PATCH v4 2/4] ASoC: Intel: atom: save " Sebastien Guiriec
2016-11-24 8:49 ` [PATCH v4 3/4] ASoC: Intel: atom: Add sysfs entry in order to store " Sebastien Guiriec
2016-11-24 8:49 ` Sebastien Guiriec [this message]
2016-11-28 16:01 ` [PATCH v4 0/4] ASoC: intel: atom: Add FW version information Vinod Koul
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=20161124084922.9623-5-sebastien.guiriec@intel.com \
--to=sebastien.guiriec@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=vinod.koul@intel.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;
as well as URLs for NNTP newsgroup(s).