From: huangchenghai <huangchenghai2@huawei.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: <herbert@gondor.apana.org.au>, <davem@davemloft.net>,
<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>
Subject: Re: [PATCH] crypto: hisilicon/sec - remove SEC crypto block cipher accelerator
Date: Wed, 19 Aug 2026 14:47:24 +0800 [thread overview]
Message-ID: <1d40794f-092f-459d-90a9-efcc266a7241@huawei.com> (raw)
In-Reply-To: <20260818172850.GC2249@quark>
在 2026/8/19 1:28, Eric Biggers 写道:
> On Tue, Aug 18, 2026 at 04:31:32PM +0800, 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>
> Acked-by: Eric Biggers <ebiggers@kernel.org>
>
> You might also need an ack from a devicetree maintainer for dropping the
> devicetree binding, though. They sometimes like to keep the bindings
> around even with no driver for some reason.
>
> - Eric
Alright, I will resend it and send it to the devicetree maintainer.
Thanks,
Chenghai
next prev parent reply other threads:[~2026-08-19 6:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 8:31 [PATCH] crypto: hisilicon/sec - remove SEC crypto block cipher accelerator Chenghai Huang
2026-08-18 17:28 ` Eric Biggers
2026-08-19 6:47 ` huangchenghai [this message]
2026-08-19 2:37 ` liulongfang
2026-08-19 3:55 ` Wei Xu
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=1d40794f-092f-459d-90a9-efcc266a7241@huawei.com \
--to=huangchenghai2@huawei.com \
--cc=davem@davemloft.net \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--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=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