RISC-V: clarify what some RISCV_ISA* config options do
authorConor Dooley <conor.dooley@microchip.com>
Thu, 24 Oct 2024 10:19:40 +0000 (11:19 +0100)
committerAlexandre Ghiti <alexghiti@rivosinc.com>
Tue, 18 Mar 2025 08:53:02 +0000 (08:53 +0000)
commit6216182fb776ae546c5566f21976d116c8650cee
tree9b08495844ef9ca26b10447c20914647d99d986f
parent4295f4ccfe8c6e6ac5b631919ba7a4fe89d22acf
RISC-V: clarify what some RISCV_ISA* config options do

During some discussion on IRC yesterday and on Pu's bpf patch [1]
I noticed that these RISCV_ISA* Kconfig options are not really clear
about their implications. Many of these options have no impact on what
userspace is allowed to do, for example an application can use Zbb
regardless of whether or not the kernel does. Change the help text to
try and clarify whether or not an option affects just the kernel, or
also userspace. None of these options actually control whether or not an
extension is detected dynamically as that's done regardless of Kconfig
options, so drop any text that implies the option is required for
dynamic detection, rewording them as "do x when y is detected".

Link: https://lore.kernel.org/linux-riscv/20240328-ferocity-repose-c554f75a676c@spud/
Reviewed-by: Andrew Jones <ajones@ventanamicro.com>
Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
Reviewed-by: Charlie Jenkins <charlie@rivosinc.com>
Reviewed-by: Samuel Holland <samuel.holland@sifive.com>
Link: https://lore.kernel.org/r/20241024-overdue-slogan-0b0f69d3da91@spud
Signed-off-by: Alexandre Ghiti <alexghiti@rivosinc.com>
arch/riscv/Kconfig