From: Wei Xu <xuwei5@hisilicon.com>
To: Chenghai Huang <huangchenghai2@huawei.com>,
<herbert@gondor.apana.org.au>, <davem@davemloft.net>
Cc: <linux-kernel@vger.kernel.org>, <linux-crypto@vger.kernel.org>,
<xuwei5@huawei.com>, <prime.zeng@hisilicon.com>,
<liulongfang@huawei.com>, <qianweili@huawei.com>,
<wangzhou1@hisilicon.com>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
"Rob Herring" <robh+dt@kernel.org>
Subject: Re: [PATCH] crypto: hisilicon/sec - remove SEC crypto block cipher accelerator
Date: Wed, 19 Aug 2026 11:55:40 +0800 [thread overview]
Message-ID: <6A85293C.2010008@hisilicon.com> (raw)
In-Reply-To: <20260818083132.1860726-1-huangchenghai2@huawei.com>
Hi Chenghai,
On 2026/8/18 16:31, Chenghai Huang wrote:
> The Hisilicon SEC crypto cipher accelerator has been superseded
> by the newer SEC2 driver (drivers/crypto/hisilicon/sec2/). SEC2
> provides wider algorithm coverage and is the maintained path forward,
> and users have migrated to it.
>
> The legacy SEC driver has had no active users for some time, and its
> primary maintainer, Jonathan Cameron, has moved on from Huawei and
> is no longer in a position to maintain it. With thanks to Jonathan
> for his contributions to this driver over the years, and with no one
> left to keep it up to date, remove it from the tree.
>
> This drops the legacy SEC driver together with all of its residual
> configuration, devicetree binding and board description references:
>
> - drivers/crypto/hisilicon/sec/
> - CONFIG_CRYPTO_DEV_HISI_SEC Kconfig option
> - sec/ entry from drivers/crypto/hisilicon/Makefile
> - Documentation/devicetree/bindings/crypto/hisilicon,hip06-sec.yaml
> - hisilicon,hip07-sec device nodes and their supporting mbigen_alg /
> smmu_alg infrastructure from arch/arm64/boot/dts/hisilicon/hip07.dtsi
>
> Signed-off-by: Chenghai Huang <huangchenghai2@huawei.com>
> ---
> .../bindings/crypto/hisilicon,hip06-sec.yaml | 134 --
> arch/arm64/boot/dts/hisilicon/hip07.dtsi | 280 ----
Since no active users, it is fine to me to drop the dts part as well.
Acked-by: Wei Xu <xuwei5@hisilicon.com>
Best Regards,
Wei
parent reply other threads:[~2026-08-19 3:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260818083132.1860726-1-huangchenghai2@huawei.com>]
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=6A85293C.2010008@hisilicon.com \
--to=xuwei5@hisilicon.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=huangchenghai2@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liulongfang@huawei.com \
--cc=prime.zeng@hisilicon.com \
--cc=qianweili@huawei.com \
--cc=robh+dt@kernel.org \
--cc=wangzhou1@hisilicon.com \
--cc=xuwei5@huawei.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