All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: Michael Walle <michael@walle.cc>,
	srinivas.kandagatla@linaro.org, gregkh@linuxfoundation.org,
	rafal@milecki.pl, linux-kernel@vger.kernel.org,
	kernel@pengutronix.de
Subject: Re: [RFC PATCH] nvmem: core: add sysfs cell write support
Date: Tue, 20 Feb 2024 11:07:01 +0100	[thread overview]
Message-ID: <20240220110701.5ac88fed@xps-13> (raw)
In-Reply-To: <20240220095038.2betrguygehvwodz@pengutronix.de>

Hi Marco,

> > > > Regarding UBI(FS) I'm not sure if this is required at all since you have
> > > > an filesystem. IMHO nvmem-cells are very lowelevel and are not made for
> > > > filesystem backed backends.  
> > 
> > I'm really talking about UBI, not UBIFS. UBI is just like MTD but
> > handles wear leveling. There is a pending series for enabling nvmem
> > cells on top of UBI.  
> 
> Cells on-top of a wear leveling device? Interesting, the cell-api is
> very lowlevel which means the specified cell will be at the exact same
> place on the hardware device as specified in the dts. How do you know
> that with wear leveling underneath the cell-api?

https://lore.kernel.org/lkml/cover.1702952891.git.daniel@makrotopia.org/

I haven't tested it though.

Thanks,
Miquèl

  reply	other threads:[~2024-02-20 10:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-15 21:14 [RFC PATCH] nvmem: core: add sysfs cell write support Marco Felsch
2024-02-16  8:47 ` Michael Walle
2024-02-16 10:07   ` Marco Felsch
2024-02-19 11:04     ` Miquel Raynal
2024-02-19 11:53       ` Marco Felsch
2024-02-19 13:26         ` Michael Walle
2024-02-20  9:18           ` Miquel Raynal
2024-02-20  9:50             ` Marco Felsch
2024-02-20 10:07               ` Miquel Raynal [this message]
2024-02-20 10:16               ` Michael Walle

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=20240220110701.5ac88fed@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.felsch@pengutronix.de \
    --cc=michael@walle.cc \
    --cc=rafal@milecki.pl \
    --cc=srinivas.kandagatla@linaro.org \
    /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.