From: Eric Biggers <ebiggers@kernel.org>
To: Konrad Dybcio <konradybcio@gmail.com>
Cc: linux-crypto@vger.kernel.org, Satya Tangirala <satyat@google.com>
Subject: Re: Qualcomm Crypto Engine driver
Date: Thu, 12 Nov 2020 13:20:13 -0800 [thread overview]
Message-ID: <X62nDWQNHy1pk+3t@sol.localdomain> (raw)
In-Reply-To: <CAMS8qEX766tggsR0DpJm8TVRwctwwvnRofiiDWhqsNDDK6exYA@mail.gmail.com>
Hi Konrad,
On Thu, Nov 12, 2020 at 09:26:30PM +0100, Konrad Dybcio wrote:
> 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..)
A while ago, I benchmarked the QCE on an older SoC, and it was much slower than
just using the ARMv8 crypto extensions. So I'm not surprised. I don't think
QCE is really used anymore. But almost everyone uses ICE.
> 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..
I'm already using your v5.10-rc3 branch, but ninges_defconfig isn't working for
me. (Though I couldn't find the firmware file "qcom/a530_zap.elf", so I had to
remove it from CONFIG_EXTRA_FIRMWARE.) Instead I'm using a kconfig based on
https://github.com/SoMainline/linux/blob/marijn/android/arch/arm64/configs/defconfig
which is working for me.
I haven't been able to get a full Android userspace to work, and currently I'm
instead just replacing the kernel in a TWRP image and booting into recovery.
It's enough to get adb shell access and chroot into a Debian chroot on the
userdata partition, which is enough to run android-xfstests to test the ICE
support. Earlier I tried AOSP using the instructions at
https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/build-aosp-android-android-11-0-0,
and also LineageOS using the instuctions at
https://wiki.lineageos.org/devices/kirin/build, but neither worked. That was a
couple weeks ago though, so I haven't tried the very latest kernel with full
Android. Let me know if you have any suggestions!
Thanks,
- Eric
next prev parent reply other threads:[~2020-11-12 21:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 11:55 Qualcomm Crypto Engine driver Konrad Dybcio
2020-10-23 17:00 ` Eric Biggers
2020-11-12 20:26 ` Konrad Dybcio
2020-11-12 21:20 ` Eric Biggers [this message]
2020-11-14 13:16 ` Konrad Dybcio
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=X62nDWQNHy1pk+3t@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=konradybcio@gmail.com \
--cc=linux-crypto@vger.kernel.org \
--cc=satyat@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox