mirror of
https://github.com/u-boot/u-boot.git
synced 2025-04-27 07:51:38 +00:00
riscv: clarify meaning of CONFIG_SBI_V02
Describe that CONFIG_SBI_V02=y does not mean SBI specification v0.2 but v0.2 or later. Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com> Reviewed-by: Rick Chen <rick@andestech.com>
This commit is contained in:
parent
c277c787a0
commit
5c89467262
1 changed files with 7 additions and 7 deletions
|
@ -257,16 +257,16 @@ config SBI_V01
|
||||||
deprecated in future once legacy M-mode software are no longer in use.
|
deprecated in future once legacy M-mode software are no longer in use.
|
||||||
|
|
||||||
config SBI_V02
|
config SBI_V02
|
||||||
bool "SBI v0.2 support"
|
bool "SBI v0.2 or later support"
|
||||||
depends on SBI
|
depends on SBI
|
||||||
help
|
help
|
||||||
This config allows kernel to use SBI v0.2 APIs. SBI v0.2 is more
|
The SBI specification introduced the concept of extensions in version
|
||||||
scalable and extendable to handle future needs for RISC-V supervisor
|
v0.2. With this configuration option U-Boot can detect and use SBI
|
||||||
interfaces. For example, with SBI v0.2 HSM extension, only a single
|
extensions. With the HSM extension introduced in SBI 0.2, only a
|
||||||
hart need to boot and enter operating system. The booting hart can
|
single hart needs to boot and enter the operating system. The booting
|
||||||
bring up secondary harts one by one afterwards.
|
hart can bring up secondary harts one by one afterwards.
|
||||||
|
|
||||||
Choose this option if OpenSBI v0.7 or above release is used together
|
Choose this option if OpenSBI release v0.7 or above is used together
|
||||||
with U-Boot.
|
with U-Boot.
|
||||||
|
|
||||||
endchoice
|
endchoice
|
||||||
|
|
Loading…
Add table
Reference in a new issue