From: Shawn Guo <shawnguo@kernel.org>
To: Li Yang <leoyang.li@nxp.com>
Cc: Michael Walle <michael@walle.cc>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, lkml <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Sahil Malhotra <sahil.malhotra@nxp.com>,
Guillaume Tucker <guillaume.tucker@collabora.com>,
"kernelci.org bot" <bot@kernelci.org>
Subject: Re: [PATCH] arm64: dts: ls1028a: fix optee node
Date: Mon, 29 Mar 2021 08:38:15 +0800 [thread overview]
Message-ID: <20210329003814.GC22955@dragon> (raw)
In-Reply-To: <CADRPPNR=xy_oBZFS+hmO1k+uu2ckFyrK9EUP77N3buU5XpuHrw@mail.gmail.com>
On Mon, Mar 22, 2021 at 06:12:06PM -0500, Li Yang wrote:
> On Thu, Mar 18, 2021 at 3:36 AM Michael Walle <michael@walle.cc> wrote:
> >
> > Don't enable the optee node in the SoC include. It is an optional
> > component and actually, if enabled, breaks boards which doesn't have it.
>
> Hi Shawn,
>
> Shall we make this a general rule? I see quite a few SoC dtsi files
> are having the optee node enabled by default.
Yeah, we should probably make it a general rule considering the issue
reported here. I thought that optee driver is smart enough to stop
probing if there is no optee os/firmware support found on given platform.
Shawn
next prev parent reply other threads:[~2021-03-29 0:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 8:34 [PATCH] arm64: dts: ls1028a: fix optee node Michael Walle
2021-03-18 9:20 ` Michael Walle
2021-03-22 23:12 ` Li Yang
2021-03-29 0:38 ` Shawn Guo [this message]
[not found] <DB7PR04MB53222C26DD58E81FEAE4A27982659@DB7PR04MB5322.eurprd04.prod.outlook.com>
2021-03-22 11:39 ` Michael Walle
[not found] <DB7PR04MB53223015C17DCD6DBCCACE5382659@DB7PR04MB5322.eurprd04.prod.outlook.com>
2021-03-22 13:35 ` Michael Walle
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=20210329003814.GC22955@dragon \
--to=shawnguo@kernel.org \
--cc=bot@kernelci.org \
--cc=devicetree@vger.kernel.org \
--cc=guillaume.tucker@collabora.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
--cc=robh+dt@kernel.org \
--cc=sahil.malhotra@nxp.com \
/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).