michaelh/zephyr
1
0
Fork 0
Code Releases Activity
zephyr/drivers/sensor/sbs_gauge/Kconfig

14 lines
370 B
Plaintext
Raw Permalink Normal View History

drivers: sensors: smart-battery with SBS 1.1 compliant fuel gauge Implementation of a SBS 1.1 compliant fuel gauge driver Signed-off-by: MORGER Patrick <patrick.morger@leica-geosystems.com>
2021-04-08 08:46:34 +02:00
# Copyright (c) 2021 Leica Geosystems AG
# SPDX-License-Identifier: Apache-2.0
config SBS_GAUGE
bool "Smart Battery Fuel Gauge"
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 05:41:45 +02:00
default y
depends on DT_HAS_SBS_SBS_GAUGE_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 17:55:31 +02:00
select I2C
drivers: sensors: smart-battery with SBS 1.1 compliant fuel gauge Implementation of a SBS 1.1 compliant fuel gauge driver Signed-off-by: MORGER Patrick <patrick.morger@leica-geosystems.com>
2021-04-08 08:46:34 +02:00
help
Enable I2C-based/SMBus-based driver for a Smart Battery Fuel Gauge.
emul: Cleanup emul directory Avoid implementations in the subsys emul directory to keep the directory focused on emulator subsystem instead of consumers. Consumers should be implemented side-by-side to their drivers Signed-off-by: Yuval Peress <peress@google.com>
2023-01-24 18:12:18 +01:00
emul: Fuel gauge tests direct access to emul_sbs The fuel gauge tests should *not* have to enable CONFIG_SENSOR in order to get access to the sbs gauge emulator. Allow fuel_gauge sbs_gauge direct access to emul_sbs_gauge.c Signed-off-by: Aaron Massey <aaronmassey@google.com>
2023-04-14 22:39:52 +02:00
# Maintain access to emul_sbs_gauge.
source "drivers/fuel_gauge/sbs_gauge/Kconfig.emul_sbs_gauge"
Copy permalink