From: Carlo Caione <ccaione@baylibre.com>
To: srinivas.kandagatla@linaro.org, khilman@baylibre.com,
narmstrong@baylibre.com, robh+dt@kernel.org, tglx@linutronix.de,
jbrunet@baylibre.com, linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, devicetree@vger.kernel.org
Cc: Carlo Caione <ccaione@baylibre.com>
Subject: [PATCH 0/5] Rework secure-monitor driver
Date: Mon, 29 Jul 2019 19:39:36 +0100 [thread overview]
Message-ID: <20190729183941.18164-1-ccaione@baylibre.com> (raw)
The secure-monitor driver is currently in really bad shape, not my
proudest piece of code (thanks Jerome for pointing that out ;). I tried
to rework it a bit to make it a bit more tolerable.
I needed to change a bit the APIs and consequently adapt the only user
we have, that is the nvmem/efuses driver. To not break bisectability I
added one single commit to change both the drivers.
The remaining commits are cosmetic and DTS/docs fixes.
Carlo Caione (5):
nvmem: meson-efuse: Move data to a container struct
firmware: meson_sm: Mark chip struct as static const
nvmem: meson-efuse: bindings: Add secure-monitor phandle
firmware: meson_sm: Rework driver as a proper platform driver
arm64: dts: meson: Link nvmem and secure-monitor nodes
.../bindings/nvmem/amlogic-efuse.txt | 6 ++
arch/arm64/boot/dts/amlogic/meson-axg.dtsi | 1 +
arch/arm64/boot/dts/amlogic/meson-g12a.dtsi | 1 +
drivers/firmware/meson/meson_sm.c | 96 +++++++++++++------
drivers/nvmem/meson-efuse.c | 70 +++++++++-----
include/linux/firmware/meson/meson_sm.h | 15 +--
6 files changed, 128 insertions(+), 61 deletions(-)
--
2.20.1
next reply other threads:[~2019-07-29 18:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 18:39 Carlo Caione [this message]
2019-07-29 18:39 ` [PATCH 1/5] nvmem: meson-efuse: Move data to a container struct Carlo Caione
2019-07-30 9:04 ` Jerome Brunet
2019-07-30 9:29 ` Carlo Caione
2019-07-29 18:39 ` [PATCH 2/5] firmware: meson_sm: Mark chip struct as static const Carlo Caione
2019-07-30 9:05 ` Jerome Brunet
2019-07-29 18:39 ` [PATCH 3/5] nvmem: meson-efuse: bindings: Add secure-monitor phandle Carlo Caione
2019-07-29 18:39 ` [PATCH 4/5] firmware: meson_sm: Rework driver as a proper platform driver Carlo Caione
2019-07-30 9:18 ` Jerome Brunet
2019-07-29 18:39 ` [PATCH 5/5] arm64: dts: meson: Link nvmem and secure-monitor nodes Carlo Caione
2019-07-30 9:23 ` Jerome Brunet
2019-07-30 9:36 ` Carlo Caione
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=20190729183941.18164-1-ccaione@baylibre.com \
--to=ccaione@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=narmstrong@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=tglx@linutronix.de \
/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).