doc: use :kconfig:option: domain role
Kconfig options now belong to the Kconfig domain, therefore, the :kconfig:option: role needs to be used. Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
This commit is contained in:
parent
fc942ef7d3
commit
260deccb6e
162 changed files with 696 additions and 696 deletions
|
@ -35,6 +35,6 @@ After flashing, the LED starts to blink.
|
|||
PM configurations
|
||||
*****************
|
||||
|
||||
By default, :kconfig:`CONFIG_PM_DEVICE` and :kconfig:`CONFIG_PM_DEVICE_RUNTIME` are
|
||||
By default, :kconfig:option:`CONFIG_PM_DEVICE` and :kconfig:option:`CONFIG_PM_DEVICE_RUNTIME` are
|
||||
enabled, but user can also deactivate one or the other to see each configuration
|
||||
in play.
|
||||
|
|
|
@ -7,7 +7,7 @@ Overview
|
|||
********
|
||||
|
||||
A simple application demonstrating the BLE operations (advertising) with
|
||||
Zephyr power management enabled (:kconfig:`CONFIG_PM`).
|
||||
Zephyr power management enabled (:kconfig:option:`CONFIG_PM`).
|
||||
|
||||
After startup, a first 2 seconds beacon is performed, 1 second break and
|
||||
beacon is started again.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue