From: Vincent Whitchurch <vincent.whitchurch@axis.com>
To: <vigneshr@ti.com>, <richard@nod.at>, <miquel.raynal@bootlin.com>,
<joern@lazybastard.org>
Cc: <kernel@axis.com>, <linux-kernel@vger.kernel.org>,
<linux-mtd@lists.infradead.org>, <devicetree@vger.kernel.org>,
<frowand.list@gmail.com>, <krzysztof.kozlowski@canonical.com>,
<robh+dt@kernel.org>,
Vincent Whitchurch <vincent.whitchurch@axis.com>
Subject: [PATCH 0/4] mtd: phram improvements
Date: Mon, 7 Mar 2022 15:15:45 +0100 [thread overview]
Message-ID: <20220307141549.2732179-1-vincent.whitchurch@axis.com> (raw)
The phram driver in the MTD subsystem can be used to allow the kernel to use an
MTD or (via mtdblock) a block device in RAM (with the contents loaded by a
bootloader for example). This series has some improvements to make it more
usable by adding device tree support and to significantly improve its
performance by using cached mappings when possible.
Vincent Whitchurch (4):
mtd: core: Check devicetree alias for index
dt-bindings: reserved-memory: Add phram
mtd: phram: Allow probing via reserved-memory
mtd: phram: Allow cached mappings
.../bindings/reserved-memory/phram.yaml | 45 +++++++++++
drivers/mtd/devices/phram.c | 78 +++++++++++++++++--
drivers/mtd/mtdcore.c | 11 ++-
drivers/of/platform.c | 1 +
4 files changed, 127 insertions(+), 8 deletions(-)
create mode 100644 Documentation/devicetree/bindings/reserved-memory/phram.yaml
--
2.34.1
next reply other threads:[~2022-03-07 14:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 14:15 Vincent Whitchurch [this message]
2022-03-07 14:15 ` [PATCH 1/4] mtd: core: Check devicetree alias for index Vincent Whitchurch
2022-03-07 14:15 ` [PATCH 2/4] dt-bindings: reserved-memory: Add phram Vincent Whitchurch
2022-03-10 20:58 ` Rob Herring
2022-03-11 10:13 ` Vincent Whitchurch
2022-03-07 14:15 ` [PATCH 3/4] mtd: phram: Allow probing via reserved-memory Vincent Whitchurch
2022-03-07 14:15 ` [PATCH 4/4] mtd: phram: Allow cached mappings Vincent Whitchurch
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=20220307141549.2732179-1-vincent.whitchurch@axis.com \
--to=vincent.whitchurch@axis.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=joern@lazybastard.org \
--cc=kernel@axis.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--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
all inboxes | Powered by JetHome®