From: Krzysztof Kozlowski <krzk@kernel.org>
To: Vabhav Sharma <vabhav.sharma@nxp.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Franck Lenormand <franck.lenormand@nxp.com>,
Aisheng Dong <aisheng.dong@nxp.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>, Peng Fan <peng.fan@nxp.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Varun Sethi <V.Sethi@nxp.com>,
Silvano Di Ninno <silvano.dininno@nxp.com>,
Pankaj Gupta <pankaj.gupta@nxp.com>, Frank Li <frank.li@nxp.com>,
Daniel Baluta <daniel.baluta@nxp.com>
Subject: Re: [EXT] Re: [PATCH 1/4] dt-bindings: firmware: secvio: Add device tree bindings
Date: Fri, 7 Jun 2024 09:07:45 +0200 [thread overview]
Message-ID: <1486a1b6-4119-4121-b6df-3da21d06add7@kernel.org> (raw)
In-Reply-To: <AS1PR04MB9358A2457AF05553457DE9B0F3FB2@AS1PR04MB9358.eurprd04.prod.outlook.com>
On 07/06/2024 06:58, Vabhav Sharma wrote:
>>
>> Missing SoC compatibles.
> Ok, I will use fsl,imx8dxl-sc-secvio
>>
>> So no, that's just abuse of DT to instantiate driver.
>>
>> NAK. Drop the binding.
> I will detail the dt binding to describe the real hardware
Still looks like way just to instantiate driver. Why it cannot be part
of existing firmware SCU node?
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-06-07 7:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 0:45 [PATCH 0/4] soc: imx: secvio: Add secvio support Vabhav Sharma
2024-05-09 0:45 ` [PATCH 1/4] dt-bindings: firmware: secvio: Add device tree bindings Vabhav Sharma
2024-05-09 3:06 ` Frank Li
2024-05-09 5:54 ` Krzysztof Kozlowski
2024-06-07 5:00 ` [EXT] " Vabhav Sharma
2024-06-07 5:08 ` Vabhav Sharma
2024-05-09 5:53 ` Krzysztof Kozlowski
2024-06-07 4:58 ` [EXT] " Vabhav Sharma
2024-06-07 7:07 ` Krzysztof Kozlowski [this message]
2024-06-12 7:20 ` Aisheng Dong
2024-06-13 6:13 ` Krzysztof Kozlowski
2024-06-13 8:48 ` Aisheng Dong
2024-06-16 7:33 ` Krzysztof Kozlowski
2024-06-17 10:11 ` Aisheng Dong
2024-06-17 12:11 ` Krzysztof Kozlowski
2024-05-09 0:45 ` [PATCH 2/4] firmware: imx: Add SC APIs required for secvio module Vabhav Sharma
2024-05-09 0:45 ` [PATCH 3/4] soc: imx: secvio: Add support for SNVS secvio and tamper via SCFW Vabhav Sharma
2024-05-09 0:45 ` [PATCH 4/4] arm64: dts: imx8q: Add node for Security Violation Vabhav Sharma
2024-05-09 5:51 ` [PATCH 0/4] soc: imx: secvio: Add secvio support Krzysztof Kozlowski
2024-06-07 4:52 ` [EXT] " Vabhav Sharma
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=1486a1b6-4119-4121-b6df-3da21d06add7@kernel.org \
--to=krzk@kernel.org \
--cc=V.Sethi@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=franck.lenormand@nxp.com \
--cc=frank.li@nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.gupta@nxp.com \
--cc=peng.fan@nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=silvano.dininno@nxp.com \
--cc=vabhav.sharma@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).