From: Miquel Raynal <miquel.raynal@bootlin.com> To: Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzk+dt@kernel.org>, devicetree@vger.kernel.org Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>, <linux-kernel@vger.kernel.org>, Robert Marko <robert.marko@sartura.hr>, Luka Perkov <luka.perkov@sartura.hr>, Thomas Petazzoni <thomas.petazzoni@bootlin.com>, Michael Walle <michael@walle.cc>, <linux-arm-kernel@lists.infradead.org>, Bartosz Golaszewski <brgl@bgdev.pl>, Christian Eggers <ceggers@arri.de>, Cory Tusar <cory.tusar@pid1solutions.com>, Miquel Raynal <miquel.raynal@bootlin.com> Subject: [PATCH v3 0/6] Bindings for NVMEM layouts Date: Fri, 4 Nov 2022 17:38:27 +0100 [thread overview] Message-ID: <20221104163833.1289857-1-miquel.raynal@bootlin.com> (raw) Hello, A month ago, Michael was sending a new iteration of his series bringing nvmem layout support. The idea is: we currently can produce nvmem cells statically defined on top of nvmem devices (which themselves may be MTD devices sometimes) but in some cases we may need more advanced parsing, which is possible thanks to the introduction of nvmem layout parsers. I am not taking over the entire series but I recently tried to make use of these layouts for the ONIE tlv table layout and Rob (rightfully) pointed out that the description was messy, because of the mix between nvmem devices and nvmem parsers. This was known to Michael which initially argued that it was simpler to handle like that. So here is a new proposal for the bindings which is described in details within "dt-bindings: nvmem: Introduce the nvmem-layout container". The idea to avoid mixing different node contents is to use a container node when relevant (suggested by Rob) which I named nvmem-layout. This container will have a compatible that describes the parser (plus possible additional properties). Michael, I have a few fixup! patches which apply directly to your former series in order to support this additional container. I propose we first settle the bindings (including the two direct use cases as examples) and once merged, we can move forward and respin both the nvmem series + the layout drivers. # Original series (v2) from Michael Link: https://lore.kernel.org/linux-arm-kernel/20220921115813.208ff789@xps-13/T/#mb97d5376647ff3e686b9c55e3d5e0dc80879e84a Cheers, Miquèl Michael Walle (1): dt-bindings: nvmem: add YAML schema for the sl28 vpd layout Miquel Raynal (5): dt-bindings: nvmem: Fix example dt-bindings: nvmem: Introduce the nvmem-layout container dt-bindings: eeprom: Inherit from nvmem.yaml dt-bindings: vendor-prefixes: Add ONIE dt-bindings: nvmem: add YAML schema for the ONIE tlv layout .../devicetree/bindings/eeprom/at24.yaml | 5 +- .../devicetree/bindings/eeprom/at25.yaml | 1 + .../bindings/eeprom/microchip,93lc46b.yaml | 1 + .../nvmem/layouts/kontron,sl28-vpd.yaml | 60 +++++++++ .../bindings/nvmem/layouts/nvmem-layout.yaml | 34 ++++++ .../nvmem/layouts/onie,tlv-layout.yaml | 115 ++++++++++++++++++ .../devicetree/bindings/nvmem/nvmem.yaml | 8 ++ .../devicetree/bindings/vendor-prefixes.yaml | 2 + 8 files changed, 225 insertions(+), 1 deletion(-) create mode 100644 Documentation/devicetree/bindings/nvmem/layouts/kontron,sl28-vpd.yaml create mode 100644 Documentation/devicetree/bindings/nvmem/layouts/nvmem-layout.yaml create mode 100644 Documentation/devicetree/bindings/nvmem/layouts/onie,tlv-layout.yaml -- 2.34.1
WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com> To: Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzk+dt@kernel.org>, devicetree@vger.kernel.org Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>, <linux-kernel@vger.kernel.org>, Robert Marko <robert.marko@sartura.hr>, Luka Perkov <luka.perkov@sartura.hr>, Thomas Petazzoni <thomas.petazzoni@bootlin.com>, Michael Walle <michael@walle.cc>, <linux-arm-kernel@lists.infradead.org>, Bartosz Golaszewski <brgl@bgdev.pl>, Christian Eggers <ceggers@arri.de>, Cory Tusar <cory.tusar@pid1solutions.com>, Miquel Raynal <miquel.raynal@bootlin.com> Subject: [PATCH v3 0/6] Bindings for NVMEM layouts Date: Fri, 4 Nov 2022 17:38:27 +0100 [thread overview] Message-ID: <20221104163833.1289857-1-miquel.raynal@bootlin.com> (raw) Hello, A month ago, Michael was sending a new iteration of his series bringing nvmem layout support. The idea is: we currently can produce nvmem cells statically defined on top of nvmem devices (which themselves may be MTD devices sometimes) but in some cases we may need more advanced parsing, which is possible thanks to the introduction of nvmem layout parsers. I am not taking over the entire series but I recently tried to make use of these layouts for the ONIE tlv table layout and Rob (rightfully) pointed out that the description was messy, because of the mix between nvmem devices and nvmem parsers. This was known to Michael which initially argued that it was simpler to handle like that. So here is a new proposal for the bindings which is described in details within "dt-bindings: nvmem: Introduce the nvmem-layout container". The idea to avoid mixing different node contents is to use a container node when relevant (suggested by Rob) which I named nvmem-layout. This container will have a compatible that describes the parser (plus possible additional properties). Michael, I have a few fixup! patches which apply directly to your former series in order to support this additional container. I propose we first settle the bindings (including the two direct use cases as examples) and once merged, we can move forward and respin both the nvmem series + the layout drivers. # Original series (v2) from Michael Link: https://lore.kernel.org/linux-arm-kernel/20220921115813.208ff789@xps-13/T/#mb97d5376647ff3e686b9c55e3d5e0dc80879e84a Cheers, Miquèl Michael Walle (1): dt-bindings: nvmem: add YAML schema for the sl28 vpd layout Miquel Raynal (5): dt-bindings: nvmem: Fix example dt-bindings: nvmem: Introduce the nvmem-layout container dt-bindings: eeprom: Inherit from nvmem.yaml dt-bindings: vendor-prefixes: Add ONIE dt-bindings: nvmem: add YAML schema for the ONIE tlv layout .../devicetree/bindings/eeprom/at24.yaml | 5 +- .../devicetree/bindings/eeprom/at25.yaml | 1 + .../bindings/eeprom/microchip,93lc46b.yaml | 1 + .../nvmem/layouts/kontron,sl28-vpd.yaml | 60 +++++++++ .../bindings/nvmem/layouts/nvmem-layout.yaml | 34 ++++++ .../nvmem/layouts/onie,tlv-layout.yaml | 115 ++++++++++++++++++ .../devicetree/bindings/nvmem/nvmem.yaml | 8 ++ .../devicetree/bindings/vendor-prefixes.yaml | 2 + 8 files changed, 225 insertions(+), 1 deletion(-) create mode 100644 Documentation/devicetree/bindings/nvmem/layouts/kontron,sl28-vpd.yaml create mode 100644 Documentation/devicetree/bindings/nvmem/layouts/nvmem-layout.yaml create mode 100644 Documentation/devicetree/bindings/nvmem/layouts/onie,tlv-layout.yaml -- 2.34.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-11-04 16:39 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-04 16:38 Miquel Raynal [this message] 2022-11-04 16:38 ` [PATCH v3 0/6] Bindings for NVMEM layouts Miquel Raynal 2022-11-04 16:38 ` [PATCH v3 1/6] dt-bindings: nvmem: Fix example Miquel Raynal 2022-11-04 16:38 ` Miquel Raynal 2022-11-10 3:51 ` Rob Herring 2022-11-10 3:51 ` Rob Herring 2022-11-11 16:47 ` Srinivas Kandagatla 2022-11-11 16:47 ` Srinivas Kandagatla 2022-11-04 16:38 ` [PATCH v3 2/6] dt-bindings: nvmem: Introduce the nvmem-layout container Miquel Raynal 2022-11-04 16:38 ` Miquel Raynal 2022-11-04 16:38 ` [PATCH v3 3/6] dt-bindings: eeprom: Inherit from nvmem.yaml Miquel Raynal 2022-11-04 16:38 ` Miquel Raynal 2022-11-04 16:38 ` [PATCH v3 4/6] dt-bindings: nvmem: add YAML schema for the sl28 vpd layout Miquel Raynal 2022-11-04 16:38 ` Miquel Raynal 2022-11-10 13:49 ` Rob Herring 2022-11-10 13:49 ` Rob Herring 2022-11-10 17:38 ` Miquel Raynal 2022-11-10 17:38 ` Miquel Raynal 2022-11-10 19:31 ` Rob Herring 2022-11-10 19:31 ` Rob Herring 2022-11-04 16:38 ` [PATCH v3 5/6] dt-bindings: vendor-prefixes: Add ONIE Miquel Raynal 2022-11-04 16:38 ` Miquel Raynal 2022-11-04 16:38 ` [PATCH v3 6/6] dt-bindings: nvmem: add YAML schema for the ONIE tlv layout Miquel Raynal 2022-11-04 16:38 ` Miquel Raynal 2022-11-10 4:00 ` Rob Herring 2022-11-10 4:00 ` Rob Herring 2022-11-10 8:50 ` Miquel Raynal 2022-11-10 8:50 ` Miquel Raynal 2022-11-10 14:05 ` Rob Herring 2022-11-10 14:05 ` Rob Herring 2022-11-10 17:43 ` Miquel Raynal 2022-11-10 17:43 ` Miquel Raynal 2022-11-10 19:47 ` Rob Herring 2022-11-10 19:47 ` Rob Herring
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=20221104163833.1289857-1-miquel.raynal@bootlin.com \ --to=miquel.raynal@bootlin.com \ --cc=brgl@bgdev.pl \ --cc=ceggers@arri.de \ --cc=cory.tusar@pid1solutions.com \ --cc=devicetree@vger.kernel.org \ --cc=krzk+dt@kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=luka.perkov@sartura.hr \ --cc=michael@walle.cc \ --cc=robert.marko@sartura.hr \ --cc=robh+dt@kernel.org \ --cc=srinivas.kandagatla@linaro.org \ --cc=thomas.petazzoni@bootlin.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: linkBe 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.