Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <CAMS8qEVZFBFv4VpFtijxnR8Z5-wWFkpZx8nKOmbm6U-vah7eLg@mail.gmail.com>
 <20201023170003.GC3908702@gmail.com>
In-Reply-To: <20201023170003.GC3908702@gmail.com>
From:   Konrad Dybcio <konradybcio@gmail.com>
Date:   Thu, 12 Nov 2020 21:26:30 +0100
Message-ID: <CAMS8qEX766tggsR0DpJm8TVRwctwwvnRofiiDWhqsNDDK6exYA@mail.gmail.com>
Subject: Re: Qualcomm Crypto Engine driver
To:     Eric Biggers <ebiggers@kernel.org>
Cc:     linux-crypto@vger.kernel.org, Satya Tangirala <satyat@google.com>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

Hi Eric,

First of all, I am EXTREMELY sorry for my long overdue response..

I just wanted to bring up that piece of HW so as to offload crypto
tasks from the CPU, but it ended up being slower (which I suspect is
due to bw scaling not being implemented, but I might be wrong, maybe
A53+crypto is just superior..)

The goal is to have the phone run Mainline Linux *at least* at
functional parity with the BSP kernel. Both ICE and CE support are
welcome.

Thanks for your interest and the patches you sent. There is more
sdm630 (and not only, keep watching :D) work coming. I suppose you
managed to boot your Xperia by now, but if you had issues, you should
try out my v5.10-rc3 branch from the repo you linked with the supplied
ninges_defconfig. Then you append the DTB to Image.gz and create an
Android boot image (or put Image.gz+dtb into an existing one with
abootimg -u boot.img -k Image.gz+dtb) and the phone should boot.

Thanks once again for your interest and apologies for the time it took..

Konrad