From: "Rafał Miłecki" <zajec5@gmail.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: "Matthias Brugger" <matthias.bgg@gmail.com>,
"Kunihiko Hayashi" <hayashi.kunihiko@socionext.com>,
"Masami Hiramatsu" <mhiramat@kernel.org>,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, "Rafał Miłecki" <rafal@milecki.pl>
Subject: [PATCH 0/4] nvmem: add and use generic MMIO NVMEM
Date: Wed, 1 Feb 2023 07:47:13 +0100 [thread overview]
Message-ID: <20230201064717.18410-1-zajec5@gmail.com> (raw)
From: Rafał Miłecki <rafal@milecki.pl>
MMIO accessible NVMEM devices should be simple enough to allow using a
single binding & driver for them.
I already replaced two existing drivers. With NVMEM layouts introduced I
can also replace Broadcom's NVRAM driver but that work depends on my
pending U-Boot patchset (it provides required helpers).
Rafał Miłecki (4):
dt-bindings: nvmem: mmio: new binding for MMIO accessible NVMEM
devices
nvmem: add generic driver for devices with MMIO access
nvmem: mtk-efuse: replace driver with a generic MMIO one
nvmem: uniphier-efuse: replace driver with a generic MMIO one
.../devicetree/bindings/nvmem/mmio.yaml | 46 +++++++++
drivers/nvmem/Kconfig | 24 +++--
drivers/nvmem/Makefile | 6 +-
drivers/nvmem/mmio.c | 84 ++++++++++++++++
drivers/nvmem/mtk-efuse.c | 97 -------------------
drivers/nvmem/uniphier-efuse.c | 78 ---------------
6 files changed, 148 insertions(+), 187 deletions(-)
create mode 100644 Documentation/devicetree/bindings/nvmem/mmio.yaml
create mode 100644 drivers/nvmem/mmio.c
delete mode 100644 drivers/nvmem/mtk-efuse.c
delete mode 100644 drivers/nvmem/uniphier-efuse.c
--
2.34.1
next reply other threads:[~2023-02-01 6:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 6:47 Rafał Miłecki [this message]
2023-02-01 6:47 ` [PATCH 1/4] dt-bindings: nvmem: mmio: new binding for MMIO accessible NVMEM devices Rafał Miłecki
2023-02-03 21:06 ` Rob Herring
2023-02-01 6:47 ` [PATCH 2/4] nvmem: add generic driver for devices with MMIO access Rafał Miłecki
2023-02-01 9:41 ` Kunihiko Hayashi
2023-02-01 11:52 ` Srinivas Kandagatla
2023-02-02 9:24 ` AngeloGioacchino Del Regno
2023-02-01 6:47 ` [PATCH 3/4] nvmem: mtk-efuse: replace driver with a generic MMIO one Rafał Miłecki
2023-02-01 8:48 ` Michael Walle
2023-02-01 9:30 ` Rafał Miłecki
2023-02-01 10:46 ` Michael Walle
2023-02-01 11:01 ` Rafał Miłecki
2023-02-01 11:11 ` Michael Walle
2023-02-01 18:54 ` Rob Herring
2023-02-01 20:15 ` Michael Walle
2023-02-02 23:44 ` Rob Herring
2023-02-01 6:47 ` [PATCH 4/4] nvmem: uniphier-efuse: " Rafał Miłecki
2023-02-01 7:50 ` [PATCH 0/4] nvmem: add and use generic MMIO NVMEM Rafał Miłecki
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=20230201064717.18410-1-zajec5@gmail.com \
--to=zajec5@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mhiramat@kernel.org \
--cc=rafal@milecki.pl \
--cc=robh+dt@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 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).