devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Daniel Golle <daniel@makrotopia.org>
Cc: Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 7/7] mtd: ubi: provide NVMEM layer over UBI volumes
Date: Mon, 19 Feb 2024 12:01:56 +0100	[thread overview]
Message-ID: <20240219120156.383a1427@xps-13> (raw)
In-Reply-To: <82ceb13954f7e701bf47c112333e7b15a57fc360.1702952891.git.daniel@makrotopia.org>

Hi Daniel,

daniel@makrotopia.org wrote on Tue, 19 Dec 2023 02:33:48 +0000:

> In an ideal world we would like UBI to be used where ever possible on a
> NAND chip. And with UBI support in ARM Trusted Firmware and U-Boot it
> is possible to achieve an (almost-)all-UBI flash layout. Hence the need
> for a way to also use UBI volumes to store board-level constants, such
> as MAC addresses and calibration data of wireless interfaces.
> 
> Add UBI volume NVMEM driver module exposing UBI volumes as NVMEM
> providers. Allow UBI devices to have a "volumes" firmware subnode with
> volumes which may be compatible with "nvmem-cells".
> Access to UBI volumes via the NVMEM interface at this point is
> read-only, and it is slow, opening and closing the UBI volume for each
> access due to limitations of the NVMEM provider API.

I don't feel qualified enough to review the other patches, however this
one looks good to me.

Thanks,
Miquèl

  reply	other threads:[~2024-02-19 11:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19  2:31 [PATCH v7 0/7] mtd: ubi: allow UBI volumes to provide NVMEM Daniel Golle
2023-12-19  2:32 ` [PATCH v7 1/7] dt-bindings: mtd: add basic bindings for UBI Daniel Golle
2023-12-19  2:32 ` [PATCH v7 2/7] dt-bindings: mtd: ubi-volume: allow UBI volumes to provide NVMEM Daniel Golle
2023-12-19  2:32 ` [PATCH v7 3/7] mtd: ubi: block: use notifier to create ubiblock from parameter Daniel Golle
2023-12-19  2:33 ` [PATCH v7 4/7] mtd: ubi: attach from device tree Daniel Golle
2023-12-19  2:33 ` [PATCH v7 5/7] mtd: ubi: introduce pre-removal notification for UBI volumes Daniel Golle
2023-12-19  2:33 ` [PATCH v7 6/7] mtd: ubi: populate ubi volume fwnode Daniel Golle
2023-12-19  2:33 ` [PATCH v7 7/7] mtd: ubi: provide NVMEM layer over UBI volumes Daniel Golle
2024-02-19 11:01   ` Miquel Raynal [this message]
2024-02-25 22:12     ` Richard Weinberger
2024-02-26  0:05       ` Daniel Golle
2024-03-10 21:17         ` Richard Weinberger
2024-03-11  2:37           ` Daniel Golle
2024-03-19 22:31             ` Richard Weinberger
2024-03-22 15:56               ` Daniel Golle
2024-03-22 16:05                 ` Richard Weinberger
2024-02-12  0:48 ` [PATCH v7 0/7] mtd: ubi: allow UBI volumes to provide NVMEM Daniel Golle

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=20240219120156.383a1427@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=conor+dt@kernel.org \
    --cc=daniel@makrotopia.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    --cc=robh+dt@kernel.org \
    --cc=vigneshr@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).