]> git.ipfire.org Git - thirdparty/kernel/linux.git/commit
EDAC/bluefield: Use Arm SMC for EMI access on BlueField-2
authorDavid Thompson <davthompson@nvidia.com>
Mon, 21 Oct 2024 23:30:13 +0000 (19:30 -0400)
committerBorislav Petkov (AMD) <bp@alien8.de>
Tue, 22 Oct 2024 16:36:13 +0000 (18:36 +0200)
commite4196757547444f7c4c156e56ea9d44612e97cbf
tree5b7c644ab2bf22866d810e22639abe33bbc41450
parent1fe774a93b46bb029b8f6fa9d1f25affa53f06c6
EDAC/bluefield: Use Arm SMC for EMI access on BlueField-2

The BlueField EDAC driver supports the first generation BlueField-1 SoC, but
not the second generation BlueField-2 SoC. The BlueField-2 SoC is different in
that only secure accesses are allowed to the External Memory Interface (EMI)
register block. On BlueField-2, all read/write accesses from Linux to EMI
registers are routed via the Arm Secure Monitor Call (SMC) through Arm Trusted
Firmware (ATF), which runs at EL3 privileged state.

On BlueField-1, EMI registers are mapped and accessed directly. In order to
support BlueField-2, the driver's read and write access methods must be
extended with additional logic to include secure access to the EMI registers
via SMCs.

  [ bp: Move struct member comments above them, simplify. ]

Signed-off-by: David Thompson <davthompson@nvidia.com>
Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
Reviewed-by: Shravan Kumar Ramani <shravankr@nvidia.com>
Link: https://lore.kernel.org/r/20241021233013.18405-1-davthompson@nvidia.com
drivers/edac/bluefield_edac.c