From: Rob Herring <robh@kernel.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Srinivas Kandagatla" <srinivas.kandagatla@linaro.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Michael Walle" <michael@walle.cc>,
"Miquel Raynal" <miquel.raynal@bootlin.com>,
linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, u-boot@lists.denx.de,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH V3 1/6] dt-bindings: nvmem: layouts: add U-Boot environment variables layout
Date: Wed, 3 Jan 2024 17:11:29 -0700 [thread overview]
Message-ID: <20240104001129.GA2045237-robh@kernel.org> (raw)
In-Reply-To: <20231221173421.13737-1-zajec5@gmail.com>
On Thu, Dec 21, 2023 at 06:34:16PM +0100, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> U-Boot env data is a way of storing firmware variables. It's a format
> that can be used of top of various storage devices. Its binding should
> be an NVMEM layout instead of a standalone device.
>
> This patch adds layout binding which allows using it on top of MTD NVMEM
> device as well as any other. At the same time it deprecates the old
> combined binding.
I don't understand the issue. From a DT perspective, there isn't. A
partition is not a device, but is describing the layout of storage
already.
Rob
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Srinivas Kandagatla" <srinivas.kandagatla@linaro.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Michael Walle" <michael@walle.cc>,
"Miquel Raynal" <miquel.raynal@bootlin.com>,
linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, u-boot@lists.denx.de,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH V3 1/6] dt-bindings: nvmem: layouts: add U-Boot environment variables layout
Date: Wed, 3 Jan 2024 17:11:29 -0700 [thread overview]
Message-ID: <20240104001129.GA2045237-robh@kernel.org> (raw)
In-Reply-To: <20231221173421.13737-1-zajec5@gmail.com>
On Thu, Dec 21, 2023 at 06:34:16PM +0100, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> U-Boot env data is a way of storing firmware variables. It's a format
> that can be used of top of various storage devices. Its binding should
> be an NVMEM layout instead of a standalone device.
>
> This patch adds layout binding which allows using it on top of MTD NVMEM
> device as well as any other. At the same time it deprecates the old
> combined binding.
I don't understand the issue. From a DT perspective, there isn't. A
partition is not a device, but is describing the layout of storage
already.
Rob
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Srinivas Kandagatla" <srinivas.kandagatla@linaro.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Michael Walle" <michael@walle.cc>,
"Miquel Raynal" <miquel.raynal@bootlin.com>,
linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, u-boot@lists.denx.de,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH V3 1/6] dt-bindings: nvmem: layouts: add U-Boot environment variables layout
Date: Wed, 3 Jan 2024 17:11:29 -0700 [thread overview]
Message-ID: <20240104001129.GA2045237-robh@kernel.org> (raw)
In-Reply-To: <20231221173421.13737-1-zajec5@gmail.com>
On Thu, Dec 21, 2023 at 06:34:16PM +0100, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> U-Boot env data is a way of storing firmware variables. It's a format
> that can be used of top of various storage devices. Its binding should
> be an NVMEM layout instead of a standalone device.
>
> This patch adds layout binding which allows using it on top of MTD NVMEM
> device as well as any other. At the same time it deprecates the old
> combined binding.
I don't understand the issue. From a DT perspective, there isn't. A
partition is not a device, but is describing the layout of storage
already.
Rob
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-01-04 0:11 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 17:34 [PATCH V3 1/6] dt-bindings: nvmem: layouts: add U-Boot environment variables layout Rafał Miłecki
2023-12-21 17:34 ` Rafał Miłecki
2023-12-21 17:34 ` Rafał Miłecki
2023-12-21 17:34 ` [PATCH V3 2/6] nvmem: core: add nvmem_dev_size() helper Rafał Miłecki
2023-12-21 17:34 ` Rafał Miłecki
2023-12-21 17:34 ` Rafał Miłecki
2023-12-21 17:34 ` [PATCH V3 3/6] nvmem: u-boot-env: use nvmem_add_one_cell() nvmem subsystem helper Rafał Miłecki
2023-12-21 17:34 ` Rafał Miłecki
2023-12-21 17:34 ` Rafał Miłecki
2023-12-21 17:34 ` [PATCH V3 4/6] nvmem: u-boot-env: use nvmem device helpers Rafał Miłecki
2023-12-21 17:34 ` Rafał Miłecki
2023-12-21 17:34 ` Rafał Miłecki
2023-12-21 17:34 ` [PATCH V3 5/6] nvmem: u-boot-env: improve coding style Rafał Miłecki
2023-12-21 17:34 ` Rafał Miłecki
2023-12-21 17:34 ` Rafał Miłecki
2023-12-21 17:34 ` [PATCH V3 6/6] nvmem: layouts: add U-Boot env layout Rafał Miłecki
2023-12-21 17:34 ` Rafał Miłecki
2023-12-21 17:34 ` Rafał Miłecki
2024-01-04 15:46 ` Greg Kroah-Hartman
2024-01-04 15:46 ` Greg Kroah-Hartman
2024-01-04 15:46 ` Greg Kroah-Hartman
2024-01-04 0:11 ` Rob Herring [this message]
2024-01-04 0:11 ` [PATCH V3 1/6] dt-bindings: nvmem: layouts: add U-Boot environment variables layout Rob Herring
2024-01-04 0:11 ` Rob Herring
2024-01-04 7:58 ` Miquel Raynal
2024-01-04 7:58 ` Miquel Raynal
2024-01-04 7:58 ` Miquel Raynal
2024-01-04 9:10 ` Rafał Miłecki
2024-01-04 9:10 ` Rafał Miłecki
2024-01-04 9:10 ` Rafał Miłecki
2024-01-15 17:09 ` Rob Herring
2024-01-15 17:09 ` Rob Herring
2024-01-15 17:09 ` Rob Herring
2024-01-15 22:10 ` Miquel Raynal
2024-01-15 22:10 ` Miquel Raynal
2024-01-15 22:10 ` Miquel Raynal
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=20240104001129.GA2045237-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=michael@walle.cc \
--cc=miquel.raynal@bootlin.com \
--cc=rafal@milecki.pl \
--cc=srinivas.kandagatla@linaro.org \
--cc=u-boot@lists.denx.de \
--cc=zajec5@gmail.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.