Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp2672237yba; Sat, 18 May 2019 00:03:05 -0700 (PDT) X-Google-Smtp-Source: APXvYqxstLNIUTwu83+rt9WqqMrFH/FvFb7zvQ/reXBZaBGU/k8XZoyBlTY+QglYVAPE3Kfh158W X-Received: by 2002:a17:902:2be7:: with SMTP id l94mr7659162plb.185.1558162984950; Sat, 18 May 2019 00:03:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558162984; cv=none; d=google.com; s=arc-20160816; b=lc5LezVe8+1znfRiEKw1VtMJWd9t2iTYZHr82SmILSQSbUD23NDuRxg4/JLGTWmjmu jdugDo3RlfEZ3pZQAIoAqxGegsuSS7o0NRA384eLCpXf0ckcGQvdILTMEJk7mUcYMwun hp7kvmQRmQ6KppXV9k1mFPvppESGpnohPhWy+01QeJovyfji80jLFpo4EBb6euhwJLWE oU9GmyBR7oBv9ZqSxjCF4mVb2bvGzSnolZcaFQEUrH6hDAIGC6RxE746xCHVWviDxKoP vmoqwy8VxHNEdx/dh/b9BCg8uPwvE05VBzQKvIOkngLUAuU805017TKyhxAhM3epANmf QUMg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=Z6EmfJ+W0cN8hA5D8o11yzt/Z0xoKoMCZuzzWMVAQRw=; b=AEpJzpT4/4jKCdg8h4cVkhPh09rfAZoJ+Zjw6vcvMxut3wgqZpzxiT1T1PmLxIE/BS J3f04pVdKyS0ZU2kvUslrTDm5MzN/uhxD5Ox1L91dZhEaqAl4kx86E/YOBGVtzsw9Ikd yXOHoSbFuneuS3hr/etbmptTPDlvgG5q7hZ9zf9vudwinIbbyo1/Nogj2S3pxyaDJrt7 PKY3WvnrLCoXmkcGmx8WwAkepJmipN3nYWHGY3B8VYmoFRL6E/frp2QFEzzYha7HFNMh D4RDDktDJU5cPlQ1Yp6cx1apE9PQK6VyLkNkgq6+FypTIAVJd5yjqZZj2Lum3lYyB715 Chfg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=Zt0DxaB5; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f14si10502513pfd.228.2019.05.18.00.02.49; Sat, 18 May 2019 00:03:04 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=Zt0DxaB5; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728946AbfERGfF (ORCPT + 99 others); Sat, 18 May 2019 02:35:05 -0400 Received: from mail.kernel.org ([198.145.29.99]:53934 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725268AbfERGfE (ORCPT ); Sat, 18 May 2019 02:35:04 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id D209D20848; Sat, 18 May 2019 06:35:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1558161304; bh=cbQxEDUMUnjV9fqBk/G2W8OaeEiXUXJBn48F5Pv0RZE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Zt0DxaB5vYVAeOnL6lXWGix86p0MB8+VBuFNEzcxsIgaYPvsMxtfO1YoeL4zRgctT H9BIiQcvRlOtTWZBge0I8vp1uzb4eglga8xXeaVbA1Gx/Uz7BxdUZXRjuPggwmqgcU nAPWU2uQ1vViLsTVK14KdMKxMqDJnx9FwKfRo1EQ= Date: Sat, 18 May 2019 08:35:01 +0200 From: Greg Kroah-Hartman To: Liming Sun Cc: Andy Shevchenko , Darren Hart , Vadim Pasternak , David Woods , "platform-driver-x86@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "David S. Miller" , Mauro Carvalho Chehab , Jonathan Cameron , Nicolas Ferre , "Paul E. McKenney" Subject: Re: [PATCH v5 2/2] platform/mellanox/mlxbf-bootctl: Add the ABI definitions Message-ID: <20190518063501.GA26163@kroah.com> References: <0b74e9ad12360b56bc0a3c2ca972798c424f2610.1548790896.git.lsun@mellanox.com> <1558115345-32476-2-git-send-email-lsun@mellanox.com> <20190517175926.GA24535@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.4 (2019-03-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 17, 2019 at 08:36:53PM +0000, Liming Sun wrote: > Thanks Greg for the comments! Please see my response inline. > > Regards, > - Liming > > > -----Original Message----- > > From: Greg Kroah-Hartman > > Sent: Friday, May 17, 2019 1:59 PM > > To: Liming Sun > > Cc: Andy Shevchenko ; Darren Hart ; Vadim Pasternak ; David > > Woods ; platform-driver-x86@vger.kernel.org; linux-kernel@vger.kernel.org; David S. Miller > > ; Mauro Carvalho Chehab ; Jonathan Cameron > > ; Nicolas Ferre ; Paul E. McKenney > > 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 > > > Signed-off-by: Liming Sun > > > --- > > > .../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 " > > > +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. > > This driver is running on the ARM processor of the SoC. The 'device' is > the SoC itself. That's to say, there is only one device here attached to > the driver and the driver state will also be the device state. That might be true today, but maybe not tomorrow :) Anyway, again, this is device state, not driver state. > This interface has been used by user-space applications for a couple of > releases. It'll be great if it could stay in such way for compatibility. Please > advise if this is strongly preferred to move them under devices. So this is code that is already in the tree, and is just now being documented? What .c file(s) is this referring to? As for "comptability", sysfs is made such that if a file is not present, userspace should be able to survive, that is why it is one-value-per-file. What tool is using this, and where is the source for it? thanks, greg k-h