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;
Date:   Tue, 7 Jan 2020 23:21:50 -0800
From:   Bjorn Andersson <bjorn.andersson@linaro.org>
To:     Stephen Boyd <swboyd@chromium.org>
Cc:     Elliot Berman <eberman@codeaurora.org>, 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
Message-ID: <20200108072150.GK738324@yoga>
References: <1578431066-19600-1-git-send-email-eberman@codeaurora.org>
 <20200108064253.GB4023550@builder>
 <5e157cb3.1c69fb81.4f0ae.6172@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5e157cb3.1c69fb81.4f0ae.6172@mx.google.com>
User-Agent: Mutt/1.12.2 (2019-09-21)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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