From: Kevin Hilman <khilman@baylibre.com>
Cc: Jerome Brunet <jbrunet@baylibre.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] arm64: dts: meson: g12a: add secure monitor and efuse
Date: Fri, 15 Mar 2019 13:45:37 -0700 [thread overview]
Message-ID: <7h5zsjc1e6.fsf@baylibre.com> (raw)
In-Reply-To: <20190315134244.14141-1-jbrunet@baylibre.com>
Jerome Brunet <jbrunet@baylibre.com> writes:
> This patchset adds the secure monitor and efuse to the g12a SoC family.
> These are sent together because the secure monitor is required for the
> efuse driver to work properly. This is probably something the bindings
> should show but it was not designed that way when the secure monitor was
> introduced ... something to look at someday.
Queued for v5.2 (branch: v5.2/dt64)
Thanks,
Kevin
prev parent reply other threads:[~2019-03-15 20:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 13:42 [PATCH 0/2] arm64: dts: meson: g12a: add secure monitor and efuse Jerome Brunet
2019-03-15 13:42 ` [PATCH 1/2] arm64: dts: meson: g12a: add secure monitor Jerome Brunet
2019-03-15 13:42 ` [PATCH 2/2] arm64: dts: meson: g12a: add efuse Jerome Brunet
2019-03-15 20:45 ` Kevin Hilman [this message]
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=7h5zsjc1e6.fsf@baylibre.com \
--to=khilman@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=linux-kernel@vger.kernel.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).