From: Kevin Hilman <khilman@baylibre.com>
To: Carlo Caione <ccaione@baylibre.com>, srinivas.kandagatla@linaro.org,
Cc: devicetree@vger.kernel.org, narmstrong@baylibre.com,
Carlo Caione <ccaione@baylibre.com>,
robh+dt@kernel.org, linux-amlogic@lists.infradead.org,
tglx@linutronix.de, linux-arm-kernel@lists.infradead.org,
jbrunet@baylibre.com
Subject: Re: [PATCH v2 0/4] Rework secure-monitor driver
Date: Mon, 05 Aug 2019 14:34:15 -0700 [thread overview]
Message-ID: <7hftmfguug.fsf@baylibre.com> (raw)
In-Reply-To: <20190731082339.20163-1-ccaione@baylibre.com>
Srinivas,
Carlo Caione <ccaione@baylibre.com> writes:
> 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.
With your ack on the nvmem bindings and nvmem part of patch 4/4, I can
take the series take the rest of this series through my tree for Amlogic
SoCs.
Kevin
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Carlo Caione <ccaione@baylibre.com>, srinivas.kandagatla@linaro.org,
Cc: devicetree@vger.kernel.org, narmstrong@baylibre.com,
Carlo Caione <ccaione@baylibre.com>,
robh+dt@kernel.org, linux-amlogic@lists.infradead.org,
tglx@linutronix.de, linux-arm-kernel@lists.infradead.org,
jbrunet@baylibre.com
Subject: Re: [PATCH v2 0/4] Rework secure-monitor driver
Date: Mon, 05 Aug 2019 14:34:15 -0700 [thread overview]
Message-ID: <7hftmfguug.fsf@baylibre.com> (raw)
In-Reply-To: <20190731082339.20163-1-ccaione@baylibre.com>
Srinivas,
Carlo Caione <ccaione@baylibre.com> writes:
> 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.
With your ack on the nvmem bindings and nvmem part of patch 4/4, I can
take the series take the rest of this series through my tree for Amlogic
SoCs.
Kevin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: srinivas.kandagatla@linaro.org
Cc: devicetree@vger.kernel.org, narmstrong@baylibre.com,
Carlo Caione <ccaione@baylibre.com>,
robh+dt@kernel.org, linux-amlogic@lists.infradead.org,
tglx@linutronix.de, linux-arm-kernel@lists.infradead.org,
jbrunet@baylibre.com
Subject: Re: [PATCH v2 0/4] Rework secure-monitor driver
Date: Mon, 05 Aug 2019 14:34:15 -0700 [thread overview]
Message-ID: <7hftmfguug.fsf@baylibre.com> (raw)
In-Reply-To: <20190731082339.20163-1-ccaione@baylibre.com>
Srinivas,
Carlo Caione <ccaione@baylibre.com> writes:
> 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.
With your ack on the nvmem bindings and nvmem part of patch 4/4, I can
take the series take the rest of this series through my tree for Amlogic
SoCs.
Kevin
next prev parent reply other threads:[~2019-08-05 21:34 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 8:23 [PATCH v2 0/4] Rework secure-monitor driver Carlo Caione
2019-07-31 8:23 ` Carlo Caione
2019-07-31 8:23 ` Carlo Caione
2019-07-31 8:23 ` [PATCH v2 1/4] firmware: meson_sm: Mark chip struct as static const Carlo Caione
2019-07-31 8:23 ` Carlo Caione
2019-07-31 8:23 ` Carlo Caione
2019-07-31 8:23 ` [PATCH v2 2/4] nvmem: meson-efuse: bindings: Add secure-monitor phandle Carlo Caione
2019-07-31 8:23 ` Carlo Caione
2019-07-31 8:23 ` Carlo Caione
2019-08-06 8:25 ` Jerome Brunet
2019-08-06 8:25 ` Jerome Brunet
2019-08-06 8:25 ` Jerome Brunet
2019-08-15 21:20 ` Kevin Hilman
2019-08-15 21:20 ` Kevin Hilman
2019-08-15 21:20 ` Kevin Hilman
2019-08-21 18:14 ` Rob Herring
2019-08-21 18:14 ` Rob Herring
2019-08-21 18:14 ` Rob Herring
2019-08-22 8:36 ` Carlo Caione
2019-08-22 8:36 ` Carlo Caione
2019-08-22 8:36 ` Carlo Caione
2019-08-22 8:59 ` Jerome Brunet
2019-08-22 8:59 ` Jerome Brunet
2019-08-22 8:59 ` Jerome Brunet
2019-07-31 8:23 ` [PATCH v2 3/4] arm64: dts: meson: Link nvmem and secure-monitor nodes Carlo Caione
2019-07-31 8:23 ` Carlo Caione
2019-07-31 8:23 ` Carlo Caione
2019-08-06 8:26 ` Jerome Brunet
2019-08-06 8:26 ` Jerome Brunet
2019-08-06 8:26 ` Jerome Brunet
2019-07-31 8:23 ` [PATCH v2 4/4] firmware: meson_sm: Rework driver as a proper platform driver Carlo Caione
2019-07-31 8:23 ` Carlo Caione
2019-07-31 8:23 ` Carlo Caione
2019-08-06 8:23 ` Srinivas Kandagatla
2019-08-06 8:23 ` Srinivas Kandagatla
2019-08-06 8:23 ` Srinivas Kandagatla
2019-08-05 21:34 ` Kevin Hilman [this message]
2019-08-05 21:34 ` [PATCH v2 0/4] Rework secure-monitor driver Kevin Hilman
2019-08-05 21:34 ` Kevin Hilman
2019-08-06 8:25 ` Srinivas Kandagatla
2019-08-06 8:25 ` Srinivas Kandagatla
2019-08-06 8:25 ` Srinivas Kandagatla
2019-08-09 21:42 ` Kevin Hilman
2019-08-09 21:42 ` Kevin Hilman
2019-08-09 21:42 ` Kevin Hilman
2019-09-24 18:45 ` Kevin Hilman
2019-09-24 18:45 ` Kevin Hilman
2019-09-24 18:45 ` Kevin Hilman
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=7hftmfguug.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=ccaione@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@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 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.