Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Message-ID: <5e157cb3.1c69fb81.4f0ae.6172@mx.google.com>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <20200108064253.GB4023550@builder>
References: <1578431066-19600-1-git-send-email-eberman@codeaurora.org> <20200108064253.GB4023550@builder>
Cc:     agross@kernel.org, Stephan Gerhold <stephan@gerhold.net>,
        saiprakash.ranjan@codeaurora.org, tsoni@codeaurora.org,
        sidgup@codeaurora.org, psodagud@codeaurora.org,
        Brian Masney <masneyb@onstation.org>,
        linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 00/17] Restructure, improve target support for qcom_scm driver
To:     Bjorn Andersson <bjorn.andersson@linaro.org>,
        Elliot Berman <eberman@codeaurora.org>
From:   Stephen Boyd <swboyd@chromium.org>
User-Agent: alot/0.8.1
Date:   Tue, 07 Jan 2020 22:54:43 -0800
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Quoting Bjorn Andersson (2020-01-07 22:42:53)
> On Tue 07 Jan 13:04 PST 2020, Elliot Berman wrote:
>=20
> > This series improves support for 32-bit Qualcomm targets on qcom_scm dr=
iver and cleans
> > up the driver for 64-bit implementations.
> >=20
> > Currently, the qcom_scm driver supports only 64-bit Qualcomm targets an=
d 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 combin=
es SMCCC
> > and legacy conventions and selects the correct convention by querying t=
he secure
> > world [1].
> >=20
> > We decided to take the opportunity as well to clean up the driver rathe=
r than
> > try to patch together qcom_scm-32 and qcom_scm-64.
> >=20
>=20
> Series applied.

Without the change-ids presumably? I was going to review the patch
series tomorrow but I guess no more need! ;-)