[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190517175926.GA24535@kroah.com>
Date: Fri, 17 May 2019 19:59:26 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Liming Sun <lsun@...lanox.com>
Cc: Andy Shevchenko <andy@...radead.org>,
Darren Hart <dvhart@...radead.org>,
Vadim Pasternak <vadimp@...lanox.com>,
David Woods <dwoods@...lanox.com>,
platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org,
"David S. Miller" <davem@...emloft.net>,
Mauro Carvalho Chehab <mchehab+samsung@...nel.org>,
Jonathan Cameron <Jonathan.Cameron@...wei.com>,
Nicolas Ferre <nicolas.ferre@...rochip.com>,
"Paul E. McKenney" <paulmck@...ux.ibm.com>
Subject: Re: [PATCH v5 2/2] platform/mellanox/mlxbf-bootctl: Add the ABI
definitions
On Fri, May 17, 2019 at 01:49:05PM -0400, Liming Sun wrote:
> This commit adds the ABI definitions exposed to userspace for
> the platform/mellanox/mlxbf-bootctl driver.
>
> Reviewed-by: Vadim Pasternak <vadimp@...lanox.com>
> Signed-off-by: Liming Sun <lsun@...lanox.com>
> ---
> .../ABI/testing/sysfs-platform-mellanox-bootctl | 58 ++++++++++++++++++++++
> MAINTAINERS | 1 +
> 2 files changed, 59 insertions(+)
> create mode 100644 Documentation/ABI/testing/sysfs-platform-mellanox-bootctl
>
> diff --git a/Documentation/ABI/testing/sysfs-platform-mellanox-bootctl b/Documentation/ABI/testing/sysfs-platform-mellanox-bootctl
> new file mode 100644
> index 0000000..19a14db
> --- /dev/null
> +++ b/Documentation/ABI/testing/sysfs-platform-mellanox-bootctl
> @@ -0,0 +1,58 @@
> +What: /sys/bus/platform/drivers/mlxbf-bootctl/lifecycle_state
> +Date: May 2019
> +KernelVersion: 5.3
> +Contact: "Liming Sun <lsun@...lanox.com>"
> +Description:
> + The Life-cycle state of the SoC, which could be one of the
> + following values.
> + Production - Production state and can be updated to secure
> + GA Secured - Secure chip and not able to change state
> + GA Non-Secured - Non-Secure chip and not able to change state
> + RMA - Return Merchandise Authorization
A "driver" does not have a lifecycle state, a "device" does.
You are putting all of these attributes in the wrong place. Put them on
your device please, not the driver. driver-specific attributes are
_VERY_ rare, and only for things that can modify/show for all devices
attached to that driver.
thanks,
greg k-h
Powered by blists - more mailing lists