All of lore.kernel.org
 help / color / mirror / Atom feed
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: Robert Marko <robert.marko@sartura.hr>,
	Luka Perkov <luka.perkov@sartura.hr>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Michael Walle <michael@walle.cc>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	<linux-kernel@vger.kernel.org>,
	Miquel Raynal <miquel.raynal@bootlin.com>
Subject: [PATCH v4 0/5] Bindings for NVMEM layouts
Date: Mon, 14 Nov 2022 09:56:54 +0100	[thread overview]
Message-ID: <20221114085659.847611-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

Changes since v3:
* Added 'select: false' into the sl28 vpd layout
* Added 'type: objec' and 'additionalProperties: false' to each and
  every nvmem-cell that could be produced by the onie layout to properly
  describe all the subnodes.

Michael Walle (1):
  dt-bindings: nvmem: add YAML schema for the sl28 vpd layout

Miquel Raynal (4):
  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       |  62 ++++++++
 .../bindings/nvmem/layouts/nvmem-layout.yaml  |  34 ++++
 .../nvmem/layouts/onie,tlv-layout.yaml        | 147 ++++++++++++++++++
 .../devicetree/bindings/nvmem/nvmem.yaml      |   7 +
 .../devicetree/bindings/vendor-prefixes.yaml  |   2 +
 8 files changed, 258 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


             reply	other threads:[~2022-11-14  8:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14  8:56 Miquel Raynal [this message]
2022-11-14  8:56 ` [PATCH v4 1/5] dt-bindings: nvmem: Introduce the nvmem-layout container Miquel Raynal
2022-11-16 20:52   ` Rob Herring
2022-11-14  8:56 ` [PATCH v4 2/5] dt-bindings: eeprom: Inherit from nvmem.yaml Miquel Raynal
2022-11-14 12:21   ` Bartosz Golaszewski
2022-11-16 20:52   ` Rob Herring
2022-11-14  8:56 ` [PATCH v4 3/5] dt-bindings: nvmem: add YAML schema for the sl28 vpd layout Miquel Raynal
2022-11-16 20:52   ` Rob Herring
2022-11-16 21:28     ` Miquel Raynal
2022-11-16 22:44       ` Srinivas Kandagatla
2022-11-14  8:56 ` [PATCH v4 4/5] dt-bindings: vendor-prefixes: Add ONIE Miquel Raynal
2022-11-14  8:56 ` [PATCH v4 5/5] dt-bindings: nvmem: add YAML schema for the ONIE tlv layout Miquel Raynal
2022-11-16 20:54   ` 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=20221114085659.847611-1-miquel.raynal@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=brgl@bgdev.pl \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.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: 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.