2015-02-13 17:30:06 +01:00
|
|
|
#
|
|
|
|
# For a description of the syntax of this configuration file,
|
2015-06-28 16:08:57 +02:00
|
|
|
# see the file kconfig-language.txt in the NuttX tools repository.
|
2015-02-13 17:30:06 +01:00
|
|
|
#
|
|
|
|
|
2015-04-02 21:00:10 +02:00
|
|
|
menu "Timer Driver Support"
|
|
|
|
|
2020-02-08 08:30:09 +01:00
|
|
|
config ARCH_HAVE_PWM_PULSECOUNT
|
|
|
|
bool
|
|
|
|
default n
|
|
|
|
|
2023-02-18 13:31:45 +01:00
|
|
|
config ARCH_HAVE_PWM_OVERWRITE
|
|
|
|
bool
|
|
|
|
default n
|
|
|
|
|
2023-03-06 12:41:11 +01:00
|
|
|
config ARCH_HAVE_PWM_DEADTIME
|
|
|
|
bool
|
|
|
|
default n
|
|
|
|
|
2020-02-08 08:30:09 +01:00
|
|
|
config ARCH_HAVE_PWM_MULTICHAN
|
|
|
|
bool
|
|
|
|
default n
|
|
|
|
|
2019-09-02 15:53:52 +02:00
|
|
|
config PWM
|
|
|
|
bool "PWM Driver Support"
|
|
|
|
default n
|
|
|
|
---help---
|
|
|
|
This selection enables building of the "upper-half" PWM driver.
|
|
|
|
See include/nuttx/timers/pwm.h for further PWM driver information.
|
|
|
|
|
|
|
|
if PWM
|
|
|
|
|
|
|
|
config PWM_PULSECOUNT
|
2019-10-06 05:39:12 +02:00
|
|
|
bool "PWM Pulse Count Support"
|
|
|
|
default n
|
|
|
|
depends on ARCH_HAVE_PWM_PULSECOUNT
|
|
|
|
---help---
|
|
|
|
Some hardware will support generation of a fixed number of pulses.
|
|
|
|
This might be used, for example to support a stepper motor. If the
|
|
|
|
hardware will support a fixed pulse count, then this configuration
|
|
|
|
should be set to enable the capability.
|
2019-09-02 15:53:52 +02:00
|
|
|
|
2023-02-18 13:31:45 +01:00
|
|
|
config PWM_OVERWRITE
|
|
|
|
bool "PWM Overwrite Support"
|
|
|
|
default n
|
|
|
|
depends on ARCH_HAVE_PWM_OVERWRITE
|
|
|
|
---help---
|
|
|
|
Some hardware will support generation of a pin overwrite with 0 or
|
|
|
|
1 without the need to wait for an end of cycle. The overwrite is
|
|
|
|
controlled from an application level the same way duty cycle or
|
|
|
|
frequency is modified.
|
|
|
|
|
2023-03-06 12:41:11 +01:00
|
|
|
config PWM_DEADTIME
|
|
|
|
bool "PWM Deadtime Support"
|
|
|
|
default n
|
|
|
|
depends on ARCH_HAVE_PWM_DEADTIME
|
|
|
|
---help---
|
|
|
|
Some hardware will support deadtime generators that automatically
|
|
|
|
insert output activation delay for complementary PWM outputs. This
|
|
|
|
is usefull for H-bridge motor control for example. The deadtime
|
|
|
|
values are set from application level via the same IOCTL that sets
|
|
|
|
up duty cycle and frequency.
|
|
|
|
|
|
|
|
For detailed description about deadtime functionality please refer
|
|
|
|
to architecture manuals and datasheets.
|
|
|
|
|
2019-09-02 15:53:52 +02:00
|
|
|
config PWM_MULTICHAN
|
2019-10-06 05:39:12 +02:00
|
|
|
bool "PWM Multiple Output Channel Support"
|
|
|
|
default n
|
|
|
|
depends on ARCH_HAVE_PWM_MULTICHAN
|
|
|
|
depends on !PWM_PULSECOUNT
|
|
|
|
---help---
|
|
|
|
Enables support for multiple output channels per timer.
|
2019-09-02 15:53:52 +02:00
|
|
|
|
|
|
|
if PWM_MULTICHAN
|
|
|
|
|
|
|
|
config PWM_NCHANNELS
|
2019-10-06 05:39:12 +02:00
|
|
|
int "Number of Output Channels Per Timer"
|
|
|
|
default 1
|
2021-06-23 11:09:18 +02:00
|
|
|
range 1 16
|
2019-10-06 05:39:12 +02:00
|
|
|
---help---
|
|
|
|
Specifies the number of output channels per timer. Each timer
|
|
|
|
may support fewer output channels than this value.
|
2019-09-02 15:53:52 +02:00
|
|
|
|
|
|
|
endif # PWM_MULTICHAN
|
|
|
|
endif # PWM
|
|
|
|
|
2022-06-26 14:00:38 +02:00
|
|
|
config CAPTURE
|
|
|
|
bool "Capture Driver Support"
|
|
|
|
default n
|
|
|
|
---help---
|
|
|
|
This selection enables building of the "upper-half" Capture driver.
|
|
|
|
See include/nuttx/timers/capture.h for further Capture driver information.
|
|
|
|
|
2016-08-12 18:40:07 +02:00
|
|
|
config TIMER
|
2015-02-13 17:30:06 +01:00
|
|
|
bool "Timer Support"
|
|
|
|
default n
|
|
|
|
---help---
|
|
|
|
This selection enables building of the "upper-half" timer
|
2015-04-01 20:37:44 +02:00
|
|
|
driver. See include/nuttx/timers/timer.h for further timer driver
|
2015-02-13 17:30:06 +01:00
|
|
|
information.
|
|
|
|
|
2018-08-27 19:55:30 +02:00
|
|
|
if TIMER
|
|
|
|
|
|
|
|
config TIMER_ARCH
|
|
|
|
bool "Timer Arch Implementation"
|
|
|
|
select ARCH_HAVE_TICKLESS
|
|
|
|
select ARCH_HAVE_TIMEKEEPING
|
2020-09-04 11:55:05 +02:00
|
|
|
select SCHED_TICKLESS_LIMIT_MAX_SLEEP if SCHED_TICKLESS
|
2022-09-09 09:17:18 +02:00
|
|
|
select SCHED_TICKLESS_TICK_ARGUMENT if SCHED_TICKLESS
|
2018-08-27 19:55:30 +02:00
|
|
|
---help---
|
|
|
|
Implement timer arch API on top of timer driver interface.
|
|
|
|
|
|
|
|
endif # TIMER
|
|
|
|
|
2016-08-12 18:40:07 +02:00
|
|
|
config ONESHOT
|
|
|
|
bool "Oneshot timer driver"
|
|
|
|
default n
|
|
|
|
---help---
|
|
|
|
This selection enables building of the "upper-half" oneshot timer
|
|
|
|
driver. See include/nuttx/timers/oneshot.h for further oneshot timer
|
|
|
|
driver information.
|
|
|
|
|
2018-08-27 19:55:30 +02:00
|
|
|
if ONESHOT
|
|
|
|
|
|
|
|
config ALARM_ARCH
|
|
|
|
bool "Alarm Arch Implementation"
|
|
|
|
select ARCH_HAVE_TICKLESS
|
|
|
|
select ARCH_HAVE_TIMEKEEPING
|
2020-09-04 11:55:05 +02:00
|
|
|
select SCHED_TICKLESS_ALARM if SCHED_TICKLESS
|
|
|
|
select SCHED_TICKLESS_LIMIT_MAX_SLEEP if SCHED_TICKLESS
|
2022-09-23 08:36:49 +02:00
|
|
|
select SCHED_TICKLESS_TICK_ARGUMENT if SCHED_TICKLESS
|
2018-08-27 19:55:30 +02:00
|
|
|
---help---
|
|
|
|
Implement alarm arch API on top of oneshot driver interface.
|
|
|
|
|
|
|
|
endif # ONESHOT
|
|
|
|
|
2015-02-13 17:30:06 +01:00
|
|
|
menuconfig RTC
|
|
|
|
bool "RTC Driver Support"
|
|
|
|
default n
|
|
|
|
---help---
|
|
|
|
This selection enables configuration of a real time clock (RTCdriver.
|
2015-04-01 20:37:44 +02:00
|
|
|
See include/nuttx/timers/rtc.h for further RTC driver information.
|
2015-02-13 17:30:06 +01:00
|
|
|
Most RTC drivers are MCU specific and may require other specific
|
|
|
|
settings.
|
|
|
|
|
|
|
|
if RTC
|
|
|
|
|
|
|
|
config RTC_DATETIME
|
|
|
|
bool "Date/Time RTC Support"
|
|
|
|
default n
|
|
|
|
---help---
|
|
|
|
There are two general types of RTC: (1) A simple battery backed
|
|
|
|
counter that keeps the time when power is down, and (2) a full
|
|
|
|
date / time RTC the provides the date and time information, often in
|
|
|
|
BCD format. If RTC_DATETIME is selected, it specifies this second kind
|
|
|
|
of RTC. In this case, the RTC is used to "seed" the normal NuttX timer
|
|
|
|
and the NuttX system timer provides for higher resolution time.
|
|
|
|
|
|
|
|
if !RTC_DATETIME
|
|
|
|
|
|
|
|
config RTC_HIRES
|
|
|
|
bool "Hi-Res RTC Support"
|
|
|
|
default n
|
|
|
|
---help---
|
|
|
|
If RTC_DATETIME not selected, then the simple, battery backed counter
|
|
|
|
is used. There are two different implementations of such simple
|
|
|
|
counters based on the time resolution of the counter: The typical RTC
|
|
|
|
keeps time to resolution of 1 second, usually supporting a 32-bit
|
|
|
|
time_t value. In this case, the RTC is used to "seed" the normal NuttX
|
|
|
|
timer and the NuttX timer provides for higherresoution time.
|
|
|
|
|
|
|
|
If RTC_HIRES is enabled in the NuttX configuration, then the RTC
|
|
|
|
provides higher resolution time and completely replaces the system
|
|
|
|
timer for purpose of date and time.
|
|
|
|
|
|
|
|
config RTC_FREQUENCY
|
|
|
|
int "Hi-Res RTC frequency"
|
|
|
|
default 1
|
|
|
|
depends on RTC_HIRES
|
|
|
|
---help---
|
|
|
|
If RTC_HIRES is defined, then the frequency of the high resolution RTC
|
|
|
|
must be provided. If RTC_HIRES is not defined, RTC_FREQUENCY is
|
|
|
|
assumed to be one Hz.
|
|
|
|
|
2023-11-14 12:52:53 +01:00
|
|
|
config RTC_ADJTIME
|
|
|
|
bool "RTC Adjustment Support"
|
|
|
|
default N
|
|
|
|
depends on RTC_HIRES
|
|
|
|
---help---
|
|
|
|
Enable support for adjtime() to adjust RTC run rate. The following
|
|
|
|
interface must be provided by RTC driver:
|
|
|
|
|
|
|
|
int up_rtc_adjtime(long ppb);
|
|
|
|
|
2015-02-13 17:30:06 +01:00
|
|
|
endif # !RTC_DATETIME
|
|
|
|
|
2015-02-25 14:22:58 +01:00
|
|
|
config RTC_ALARM
|
|
|
|
bool "RTC Alarm Support"
|
|
|
|
default n
|
|
|
|
---help---
|
|
|
|
Enable if the RTC hardware supports setting of an alarm. A callback
|
|
|
|
function will be executed when the alarm goes off.
|
|
|
|
|
2016-04-02 21:01:02 +02:00
|
|
|
config RTC_NALARMS
|
|
|
|
int "Number of alarms"
|
|
|
|
default 1
|
2016-04-04 17:24:27 +02:00
|
|
|
depends on RTC_ALARM
|
2016-04-02 21:01:02 +02:00
|
|
|
---help---
|
|
|
|
Number of alarms supported by the hardware.
|
|
|
|
|
2015-02-15 15:19:23 +01:00
|
|
|
config RTC_DRIVER
|
|
|
|
bool "RTC Driver Support"
|
|
|
|
default n
|
|
|
|
---help---
|
|
|
|
This selection enables building of the "upper-half" RTC
|
2015-04-01 20:37:44 +02:00
|
|
|
driver. See include/nuttx/timers/rtc.h for further RTC driver
|
2015-02-15 15:19:23 +01:00
|
|
|
information.
|
|
|
|
|
|
|
|
if RTC_DRIVER
|
|
|
|
|
2018-08-27 19:55:30 +02:00
|
|
|
config RTC_ARCH
|
|
|
|
bool "RTC Arch Implementation"
|
|
|
|
default n
|
|
|
|
---help---
|
|
|
|
Implement RTC arch API on top of RTC driver interface.
|
|
|
|
|
2015-02-15 15:19:23 +01:00
|
|
|
config RTC_PERIODIC
|
|
|
|
bool "RTC Periodic Interrupts"
|
2015-02-13 17:30:06 +01:00
|
|
|
default n
|
|
|
|
---help---
|
2015-02-15 15:19:23 +01:00
|
|
|
Add interrupt controls for RTCs that support periodic interrupts.
|
|
|
|
|
2015-02-18 15:23:10 +01:00
|
|
|
config RTC_IOCTL
|
|
|
|
bool "RTC IOCTLs"
|
|
|
|
default n
|
|
|
|
---help---
|
|
|
|
Support the RTC interface ioctl() method. This allows you to add
|
|
|
|
architecture-specific RTC operations to the RTC interface
|
|
|
|
|
2015-02-15 15:19:23 +01:00
|
|
|
endif # RTC_DRIVER
|
2015-11-17 21:07:55 +01:00
|
|
|
|
2015-11-19 21:54:30 +01:00
|
|
|
config RTC_EXTERNAL
|
|
|
|
bool "External RTC Support"
|
|
|
|
default n
|
|
|
|
---help---
|
|
|
|
In modern MCUs, the RTC is usually implement as an internal
|
|
|
|
peripheral to the MCU. An option is to use an external RTC
|
|
|
|
connected to the MCU typically via SPI or I2C.
|
|
|
|
|
|
|
|
If an external RTC is connect to the MCU through some bus, then the
|
|
|
|
RTC will not be available to the system until after the system
|
|
|
|
fully boots up and is able to access the bus. In that case, this
|
|
|
|
setting must be included to suppress attempts to initialize the RTC
|
|
|
|
early in the boot sequence.
|
|
|
|
|
|
|
|
config RTC_DSXXXX
|
2015-11-20 02:26:09 +01:00
|
|
|
bool "DS130x/DS323x RTC Driver"
|
2015-11-17 21:07:55 +01:00
|
|
|
default n
|
|
|
|
select I2C
|
|
|
|
select RTC_DATETIME
|
2015-11-29 19:13:24 +01:00
|
|
|
depends on RTC_EXTERNAL
|
2015-11-17 21:07:55 +01:00
|
|
|
---help---
|
|
|
|
Enables support for the Maxim Integrated DS3231 I2C RTC timer.
|
|
|
|
|
2015-11-19 21:54:30 +01:00
|
|
|
if RTC_DSXXXX
|
2015-11-18 15:43:19 +01:00
|
|
|
|
|
|
|
choice
|
|
|
|
prompt "Maxim Integrated RTC"
|
|
|
|
default RTC_DS3231
|
|
|
|
|
2015-11-20 02:26:09 +01:00
|
|
|
config RTC_DS1302
|
|
|
|
bool "DS1302"
|
|
|
|
---help---
|
2018-07-22 13:56:11 +02:00
|
|
|
Enables support for the Maxim Integrated DS1302 serial RTC timer.
|
2015-11-20 02:26:09 +01:00
|
|
|
|
2015-11-18 15:43:19 +01:00
|
|
|
config RTC_DS1307
|
|
|
|
bool "DS1307"
|
|
|
|
---help---
|
2015-11-19 22:57:36 +01:00
|
|
|
Enables support for the Maxim Integrated DS1307 I2C RTC timer.
|
2015-11-18 15:43:19 +01:00
|
|
|
|
|
|
|
config RTC_DS3231
|
|
|
|
bool "DS3231"
|
|
|
|
---help---
|
2015-11-19 22:57:36 +01:00
|
|
|
Enables support for the Maxim Integrated DS3231 I2C RTC timer.
|
|
|
|
|
2015-11-20 02:26:09 +01:00
|
|
|
config RTC_DS3232
|
|
|
|
bool "DS3232"
|
|
|
|
---help---
|
|
|
|
Enables support for the Maxim Integrated DS3232 I2C RTC timer.
|
|
|
|
|
2015-11-19 22:57:36 +01:00
|
|
|
config RTC_DS3234
|
|
|
|
bool "DS3234"
|
|
|
|
depends on EXPERIMENTAL
|
|
|
|
---help---
|
|
|
|
Enables support for the Maxim Integrated DS3234 SPI RTC timer.
|
|
|
|
|
|
|
|
Not yet implemented.
|
2015-11-18 15:43:19 +01:00
|
|
|
|
|
|
|
endchoice # Maxim Integrated RTC
|
2015-11-17 21:07:55 +01:00
|
|
|
|
|
|
|
config DS3231_I2C_FREQUENCY
|
2015-11-19 22:57:36 +01:00
|
|
|
int "DS1307/DS323x I2C frequency"
|
2015-11-17 21:07:55 +01:00
|
|
|
default 400000
|
2015-11-21 00:36:10 +01:00
|
|
|
range 1 400000
|
2015-11-17 21:07:55 +01:00
|
|
|
|
2015-11-19 21:54:30 +01:00
|
|
|
endif # RTC_DSXXXX
|
2015-11-21 00:36:10 +01:00
|
|
|
|
|
|
|
config RTC_PCF85263
|
|
|
|
bool "PCF85263 RTC Driver"
|
|
|
|
default n
|
|
|
|
select I2C
|
|
|
|
select RTC_DATETIME
|
2015-11-29 19:13:24 +01:00
|
|
|
depends on RTC_EXTERNAL
|
2015-11-21 00:36:10 +01:00
|
|
|
---help---
|
2019-01-07 00:32:02 +01:00
|
|
|
Enables support for the NXP PCF85263 I2C RTC timer.
|
2015-11-21 00:36:10 +01:00
|
|
|
|
|
|
|
if RTC_PCF85263
|
|
|
|
|
|
|
|
config PCF85263_I2C_FREQUENCY
|
|
|
|
int "PCF85263 I2C frequency"
|
|
|
|
default 400000
|
|
|
|
range 1 400000
|
|
|
|
|
|
|
|
endif # RTC_PCF85263
|
2019-01-07 00:32:02 +01:00
|
|
|
|
2023-06-27 14:55:06 +02:00
|
|
|
config RTC_PL031
|
|
|
|
bool "PL031 RTC Support"
|
|
|
|
default n
|
|
|
|
|
2019-01-08 20:04:50 +01:00
|
|
|
config RTC_MCP794XX
|
|
|
|
bool "MCP794XX RTC Driver"
|
2019-01-07 00:32:02 +01:00
|
|
|
default n
|
|
|
|
select I2C
|
|
|
|
select RTC_DATETIME
|
|
|
|
depends on RTC_EXTERNAL
|
|
|
|
---help---
|
2019-01-08 20:04:50 +01:00
|
|
|
Enables support for the Microchip MCP794XX I2C RTC timer.
|
2019-01-07 00:32:02 +01:00
|
|
|
|
2019-01-08 20:04:50 +01:00
|
|
|
if RTC_MCP794XX
|
2019-01-07 00:32:02 +01:00
|
|
|
|
2024-05-28 10:16:48 +02:00
|
|
|
config MCP794XX_DATETIME_UTC
|
|
|
|
bool "Store datetime in UTC"
|
|
|
|
default n
|
|
|
|
---help---
|
|
|
|
If set, the datetime is stored in UTC timezone instead of timezone
|
|
|
|
defined by local time.
|
|
|
|
|
2019-01-08 20:04:50 +01:00
|
|
|
config MCP794XX_I2C_FREQUENCY
|
|
|
|
int "MCP794XX I2C frequency"
|
2019-01-07 00:32:02 +01:00
|
|
|
default 400000
|
|
|
|
range 1 400000
|
|
|
|
|
2019-01-08 20:04:50 +01:00
|
|
|
endif # RTC_MCP794XX
|
2019-11-02 18:30:33 +01:00
|
|
|
|
2022-02-24 07:43:33 +01:00
|
|
|
config RTC_RX8010SJ
|
|
|
|
bool "RX8010SJ RTC Driver"
|
|
|
|
default n
|
|
|
|
select I2C
|
|
|
|
select RTC_DATETIME
|
|
|
|
depends on RTC_EXTERNAL
|
|
|
|
---help---
|
|
|
|
Enables support for the EPSON RX-8010SJ I2C RTC timer.
|
|
|
|
|
|
|
|
if RTC_RX8010SJ
|
|
|
|
|
|
|
|
config RX8010SJ_I2C_FREQUENCY
|
|
|
|
int "RX8010SJ I2C frequency"
|
|
|
|
default 400000
|
|
|
|
range 1 400000
|
|
|
|
|
|
|
|
endif # RTC_RX8010SJ
|
|
|
|
|
2019-11-02 18:30:33 +01:00
|
|
|
config RTC_RPMSG
|
2023-10-27 12:56:33 +02:00
|
|
|
bool "RPMSG RTC Driver"
|
2019-11-02 18:30:33 +01:00
|
|
|
default n
|
2024-02-04 07:30:39 +01:00
|
|
|
depends on RPMSG
|
2019-11-02 18:30:33 +01:00
|
|
|
select ARCH_HAVE_RTC_SUBSECONDS
|
|
|
|
|
2021-05-07 05:28:35 +02:00
|
|
|
config RTC_RPMSG_SERVER
|
2023-10-27 12:56:33 +02:00
|
|
|
bool "The RTC RPMSG Role"
|
2024-02-04 07:30:39 +01:00
|
|
|
depends on RPMSG
|
2021-05-07 05:28:35 +02:00
|
|
|
|
2021-04-24 08:18:21 +02:00
|
|
|
config RTC_RPMSG_SERVER_NAME
|
2023-10-27 12:56:33 +02:00
|
|
|
string "The name of RTC RPMSG Server"
|
2021-04-24 08:18:21 +02:00
|
|
|
depends on RTC_RPMSG
|
|
|
|
---help---
|
2023-10-27 12:56:33 +02:00
|
|
|
The proc name of RTC server. Client requests time from
|
2021-04-24 08:18:21 +02:00
|
|
|
specified name of remote proc.
|
|
|
|
|
2023-11-03 08:44:36 +01:00
|
|
|
config RTC_RPMSG_SYNC_BASETIME
|
|
|
|
bool "Update g_basetime from rpmsg."
|
|
|
|
default n
|
|
|
|
depends on !RTC_RPMSG_SERVER && !CLOCK_TIMEKEEPING
|
|
|
|
---help---
|
|
|
|
Prevent g_basetime differences in multi-core situations.
|
|
|
|
|
2015-02-13 17:30:06 +01:00
|
|
|
endif # RTC
|
|
|
|
|
|
|
|
menuconfig WATCHDOG
|
|
|
|
bool "Watchdog Timer Support"
|
|
|
|
default n
|
|
|
|
---help---
|
|
|
|
This selection enables building of the "upper-half" watchdog timer
|
2015-04-01 20:37:44 +02:00
|
|
|
driver. See include/nuttx/timers/watchdog.h for further watchdog timer driver
|
2015-02-13 17:30:06 +01:00
|
|
|
information.
|
|
|
|
|
|
|
|
if WATCHDOG
|
|
|
|
|
|
|
|
config WATCHDOG_DEVPATH
|
|
|
|
string "Watchdog Device Path"
|
|
|
|
default "/dev/watchdog0"
|
2020-12-21 12:42:00 +01:00
|
|
|
---help---
|
|
|
|
Please, check how your specific chip or board uses this symbol.
|
|
|
|
FYI: It's NOT used by the Auto-monitor feature.
|
2015-02-13 17:30:06 +01:00
|
|
|
|
2023-02-01 11:04:39 +01:00
|
|
|
config WATCHDOG_MAGIC_V
|
2022-12-26 12:28:34 +01:00
|
|
|
bool "Watchdog Device Magic num"
|
2023-01-30 13:55:06 +01:00
|
|
|
default y
|
2022-12-26 12:28:34 +01:00
|
|
|
---help---
|
|
|
|
The watchdog can be stopped by writing 'V' to the watchdog's device node
|
|
|
|
|
2023-07-22 05:44:10 +02:00
|
|
|
config WATCHDOG_PANIC_NOTIFIER
|
|
|
|
bool "Enable watchdog panic notifier"
|
|
|
|
default n
|
|
|
|
---help---
|
|
|
|
When system PANIC, wdog_notifier() will be callled to disable the watchdog,
|
|
|
|
this is an useful option for debug if you want to keep crash scene.
|
|
|
|
|
2020-12-21 12:42:00 +01:00
|
|
|
menuconfig WATCHDOG_AUTOMONITOR
|
2019-01-27 17:03:16 +01:00
|
|
|
bool "Auto-monitor"
|
|
|
|
---help---
|
|
|
|
The auto-monitor provides an OS-internal mechanism for automatically
|
2020-12-21 12:42:00 +01:00
|
|
|
start and repeatedly reset the WDTs that were previous selected.
|
|
|
|
Once the Auto-monitor is enabled, it will reset all
|
|
|
|
registered watchdog timers. If you start a specific WDT, the auto-monitor
|
|
|
|
will stop for that WDT and the application should take care of this from
|
|
|
|
now on.
|
2019-01-27 17:03:16 +01:00
|
|
|
|
|
|
|
if WATCHDOG_AUTOMONITOR
|
|
|
|
|
|
|
|
choice
|
|
|
|
prompt "Auto-monitor keepalive by"
|
2022-09-18 04:18:40 +02:00
|
|
|
default WATCHDOG_AUTOMONITOR_BY_WDOG
|
2019-01-27 17:03:16 +01:00
|
|
|
|
|
|
|
config WATCHDOG_AUTOMONITOR_BY_CAPTURE
|
|
|
|
bool "Capture callback"
|
2022-09-18 23:28:49 +02:00
|
|
|
---help---
|
|
|
|
Feed watchdog through watchdog_ops_s::capture callback periodically
|
2019-01-27 17:03:16 +01:00
|
|
|
|
2022-09-18 06:08:13 +02:00
|
|
|
config WATCHDOG_AUTOMONITOR_BY_ONESHOT
|
|
|
|
bool "Oneshot callback"
|
|
|
|
depends on ONESHOT
|
2022-09-18 23:28:49 +02:00
|
|
|
---help---
|
|
|
|
Feed watchdog through oneshot_lowerhalf_s functions periodically
|
2022-09-18 06:08:13 +02:00
|
|
|
|
2022-09-18 04:47:19 +02:00
|
|
|
config WATCHDOG_AUTOMONITOR_BY_TIMER
|
|
|
|
bool "Timer callback"
|
|
|
|
depends on TIMER
|
2022-09-18 23:28:49 +02:00
|
|
|
---help---
|
|
|
|
Feed watchdog through timer_lowerhalf_s functions periodically
|
2022-09-18 04:47:19 +02:00
|
|
|
|
2022-09-18 04:18:40 +02:00
|
|
|
config WATCHDOG_AUTOMONITOR_BY_WDOG
|
|
|
|
bool "Wdog callback"
|
2022-09-18 23:28:49 +02:00
|
|
|
---help---
|
|
|
|
Feed watchdog through wdog functions periodically
|
2019-01-27 17:03:16 +01:00
|
|
|
|
|
|
|
config WATCHDOG_AUTOMONITOR_BY_WORKER
|
|
|
|
bool "Worker callback"
|
|
|
|
depends on SCHED_WORKQUEUE
|
2022-09-18 23:28:49 +02:00
|
|
|
---help---
|
|
|
|
Feed watchdog through wqueue functions periodically
|
2019-01-27 17:03:16 +01:00
|
|
|
|
|
|
|
config WATCHDOG_AUTOMONITOR_BY_IDLE
|
|
|
|
bool "Idle callback"
|
|
|
|
depends on PM
|
2022-09-18 23:28:49 +02:00
|
|
|
---help---
|
|
|
|
Feed watchdog before idle through pm_callback_s::notify callback
|
2019-01-27 17:03:16 +01:00
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
2020-12-21 12:42:00 +01:00
|
|
|
config WATCHDOG_AUTOMONITOR_TIMEOUT
|
|
|
|
int "Auto-monitor reset timeout(second)"
|
|
|
|
default 60
|
|
|
|
|
2022-09-18 04:47:19 +02:00
|
|
|
if !WATCHDOG_AUTOMONITOR_BY_CAPTURE && !WATCHDOG_AUTOMONITOR_BY_IDLE
|
2020-12-21 12:42:00 +01:00
|
|
|
|
|
|
|
config WATCHDOG_AUTOMONITOR_PING_INTERVAL
|
|
|
|
int "Auto-monitor keep a live interval"
|
2022-09-18 14:38:32 +02:00
|
|
|
range 0 WATCHDOG_AUTOMONITOR_TIMEOUT
|
|
|
|
default 0
|
2020-12-21 12:42:00 +01:00
|
|
|
---help---
|
2022-09-18 14:38:32 +02:00
|
|
|
If the interval is 0, it will change to (WATCHDOG_AUTOMONITOR_TIMEOUT / 2).
|
|
|
|
This interval will only be used by auto-monitor in oneshot, timer, wdog or
|
|
|
|
worker case.
|
2020-12-21 12:42:00 +01:00
|
|
|
|
2022-09-18 04:47:19 +02:00
|
|
|
endif # !WATCHDOG_AUTOMONITOR_BY_CAPTURE && !WATCHDOG_AUTOMONITOR_BY_IDLE
|
2020-12-21 12:42:00 +01:00
|
|
|
|
2019-01-27 17:03:16 +01:00
|
|
|
endif # WATCHDOG_AUTOMONITOR
|
|
|
|
|
2015-02-13 17:30:06 +01:00
|
|
|
endif # WATCHDOG
|
2015-04-02 21:00:10 +02:00
|
|
|
|
|
|
|
config TIMERS_CS2100CP
|
|
|
|
bool "CS2100-CP Fraction-N Clock Multiplier"
|
|
|
|
depends on I2C
|
|
|
|
|
|
|
|
if TIMERS_CS2100CP
|
|
|
|
|
|
|
|
config CS2100CP_DEBUG
|
|
|
|
bool "Enable CS2100-CP Debug Features"
|
2016-06-11 22:14:08 +02:00
|
|
|
depends on DEBUG_FEATURES
|
2015-04-02 21:00:10 +02:00
|
|
|
|
|
|
|
config CS2100CP_REGDEBUG
|
|
|
|
bool "Enable CS2100-CP Register Debug"
|
2016-06-11 22:14:08 +02:00
|
|
|
depends on DEBUG_FEATURES
|
2015-04-02 21:00:10 +02:00
|
|
|
|
|
|
|
endif # TIMERS_CS2100CP
|
2023-05-22 12:20:06 +02:00
|
|
|
endmenu # Timer Driver Support
|