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: <AM6PR06MB469129E72ED6FBE0B33C693DA64C9@AM6PR06MB4691.eurprd06.prod.outlook.com>
Date:   Thu, 6 Jan 2022 10:56:12 +0000
From:   ZHIZHIKIN Andrey <andrey.zhizhikin@...ca-geosystems.com>
To:     "herbert@...dor.apana.org.au" <herbert@...dor.apana.org.au>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC:     "robh+dt@...nel.org" <robh+dt@...nel.org>,
        "shawnguo@...nel.org" <shawnguo@...nel.org>,
        "michael@...le.cc" <michael@...le.cc>,
        "s.hauer@...gutronix.de" <s.hauer@...gutronix.de>,
        "kernel@...gutronix.de" <kernel@...gutronix.de>,
        "festevam@...il.com" <festevam@...il.com>,
        "linux-imx@....com" <linux-imx@....com>,
        "horia.geanta@....com" <horia.geanta@....com>,
        "pankaj.gupta@....com" <pankaj.gupta@....com>,
        "davem@...emloft.net" <davem@...emloft.net>,
        "l.stach@...gutronix.de" <l.stach@...gutronix.de>,
        "qiangqing.zhang@....com" <qiangqing.zhang@....com>,
        "peng.fan@....com" <peng.fan@....com>,
        "alice.guo@....com" <alice.guo@....com>,
        "aford173@...il.com" <aford173@...il.com>,
        "frieder.schrempf@...tron.de" <frieder.schrempf@...tron.de>,
        "krzk@...nel.org" <krzk@...nel.org>,
        "shengjiu.wang@....com" <shengjiu.wang@....com>,
        "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
        "ping.bai@....com" <ping.bai@....com>,
        "daniel.baluta@....com" <daniel.baluta@....com>,
        "jun.li@....com" <jun.li@....com>, "marex@...x.de" <marex@...x.de>,
        "thunder.leizhen@...wei.com" <thunder.leizhen@...wei.com>,
        "martink@...teo.de" <martink@...teo.de>,
        "leonard.crestez@....com" <leonard.crestez@....com>,
        "hongxing.zhu@....com" <hongxing.zhu@....com>,
        "agx@...xcpu.org" <agx@...xcpu.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        "linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
        "op-tee@...ts.trustedfirmware.org" <op-tee@...ts.trustedfirmware.org>
Subject: RE: [PATCH v3 0/2] CAAM Driver: re-factor and set proper JR status

Hello Herbert,

Gentle ping on this V3. I see that in Patchwork this series state is set to "Deferred".

Is there anything missing here to proceed further?

> -----Original Message-----
> From: Andrey Zhizhikin <andrey.zhizhikin@...ca-geosystems.com>
> Sent: Wednesday, December 8, 2021 12:02 AM
> To: linux-kernel@...r.kernel.org
> Cc: robh+dt@...nel.org; shawnguo@...nel.org; michael@...le.cc;
> s.hauer@...gutronix.de; kernel@...gutronix.de; festevam@...il.com; linux-
> imx@....com; horia.geanta@....com; pankaj.gupta@....com;
> herbert@...dor.apana.org.au; davem@...emloft.net; l.stach@...gutronix.de;
> qiangqing.zhang@....com; peng.fan@....com; alice.guo@....com; aford173@...il.com;
> frieder.schrempf@...tron.de; krzk@...nel.org; shengjiu.wang@....com;
> gregkh@...uxfoundation.org; ping.bai@....com; daniel.baluta@....com;
> jun.li@....com; marex@...x.de; thunder.leizhen@...wei.com; martink@...teo.de;
> leonard.crestez@....com; hongxing.zhu@....com; agx@...xcpu.org;
> devicetree@...r.kernel.org; linux-arm-kernel@...ts.infradead.org; linux-
> crypto@...r.kernel.org; op-tee@...ts.trustedfirmware.org; Andrey Zhizhikin
> <andrey.zhizhikin@...ca-geosystems.com>
> Subject: [PATCH v3 0/2] CAAM Driver: re-factor and set proper JR status
> 
> This V3 series covers points uncovered during the review of the previous
> series, one major point being that register readout should not be used
> for dynamic JR availability check due to its unreliability.
> 
> Instead, JR should have a proper status set in FDT which indicates the
> availability of the ring in NS-World. This status is aligned with what
> BootROM code configures, and can be modified by all actors in the boot
> chain.
> 
> Therefore, patch in V2 series that was handling the dynamic JR
> availability check is dropped in this series and replaced by the patch
> which sets proper DT status for JR nodes.
> 
> Andrey Zhizhikin (2):
>   crypto: caam - convert to use capabilities
>   arm64: dts: imx8m: define proper status for caam jr
> 
>  arch/arm64/boot/dts/freescale/imx8mm.dtsi |   4 +
>  arch/arm64/boot/dts/freescale/imx8mn.dtsi |   4 +
>  arch/arm64/boot/dts/freescale/imx8mp.dtsi |   4 +
>  arch/arm64/boot/dts/freescale/imx8mq.dtsi |   4 +
>  drivers/crypto/caam/caamalg_qi.c          |   2 +-
>  drivers/crypto/caam/ctrl.c                | 115 ++++++++++++++--------
>  drivers/crypto/caam/intern.h              |  20 ++--
>  drivers/crypto/caam/jr.c                  |  19 +++-
>  drivers/crypto/caam/regs.h                |   2 -
>  9 files changed, 122 insertions(+), 52 deletions(-)
> 
> 
> base-commit: 04fe99a8d936d46a310ca61b8b63dc270962bf01
> --
> 2.25.1
> 

-- andrey

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ