linux-kernel - Re: [PATCH v3 2/2] arm64: dts: imx8m: define proper status for caam jr

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <00e083278fb4a8c96fdef564a2183600@walle.cc>
Date:   Fri, 07 Jan 2022 13:05:01 +0100
From:   Michael Walle <michael@...le.cc>
To:     Lucas Stach <l.stach@...gutronix.de>
Cc:     Rouven Czerwinski <r.czerwinski@...gutronix.de>,
        ZHIZHIKIN Andrey <andrey.zhizhikin@...ca-geosystems.com>,
        linux-kernel@...r.kernel.org, peng.fan@....com, ping.bai@....com,
        alice.guo@....com, agx@...xcpu.org, krzk@...nel.org,
        leonard.crestez@....com, festevam@...il.com, marex@...x.de,
        herbert@...dor.apana.org.au, horia.geanta@....com,
        daniel.baluta@....com, frieder.schrempf@...tron.de,
        linux-imx@....com, devicetree@...r.kernel.org,
        hongxing.zhu@....com, s.hauer@...gutronix.de, pankaj.gupta@....com,
        robh+dt@...nel.org, thunder.leizhen@...wei.com, martink@...teo.de,
        aford173@...il.com, linux-arm-kernel@...ts.infradead.org,
        gregkh@...uxfoundation.org, shengjiu.wang@....com,
        qiangqing.zhang@....com, op-tee@...ts.trustedfirmware.org,
        linux-crypto@...r.kernel.org, kernel@...gutronix.de,
        shawnguo@...nel.org, davem@...emloft.net, jun.li@....com
Subject: Re: [PATCH v3 2/2] arm64: dts: imx8m: define proper status for caam
 jr

Am 2022-01-07 12:58, schrieb Lucas Stach:
> Am Freitag, dem 07.01.2022 um 12:47 +0100 schrieb Michael Walle:
>> Hi Rouven,
>> 
>> Am 2022-01-07 10:46, schrieb Rouven Czerwinski:
>> > .. since AFAIK i.MX8M* can not be run without TF-A.
>> 
>> Are you sure? There probably aren't any boards out there
>> without TF-A, but why shouldn't it work without it?
> 
> PSCI, i.e. the only means to start the secondary CPUs, is implemented
> in TF-A, so it's very unlikely that anyone would want to run a system
> without TF-A. Also quite a bit of the lowlevel SoC initialization is
> implemented in TF-A.

Doesn't mean u-boot cannot implement PSCI; actually you doesn't need
it at all, you can still use spin tables. I just keep hearing the same
arguments for the LS1028A SoC and yet there is one board without TF-A ;)
Anyway, I admit it's rather unlikely.

-michael