All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: POPESCU Catalin <catalin.popescu@leica-geosystems.com>
Cc: "srinivas.kandagatla@linaro.org" <srinivas.kandagatla@linaro.org>,
	"michael@walle.cc" <michael@walle.cc>,
	"rafal@milecki.pl" <rafal@milecki.pl>,
	"robh@kernel.org" <robh@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	GEO-CHHER-bsp-development
	<bsp-development.geo@leica-geosystems.com>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"luca.ceresoli@bootlin.com" <luca.ceresoli@bootlin.com>
Subject: Re: [PATCH] nvmem: core: add fixed-layout declaration
Date: Tue, 30 Jan 2024 16:00:21 +0100	[thread overview]
Message-ID: <20240130160021.70ddef92@xps-13> (raw)
In-Reply-To: <d568b3e2-0305-4041-9f6a-8375b5c497b2@leica-geosystems.com>

Hi Catalin,

catalin.popescu@leica-geosystems.com wrote on Mon, 29 Jan 2024 15:29:31
+0000:

> Hi Miquel,
> 
> Now, that "specific" layouts are considered like drivers and rely on 
> NVMEM_LAYOUTS to populate the nvmem cells (layouts.c), I guess it's not 
> possible anymore to consider "fixed-layout" as a normal layout that 
> should be treated the same way than any layout. Unless, we move 
> "fixed-layout" under drivers/nvmem/layouts.

That would be the relevant approach, yes.

> But, this also means that 
> "fixed-layout" won't be supported anymore out-of-the-box (by nvmem core) 

That would not be acceptable indeed.

> and will require additional kernel configuration change.

This would presumably be manageable however.

No pressure if you don't feel like you could carry that task, it's not
longer trivial.

Thanks,
Miquèl

      reply	other threads:[~2024-01-30 15:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-11 15:28 [PATCH] nvmem: core: add fixed-layout declaration Catalin Popescu
2024-01-11 15:41 ` Miquel Raynal
2024-01-29 15:29   ` POPESCU Catalin
2024-01-30 15:00     ` Miquel Raynal [this message]

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=20240130160021.70ddef92@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=bsp-development.geo@leica-geosystems.com \
    --cc=catalin.popescu@leica-geosystems.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.ceresoli@bootlin.com \
    --cc=michael@walle.cc \
    --cc=rafal@milecki.pl \
    --cc=robh@kernel.org \
    --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.