OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/drivers/sensor/tdk/mpu9250/Kconfig

61 lines
1.3 KiB
Plaintext
Raw Normal View History

sensors: Implement MPU9250 driver MPU9250 driver for 9-axis gyroscope, accelerometer, magnetometer Signed-off-by: Dominik Chat <dominik.chat@nordicsemi.no>
2021-11-26 17:22:54 +08:00
# MPU9250 Nine-Axis Motion Tracking device configuration options
# Copyright (c) 2021 Nordic Semiconductor ASA
# SPDX-License-Identifier: Apache-2.0
menuconfig MPU9250
bool "MPU9250 Nine-Axis Motion Tracking Device"
drivers: sensor: Update drivers to use devicetree Kconfig symbol Update sensor drivers to use DT_HAS_<compat>_ENABLED Kconfig symbol to expose the driver and enable it by default based on devicetree. Signed-off-by: Kumar Gala <galak@kernel.org>
2022-07-20 11:41:45 +08:00
default y
depends on DT_HAS_INVENSENSE_MPU9250_ENABLED
drivers: sensor: Convert Kconfig bus 'depends on' to 'select' This change in pattern is meant to address a misconfiguration issue that can occur for sensors that support being on multiple busses like I2C & SPI. For example, you can have a configuration in which such a sensor is on the I2C bus in the devicetree and the sensor is enabled. However the application configuration enables CONFIG_SPI=y and CONFIG_I2C=n and this will cause the sensor driver to be built by default, however since we don't have the I2C bus enabled the driver will not compile correctly. Previously we had been adding to board Kconfig.defconfig something like: config I2C default y if SENSOR This pattern doesn't scale well and may differ from what an application specific need/use is. So instead move to a pattern in which we leave the default enablement up to the devicetree "status" property for the sensor. We then have the Kconfig move from 'depends on <BUS>' to 'select <BUS>' and in the case of drivers that support multiple busses we have the Kconfig be: 'select <BUS> if $(dt_compat_on_bus,$(<DT_COMPAT>),<BUS>) for each bus type the sensor supports. This removes the need to add Kconfig logic to each board and enables the bus subsystem and bus controller driver if the sensor requires it by default in the build system. Fixes: #48518 Signed-off-by: Kumar Gala <galak@kernel.org>
2022-08-04 23:55:31 +08:00
select I2C
sensors: Implement MPU9250 driver MPU9250 driver for 9-axis gyroscope, accelerometer, magnetometer Signed-off-by: Dominik Chat <dominik.chat@nordicsemi.no>
2021-11-26 17:22:54 +08:00
help
Enable driver for MPU9250 I2C-based nine-axis motion tracking device.
if MPU9250
choice
prompt "Trigger mode"
default MPU9250_TRIGGER_GLOBAL_THREAD
help
Specify the type of triggering to be used by the driver.
config MPU9250_TRIGGER_NONE
bool "No trigger"
config MPU9250_TRIGGER_GLOBAL_THREAD
bool "Use global thread"
depends on GPIO
select MPU9250_TRIGGER
config MPU9250_TRIGGER_OWN_THREAD
bool "Use own thread"
depends on GPIO
select MPU9250_TRIGGER
endchoice
config MPU9250_TRIGGER
bool
config MPU9250_THREAD_PRIORITY
int "Thread priority"
depends on MPU9250_TRIGGER_OWN_THREAD
default 10
help
Priority of thread used by the driver to handle interrupts.
config MPU9250_THREAD_STACK_SIZE
int "Thread stack size"
depends on MPU9250_TRIGGER_OWN_THREAD
default 1024
help
Stack size of thread used by the driver to handle interrupts.
config MPU9250_MAGN_EN
bool "Magnetometer enable"
default y
help
Enable AK8963 builtin magnetometer.
endif # MPU9250