From: Greg KH <gregkh@linuxfoundation.org>
To: richard.gong@linux.intel.com
Cc: robh+dt@kernel.org, mark.rutland@arm.com, dinguyen@kernel.org,
atull@kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, Richard Gong <richard.gong@intel.com>
Subject: Re: [PATCHv1 5/6] firmware: rsu: document sysfs interface
Date: Thu, 25 Apr 2019 22:28:27 +0200 [thread overview]
Message-ID: <20190425202827.GD22307@kroah.com> (raw)
In-Reply-To: <1554835562-25056-6-git-send-email-richard.gong@linux.intel.com>
On Tue, Apr 09, 2019 at 01:46:01PM -0500, richard.gong@linux.intel.com wrote:
> From: Richard Gong <richard.gong@intel.com>
>
> Describe Intel Stratix10 Remote System Update (RSU) device attributes
>
> Signed-off-by: Richard Gong <richard.gong@intel.com>
> Reviewed-by: Alan Tull <atull@kernel.org>
> ---
> .../testing/sysfs-devices-platform-stratix10-rsu | 78 ++++++++++++++++++++++
> 1 file changed, 78 insertions(+)
> create mode 100644 Documentation/ABI/testing/sysfs-devices-platform-stratix10-rsu
>
> diff --git a/Documentation/ABI/testing/sysfs-devices-platform-stratix10-rsu b/Documentation/ABI/testing/sysfs-devices-platform-stratix10-rsu
> new file mode 100644
> index 0000000..cb461ee
> --- /dev/null
> +++ b/Documentation/ABI/testing/sysfs-devices-platform-stratix10-rsu
> @@ -0,0 +1,78 @@
> + Intel Stratix10 Remote System Update (RSU) device attributes
> +
> +What: /sys/devices/platform/soc:firmware:svc/soc:firmware:svc:rsu/current_image
> +Date: April 2019
> +KernelVersion: 5.2
> +Contact: Richard Gong <richard.gong@intel.com>
> +Description:
> + (RO) the address of image currently running in flash.
> +
> +What: /sys/devices/platform/soc:firmware:svc/soc:firmware:svc:rsu/fail_image
> +Date: April 2019
> +KernelVersion: 5.2
> +Contact: Richard Gong <richard.gong@intel.com>
> +Description:
> + (RO) the address of failed image in flash.
> +
> +What: /sys/devices/platform/soc:firmware:svc/soc:firmware:svc:rsu/state
> +Date: April 2019
> +KernelVersion: 5.2
> +Contact: Richard Gong <richard.gong@intel.com>
> +Description:
> + (RO) the state of RSU system.
> + The state field has two parts: major error code in upper 16 bits and minor error code
> + in lower 16 bits.
> + 1. Major error code
> + 0xF001 -- bitstream error
> + 0xF002 -- hardware access failure
> + 0xF003 -- bitstream corruption
> + 0xF004 -- internal error
> + 0xF005 -- device error
> + 0xF006 -- HPS watchdog timeout
> + 0xF007 -- internal unknown error
> + 2: Minor error code
> + Currently used only when major error is 0xF006 (HPS watchdog timeout), in which
> + case the minor error code is the value reported by HPS to firmware through the RSU notify
> + command before the watchdog timeout occurs.
Properly wrap your lines at 72 colums.
next prev parent reply other threads:[~2019-04-25 20:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 18:45 [PATCHv1 0/6] add Intel Stratix10 remote system update driver richard.gong
2019-04-09 18:45 ` [PATCHv1 1/6] firmware: stratix10-svc: add to support RSU notify richard.gong
2019-04-09 18:45 ` [PATCHv1 2/6] dt-bindings, firmware: add Intel Stratix10 remote system update binding richard.gong
2019-04-29 17:48 ` Rob Herring
2019-04-09 18:45 ` [PATCHv1 3/6] arm64: dts: stratix10: add remote system update richard.gong
2019-04-09 18:46 ` [PATCHv1 4/6] firmware: add Intel Stratix10 remote system update driver richard.gong
2019-04-25 20:30 ` Greg KH
2019-04-25 20:33 ` Greg KH
2019-04-09 18:46 ` [PATCHv1 5/6] firmware: rsu: document sysfs interface richard.gong
2019-04-25 20:27 ` Greg KH
2019-04-25 20:28 ` Greg KH [this message]
2019-04-09 18:46 ` [PATCHv1 6/6] MAINTAINERS: add maintainer for Intel Stratix10 FW drivers richard.gong
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=20190425202827.GD22307@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=atull@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=richard.gong@intel.com \
--cc=richard.gong@linux.intel.com \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.