OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/subsys/emul/Kconfig

40 lines
1.1 KiB
Plaintext
Raw Normal View History

emul: Create an emulation implementation Create a header file and implementation for emulators. Set up a linker list so that emulators can be found and initialised at start-up. Emulators are used to emulate hardware devices, to support testing of various subsystems. For example, it is possible to write an emulator for an I2C compass such that it appears on the I2C bus and can be used just like a real hardware device. Emulators often implement special features for testing. For example a compass may support returning bogus data if the I2C bus speed is too high, or may return invalid measurements if calibration has not yet been completed. This allows for testing that high-level code can handle these situations correctly. Test coverage can therefore approach 100% if all failure conditions are emulated. Signed-off-by: Peter Bigot <peter.bigot@nordicsemi.no> Signed-off-by: Simon Glass <sjg@chromium.org>
2020-08-20 22:07:29 +08:00
# Emulator configuration options
# Copyright 2020 Google LLC
# SPDX-License-Identifier: Apache-2.0
#
# Emulator options
#
menuconfig EMUL
bool "Emulation drivers"
help
Enable Emulation Driver Configuration
These drivers are used to emulate hardware devices, to support testing
of various subsystems. For example, it is possible to write an
emulator for an I2C compass such that it appears on the I2C bus and
can be used just like a real hardware device.
Emulators often implement special features for testing. For example
a compass may support returning bogus data if the I2C bus speed is
too high, or may return invalid measurements if calibration has not
yet been completed. This allows for testing that high-level code can
handle these situations correctly. Test coverage can therefore
approach 100% if all failure conditions are emulated.
if EMUL
config EMUL_INIT_PRIORITY
int "Init priority"
default 60
help
Emulation device driver initialisation priority.
module = EMUL
module-str = emul
source "subsys/logging/Kconfig.template.log_config"
emul: Add an emulator for the eSPI Host This emulator pretends a generic eSPI Host. It supports basic virtual wires and port80 operations. There are functions to trigger actions on the host side e.g. for setting a virtual wire from the host to the eSPI slave, use emul_espi_host_send_vw. It will prepare data and set a proper event on the slave side which will trigger callback (if there is any). Signed-off-by: Dawid Niedzwiecki <dn@semihalf.com>
2020-12-16 22:08:59 +08:00
source "subsys/emul/espi/Kconfig"
emul: Add an emulator for the Atmel AT24 series This emulator supports basic reads and writes with 8-bit addressing. It connects itself to any AT24 devices it finds in the device tree. The I2C emulation controller driver is used to direct I2C messages from the AT24 driver to the AT24 emulator. Signed-off-by: Simon Glass <sjg@chromium.org> Signed-off-by: Peter Bigot <peter.bigot@nordicsemi.no>
2020-08-20 22:11:24 +08:00
emul: Create an emulation implementation Create a header file and implementation for emulators. Set up a linker list so that emulators can be found and initialised at start-up. Emulators are used to emulate hardware devices, to support testing of various subsystems. For example, it is possible to write an emulator for an I2C compass such that it appears on the I2C bus and can be used just like a real hardware device. Emulators often implement special features for testing. For example a compass may support returning bogus data if the I2C bus speed is too high, or may return invalid measurements if calibration has not yet been completed. This allows for testing that high-level code can handle these situations correctly. Test coverage can therefore approach 100% if all failure conditions are emulated. Signed-off-by: Peter Bigot <peter.bigot@nordicsemi.no> Signed-off-by: Simon Glass <sjg@chromium.org>
2020-08-20 22:07:29 +08:00
endif