From: Dinh Nguyen <dinguyen@kernel.org>
To: hang.suan.wang@altera.com, linux-kernel@vger.kernel.org,
"Michael S . Tsirkin" <mst@redhat.com>,
Huacai Chen <chenhuacai@kernel.org>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Chen-Yu Tsai <wenst@chromium.org>
Cc: muhammad.nazim.amirul.nazle.asmade@altera.com,
tze.yee.ng@altera.com, chee.nouk.phoon@altera.com,
genevieve.chan@altera.com
Subject: Re: [PATCH v1 0/2] Add Altera SoCFPGA Crypto Service (FCS) driver
Date: Mon, 6 Jul 2026 07:33:25 -0500 [thread overview]
Message-ID: <d07082b1-ee45-4e5b-8c2f-9f0c833eea4b@kernel.org> (raw)
In-Reply-To: <cover.1782888532.git.hang.suan.wang@altera.com>
On 7/1/26 02:39, hang.suan.wang@altera.com wrote:
> From: Hang Suan Wang <hang.suan.wang@altera.com>
>
> This series adds support for the Altera SoCFPGA Crypto Service (FCS), the
> runtime cryptographic interface provided by the Secure Device Manager
> (SDM). The SDM is the hardware security controller in Altera SoCFPGA
> devices. It acts as the root-of-trust device and controls access to
> built-in cryptographic hardware such as AES, SHA, a true random number
> generator, and Intel PUF. The SDM is responsible for security-critical
> functions including secure boot, FPGA bitstream authentication and optional
> decryption, remote system update, and runtime crypto services. On the HPS
> side, software reaches the SDM through a mailbox interface exposed in Linux
> via the stratix10-svc layer, which uses Arm Trusted Firmware SIP SMC calls
> underneath.
>
> The FPGA Crypto Service (FCS) is the runtime crypto interface provided by
> the SDM. It covers services such as random number generation, AES
> operations, HMAC/SHA, key management, attestation, and related security
> functions.
>
> This series implements one FCS feature: the Secure Data Object Service
> (SDOS), which protects sensitive data at rest. With SDOS the SDM encrypts
> and decrypts data using a key derived from a device-unique root key that
> never leaves the secure boundary, plus an SDM-generated IV. The host never
> handles raw key material or IVs: it supplies plaintext and receives an
> authenticated ciphertext object (and vice versa for decryption). A primary
> use case is black key provisioning, where operational keys are installed in
> protected form without ever being exposed in cleartext.
>
> The driver reaches the SDM through the existing stratix10-svc mailbox using
> the Arm Trusted Firmware SIP SMC transport. Data buffers are allocated from
> the service-layer memory pool, which provides physically-contiguous memory
> whose physical address is handed to the SDM.
>
> The series is organized as follows:
> - Patch 1 (prerequisite) extends the stratix10-svc service layer with the
> FCS command codes and matching SIP SMC function IDs, adds the Agilex 5
> (intel,agilex5-svc) match, and registers a "stratix10-fcs" platform
> device that an FCS client driver binds to.
>
> - Patch 2 adds the FCS firmware driver implementing SDOS encrypt/decrypt
> and the crypto-session lifecycle, exposed via sysfs. It relies on the
> command codes and the device from patch 1, so patch 1 must be applied
> first.
>
> Testing:
> - Built for arm64 (defconfig + CONFIG_ALTERA_SOCFPGA_FCS=m).
>
There are a few sashiko comments on this. Can you verify that they are
applicable?
https://sashiko.dev/#/patchset/cover.1782888532.git.hang.suan.wang%40altera.com
Thanks,
Dinh
next prev parent reply other threads:[~2026-07-06 12:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 7:39 hang.suan.wang
2026-07-01 7:39 ` [PATCH v1 1/2] firmware: stratix10-svc: add FCS crypto-service commands for Agilex 5 hang.suan.wang
2026-07-01 7:39 ` [PATCH v1 2/2] firmware: socfpga-fcs: add Altera SoCFPGA FCS driver with SDOS hang.suan.wang
2026-07-07 18:41 ` Dinh Nguyen
2026-07-09 13:24 ` Hang Suan Wang
2026-07-06 12:33 ` Dinh Nguyen [this message]
2026-07-09 7:45 ` [PATCH v1 0/2] Add Altera SoCFPGA Crypto Service (FCS) driver Hang Suan Wang
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=d07082b1-ee45-4e5b-8c2f-9f0c833eea4b@kernel.org \
--to=dinguyen@kernel.org \
--cc=chee.nouk.phoon@altera.com \
--cc=chenhuacai@kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=genevieve.chan@altera.com \
--cc=hang.suan.wang@altera.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=muhammad.nazim.amirul.nazle.asmade@altera.com \
--cc=tze.yee.ng@altera.com \
--cc=wenst@chromium.org \
/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
Powered by JetHome