From: Carlo Caione <ccaione@baylibre.com>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, narmstrong@baylibre.com,
khilman@baylibre.com, srinivas.kandagatla@linaro.org,
linux-amlogic@lists.infradead.org, tglx@linutronix.de,
linux-arm-kernel@lists.infradead.org, jbrunet@baylibre.com
Subject: Re: [PATCH v2 2/4] nvmem: meson-efuse: bindings: Add secure-monitor phandle
Date: Thu, 22 Aug 2019 09:36:33 +0100 [thread overview]
Message-ID: <7c5307fe-2762-eefd-5c65-4ff7c4bd2f5d@baylibre.com> (raw)
In-Reply-To: <20190821181458.GA2886@bogus>
On 21/08/2019 19:14, Rob Herring wrote:
> On Wed, Jul 31, 2019 at 09:23:37AM +0100, Carlo Caione wrote:
> There's no need for 'secure-monitor' anyways. Just do
> 'of_find_compatible_node(NULL, NULL, "amlogic,meson-gxbb-sm")' or search
> for the driver directly. It's not like there's more than one secure
> monitor...
How is hardcoding the secure-monitor directly into the efuse driver
better than having it referenced in the DT?
Yes, there is one single secure monitor but (even if this is not
currently the case) several drivers can use it making the secure-monitor
a resource to be potentially used by several devices.
--
Carlo Caione
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-08-22 8:36 UTC|newest]
Thread overview: 16+ 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 ` [PATCH v2 1/4] firmware: meson_sm: Mark chip struct as static const Carlo Caione
2019-07-31 8:23 ` [PATCH v2 2/4] nvmem: meson-efuse: bindings: Add secure-monitor phandle Carlo Caione
2019-08-06 8:25 ` Jerome Brunet
2019-08-15 21:20 ` Kevin Hilman
2019-08-21 18:14 ` Rob Herring
2019-08-22 8:36 ` Carlo Caione [this message]
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-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-08-06 8:23 ` Srinivas Kandagatla
2019-08-05 21:34 ` [PATCH v2 0/4] Rework secure-monitor driver Kevin Hilman
2019-08-06 8:25 ` Srinivas Kandagatla
2019-08-09 21:42 ` 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=7c5307fe-2762-eefd-5c65-4ff7c4bd2f5d@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@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).