linux-kernel - Re: [PATCH v5 00/17] Restructure, improve target support for qcom

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] [day] [month] [year] [list]

Date:   Tue, 7 Jan 2020 23:21:50 -0800
From:   Bjorn Andersson <bjorn.andersson@...aro.org>
To:     Stephen Boyd <swboyd@...omium.org>
Cc:     Elliot Berman <eberman@...eaurora.org>, agross@...nel.org,
        Stephan Gerhold <stephan@...hold.net>,
        saiprakash.ranjan@...eaurora.org, tsoni@...eaurora.org,
        sidgup@...eaurora.org, psodagud@...eaurora.org,
        Brian Masney <masneyb@...tation.org>,
        linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 00/17] Restructure, improve target support for
 qcom_scm driver

On Tue 07 Jan 22:54 PST 2020, Stephen Boyd wrote:

> Quoting Bjorn Andersson (2020-01-07 22:42:53)
> > On Tue 07 Jan 13:04 PST 2020, Elliot Berman wrote:
> > 
> > > This series improves support for 32-bit Qualcomm targets on qcom_scm driver and cleans
> > > up the driver for 64-bit implementations.
> > > 
> > > Currently, the qcom_scm driver supports only 64-bit Qualcomm targets and very
> > > old 32-bit Qualcomm targets. Newer 32-bit targets use ARM's SMC Calling
> > > Convention to communicate with secure world. Older 32-bit targets use a
> > > "buffer-based" legacy approach for communicating with secure world (as
> > > implemented in qcom_scm-32.c). All arm64 Qualcomm targets use ARM SMCCC.
> > > Currently, SMCCC-based communication is enabled only on ARM64 config and
> > > buffer-based communication only on ARM config. This patch-series combines SMCCC
> > > and legacy conventions and selects the correct convention by querying the secure
> > > world [1].
> > > 
> > > We decided to take the opportunity as well to clean up the driver rather than
> > > try to patch together qcom_scm-32 and qcom_scm-64.
> > > 
> > 
> > Series applied.
> 
> Without the change-ids presumably?

Of course.

> I was going to review the patch series tomorrow but I guess no more
> need! ;-)
> 

Thanks, I do appreciate the intention :)

Regards,
Bjorn