Message ID | 20230922174854.611975-1-miquel.raynal@bootlin.com |
---|---|
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a05:612c:172:b0:3f2:4152:657d with SMTP id h50csp5935097vqi; Fri, 22 Sep 2023 16:54:37 -0700 (PDT) X-Google-Smtp-Source: AGHT+IGsvlFru8u8q5MLoOZ1OCrFKsyNhK7cRNYANq2xr2Q07QdALFE7MlYRdJACW+fM6HYZqUQ1 X-Received: by 2002:a05:6870:1715:b0:1bb:5480:4b4 with SMTP id h21-20020a056870171500b001bb548004b4mr1061869oae.8.1695426876896; Fri, 22 Sep 2023 16:54:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1695426876; cv=none; d=google.com; s=arc-20160816; b=U39nkV907GxezTpyM/EfgbNNoFFK76VFoKE6GUYg8C2VOoYa3LOr8x6N5qkYtMBWkY Sz7XnEr5ZXSLRjucwkUKqPAKKThzdMJQ2+CCngbjChw6jzpzJ9tgKuq3jXB9hrd2505b 8aTZB0WzmIJR2c1WcgMNfA4MFdomXWnFSe+Oj8i7PjHyPWBf/uTW+8z2KsySS0qyUD9z wSMc6iDJwQFh/p8QIMjZWvh2Vp4prEqf+ll85C4teDrFniRxWsQmOES6JRzbplUcKguN TiIQuF7UAsXF5LFcVQkP7y3SODfqQildgY+lgOYwYifCUPMQzQrx+LIZ+4P9p4T8fUeS kOtw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=8uEZMn+z2Ga5O+jw4orgjY44OmW9D5RYF/9+50MV1Xc=; fh=uNRYBw15K+4lj0RowSR5ppkZ/jQAGNdwwLd8P1k8N6c=; b=Npf8j7FIjlY0CSxqYVu28AHwXkEWJYpg9l2EAaoisEe4Ge/R498kXJN/A0+8gHLf3s PhnsK5vnqRxvuOWXyb/z5GOp9RI6uabX413dtApTMiMmwAplIlfXTvnosxyjE8IX8DNz xI8og0kzUSXoGruAgpknWhqQiIZDKlPtFNg1j2id8+q6m3SpjX/1g0GNaJ74bCeZ6X5g rhA78gNGN32WpabURPKN348jhV28XY7HcJj/yS6wA7ifcf7LH46bLUc+RhgElt74UEuJ yFyCbVmfVOCBElenJc+JofvLmJnXUzDn5S4tkpyhRvj4g26Ocdx6YCGOKmgo6Rk4evNl xM1w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@bootlin.com header.s=gm1 header.b=dVOwTsL2; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.34 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=bootlin.com Received: from howler.vger.email (howler.vger.email. [23.128.96.34]) by mx.google.com with ESMTPS id n13-20020a65488d000000b005777bea0b6asi4651612pgs.859.2023.09.22.16.54.36 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 22 Sep 2023 16:54:36 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.34 as permitted sender) client-ip=23.128.96.34; Authentication-Results: mx.google.com; dkim=pass header.i=@bootlin.com header.s=gm1 header.b=dVOwTsL2; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.34 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=bootlin.com Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by howler.vger.email (Postfix) with ESMTP id 56461852D27B; Fri, 22 Sep 2023 10:49:26 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at howler.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232883AbjIVRtJ (ORCPT <rfc822;pwkd43@gmail.com> + 28 others); Fri, 22 Sep 2023 13:49:09 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60348 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230053AbjIVRtI (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Fri, 22 Sep 2023 13:49:08 -0400 Received: from relay4-d.mail.gandi.net (relay4-d.mail.gandi.net [IPv6:2001:4b98:dc4:8::224]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C1AB199 for <linux-kernel@vger.kernel.org>; Fri, 22 Sep 2023 10:49:01 -0700 (PDT) Received: by mail.gandi.net (Postfix) with ESMTPSA id A3B5EE0002; Fri, 22 Sep 2023 17:48:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bootlin.com; s=gm1; t=1695404940; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=8uEZMn+z2Ga5O+jw4orgjY44OmW9D5RYF/9+50MV1Xc=; b=dVOwTsL2ddY5edxQxhpLBRNKyeUx+MCOhIj17OekyWIl0uzLKqJ2p1PLFt+3V8KxE+A1q2 +GnEDU6khGLlLgt6MTsa2cNH/5Htg0RkL1utdE2iT1T0g/P38yrNc0wgjb/a25fDlC57Zp z0DOC0RtJkQNjN1HJThDNtiK5uL1eZEXDaSRXdkYQTukYsXmgqKikvTVC2rOwqNa+f5Rwa /bVZHS8Y3saw48/ZIHXURjUc6sTSdPm/x+aDyzSUCbvoKI4sFr5vV7GvvWeArOMBkZZ7bj 8Bl5T+dU18iSYCy4lrWrANCimollp5sQrkPM+Qc8SWl7hvjtR+qLus+KFW0gdw== From: Miquel Raynal <miquel.raynal@bootlin.com> To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>, Greg Kroah-Hartman <gregkh@linuxfoundation.org> Cc: Michael Walle <michael@walle.cc>, Thomas Petazzoni <thomas.petazzoni@bootlin.com>, Robert Marko <robert.marko@sartura.hr>, Luka Perkov <luka.perkov@sartura.hr>, <linux-kernel@vger.kernel.org>, Randy Dunlap <rdunlap@infradead.org>, Chen-Yu Tsai <wenst@chromium.org>, Daniel Golle <daniel@makrotopia.org>, =?utf-8?b?UmFmYcWCIE1pxYJlY2tp?= <rafal@milecki.pl>, Miquel Raynal <miquel.raynal@bootlin.com> Subject: [PATCH v10 0/3] NVMEM cells in sysfs Date: Fri, 22 Sep 2023 19:48:51 +0200 Message-Id: <20230922174854.611975-1-miquel.raynal@bootlin.com> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-GND-Sasl: miquel.raynal@bootlin.com X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS, SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (howler.vger.email [0.0.0.0]); Fri, 22 Sep 2023 10:49:28 -0700 (PDT) X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1777783932448707530 X-GMAIL-MSGID: 1777783932448707530 |
Series | NVMEM cells in sysfs | |
Message
Miquel Raynal
Sept. 22, 2023, 5:48 p.m. UTC
Hello, As part of a previous effort, support for dynamic NVMEM layouts was brought into mainline, helping a lot in getting information from NVMEM devices at non-static locations. One common example of NVMEM cell is the MAC address that must be used. Sometimes the cell content is mainly (or only) useful to the kernel, and sometimes it is not. Users might also want to know the content of cells such as: the manufacturing place and date, the hardware version, the unique ID, etc. Two possibilities in this case: either the users re-implement their own parser to go through the whole device and search for the information they want, or the kernel can expose the content of the cells if deemed relevant. This second approach sounds way more relevant than the first one to avoid useless code duplication, so here is a series bringing NVMEM cells content to the user through sysfs. Here is a real life example with a Marvell Armada 7040 TN48m switch: $ nvmem=/sys/bus/nvmem/devices/1-00563/ $ for i in `ls -1 $nvmem/cells/*`; do basename $i; hexdump -C $i | head -n1; done country-code@77 00000000 54 57 |TW| crc32@88 00000000 bb cd 51 98 |..Q.| device-version@49 00000000 02 |.| diag-version@80 00000000 56 31 2e 30 2e 30 |V1.0.0| label-revision@4c 00000000 44 31 |D1| mac-address@2c 00000000 18 be 92 13 9a 00 |......| manufacture-date@34 00000000 30 32 2f 32 34 2f 32 30 32 31 20 31 38 3a 35 39 |02/24/2021 18:59| manufacturer@72 00000000 44 4e 49 |DNI| num-macs@6e 00000000 00 40 |.@| onie-version@61 00000000 32 30 32 30 2e 31 31 2d 56 30 31 |2020.11-V01| platform-name@50 00000000 38 38 46 37 30 34 30 2f 38 38 46 36 38 32 30 |88F7040/88F6820| product-name@d 00000000 54 4e 34 38 4d 2d 50 2d 44 4e |TN48M-P-DN| serial-number@19 00000000 54 4e 34 38 31 50 32 54 57 32 30 34 32 30 33 32 |TN481P2TW2042032| vendor@7b 00000000 44 4e 49 |DNI| This layout with a cells/ folder containing one file per cell has been legitimately challenged by John Thomson. I am not against the idea of having a sub-folder per cell but I did not find a relevant way to do that so for know I did not change the sysfs organization. If someone really wants this other layout, please provide a code snipped which I can integrate. Current support does not include: * The knowledge of the type of data (binary vs. ASCII), so by default all cells are exposed in binary form. * Write support. Changes in v10: * All preparation patches have been picked-up by Srinivas. * Rebased on top of v6.6-rc1. * Fix an error path in the probe due to the recent additions. Changes in v9: * Hopefully fixed the creation of sysfs entries when describing the cells using the legacy layout, as reported by Chen-Yu. * Dropped the nvmem-specific device list and used the driver core list instead as advised by Greg. Changes in v8: * Fix a compilation warning whith !CONFIG_NVMEM_SYSFS. * Add a patch to return NULL when no layout is found (reported by Dan Carpenter). * Fixed the documentation as well as the cover letter regarding the addition of addresses in the cell names. Changes in v7: * Rework the layouts registration mechanism to use the platform devices logic. * Fix the two issues reported by Daniel Golle and Chen-Yu Tsai, one of them consist in suffixing '@<offset>' to the cell name to create the sysfs files in order to be sure they are all unique. * Update the doc. Changes in v6: * ABI documentation style fixes reported by Randy Dunlap: s|cells/ folder|"cells" folder| Missing period at the end of the final note. s|Ex::|Example::| * Remove spurious patch from the previous resubmission. Resending v5: * I forgot the mailing list in my former submission, both are absolutely identical otherwise. Changes in v5: * Rebased on last -rc1, fixing a conflict and skipping the first two patches already taken by Greg. * Collected tags from Greg. * Split the nvmem patch into two, one which just moves the cells creation and the other which adds the cells. Changes in v4: * Use a core helper to count the number of cells in a list. * Provide sysfs attributes a private member which is the entry itself to avoid the need for looking up the nvmem device and then looping over all the cells to find the right one. Changes in v3: * Patch 1 is new: fix a style issue which bothered me when reading the core. * Patch 2 is new: Don't error out when an attribute group does not contain any attributes, it's easier for developers to handle "empty" directories this way. It avoids strange/bad solutions to be implemented and does not cost much. * Drop the is_visible hook as it is no longer needed. * Stop allocating an empty attribute array to comply with the sysfs core checks (this check has been altered in the first commits). * Fix a missing tab in the ABI doc. Changes in v2: * Do not mention the cells might become writable in the future in the ABI documentation. * Fix a wrong return value reported by Dan and kernel test robot. * Implement .is_bin_visible(). * Avoid overwriting the list of attribute groups, but keep the cells attribute group writable as we need to populate it at run time. * Improve the commit messages. * Give a real life example in the cover letter. Miquel Raynal (3): nvmem: core: Rework layouts to become platform devices ABI: sysfs-nvmem-cells: Expose cells through sysfs nvmem: core: Expose cells through sysfs Documentation/ABI/testing/sysfs-nvmem-cells | 21 ++ drivers/nvmem/core.c | 257 +++++++++++++++++--- drivers/nvmem/layouts/onie-tlv.c | 39 ++- drivers/nvmem/layouts/sl28vpd.c | 39 ++- include/linux/nvmem-provider.h | 11 +- 5 files changed, 318 insertions(+), 49 deletions(-) create mode 100644 Documentation/ABI/testing/sysfs-nvmem-cells