drivers: sensor: bmi323: Add i2c support #1
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Document the changes to the ZBus function `zbus_chan_add_obs`. Signed-off-by: Jordan Yates <[email protected]>
Use underlying Zephyr thread directly to store thread name instead of storing the name in CMSIS control block. Also, allow `osThreadGetName` to work within ISR, as expected from spec. Signed-off-by: Utsav Munendra <[email protected]>
Instead, just store the pointer to the string provided as part of the RTOS object init attributes. Signed-off-by: Utsav Munendra <[email protected]>
Add test cases where spi_transceive gets NULL spi_buf_set once for tx and once for rx. Signed-off-by: Piotr Krzyzanowski <[email protected]>
1. add uart support 2. enable the uart_async_api test example Signed-off-by: Peter Wang <[email protected]>
1. enable flash support 2. verified test/driver/flash Signed-off-by: Peter Wang <[email protected]>
As it is a common pattern for drivers performing writes (e.g: write reg-addr + write reg-data) without having to memcpy both into a buffer. Signed-off-by: Luis Ubieda <[email protected]>
This patch establishes proper handling of RTIO OPs with multiple write requests in the same transfer (as in: including OP_TRANSACTION flag). An example of this is captured in test_ram_rtio_write_with_transaction test). This patch makes that testcase pass for i2c_nrfx_twi_rtio. Signed-off-by: Luis Ubieda <[email protected]>
- In middleware/CMakeLists.txt, using add_subdirectory()
to load the cmakelists.txt under bt_controller will
result in the bt_controller directory not being found
correctly, because the starting point of the query
is mcux-sdk-ng/CMakeLists.txt. Need to add
${CMAKE_CURRENT_LIST_DIR} to bt_controller to correctly
locate the folder.
Signed-off-by: Zhaoxiang Jin <[email protected]>
Brings some commits from the upstream TF-M which introduce nRF54L10 ns support. Signed-off-by: Georgios Vasilakis <[email protected]>
Update the header to include a generic header for the NRF54L series and not a specific one for the NRF54L15. Signed-off-by: Georgios Vasilakis <[email protected]>
This adds the nrf54l15dk/nrf54l10/cpuapp/ns board variant to
Zephyr. It allows to build applications for this target.
This is an initial support for the non secure target which allows
building and running tfm_ipc and config_build.
This is NOT full support of the non secure target in upstream
Zephyr.
There are important limitations, such as:
- The hardware Crypto accelerator is not supported and thus the non
secur target is NOT secure for production applications in upstream
Zephyr.
- The BL2 is not supported, so no DFU is supported with this support
Most of the code changes here are taken from nRF Connect SDK
in order to avoid having noups there.
Signed-off-by: Georgios Vasilakis <[email protected]>
Add nRF54L10 non secure target for the config_build and the tfm_ipc samples. Signed-off-by: Georgios Vasilakis <[email protected]>
The ADC and watchdog samples are not currently supported for the non secure target of the nRF54L10 DK. Add exclusions for these until they are supported. Signed-off-by: Georgios Vasilakis <[email protected]>
It seems that some copyrights were not udpated to Apache-2.0 as they should have been so this commit updates them. Signed-off-by: Georgios Vasilakis <[email protected]>
- Added support for background scan and configured the default values of BG scan configuration Signed-off-by: Nitin Pandey <[email protected]>
- Verified and configured scan dwell time for active, passive and advance scan Signed-off-by: Nitin Pandey <[email protected]>
- Defined Kconfig macros for Roam config - Added set roam configuration API call after BGSCAN Signed-off-by: Nitin Pandey <[email protected]>
Update the kernel API doxygen for k_thread_stack_alloc() and k_thread_create() to convey that kernel thread stacks may be dynamically allocated as an alternative to static allocation. Signed-off-by: Chris Friedt <[email protected]>
Add documentation to indicate that, aside from static thread stack allocation, Zephyr supports dynamically allocated thread stacks. Signed-off-by: Chris Friedt <[email protected]>
Update the driver to account for variations in the SDK driver when it uses the instance number instead of the base address. Applying 49bdcd2 on RTIO-version. Co-authored-by: Mahesh Mahadevan <[email protected]> Signed-off-by: Luis Ubieda <[email protected]>
Some NXP SoC's have a FlexComm interface that manages the interrupts. Applying 482e39e on RTIO-version. Authored-by: Mahesh Mahadevan <[email protected]> Signed-off-by: Luis Ubieda <[email protected]>
The Low Power Flexcomm driver manages the interrupt handling and provides an API to register interrupt callbacks. Register the NXP LPI2C interrupt handler. Applying dca6e64 on RTIO-version. Authored-by: Mahesh Mahadevan <[email protected]> Signed-off-by: Luis Ubieda <[email protected]>
Determine if lpflexcomm wrapped lpi2c by instance and connect irq differently dependending on that to support platforms with both flexcomm wrapped and unwrapped lpi2c's. Applying c1286a8 to RTIO version. Authored-by: Declan Snyder <[email protected]> Signed-off-by: Luis Ubieda <[email protected]>
Require latest python version for Setup Zephyr Project step. Signed-off-by: Okan Sahin <[email protected]>
This reverts commit fe32d05. A supported host, 52840 does not support 16MHz SPI (though it falls back to 8M) but prioritize interoperability over performance. Signed-off-by: Chaitanya Tata <[email protected]>
Flexcomm3 is used for the mikrobus header, enable the clock for it and setup a pinctrl group for i2c. Signed-off-by: Tom Burdick <[email protected]>
Add tachometer driver for Realtek rts5912. Signed-off-by: Jhan BoChao <[email protected]>
DAC pins are not defined for SAM V71(B) Xplained Ultra - this was causing device initialization to fail. This commit fixes that. Signed-off-by: Dhanesh S R <[email protected]>
Implement watchdog driver for ITE it51xxx series chip. Signed-off-by: Ruibin Chang <[email protected]>
Adds missing groupings for non-secure board targets Signed-off-by: Jamie McCrae <[email protected]>
V-Tiled displays need different treatment when getting the glyph byte. Signed-off-by: Yishai Jaffe <[email protected]>
The flash size is the second part (size) of the first reg value, not the first part (address) of a nonexistent second reg value. Based-on-patch-by: Armin Brauns <[email protected]> Signed-off-by: Tim Pambor <[email protected]>
Like other nRF54L series products, the radio on 54l20 supports CS. Signed-off-by: Olivier Lesage <[email protected]>
- Sets MAIN_STACK_SIZE in prj.conf to 2048 (default is 1024) to avoid possible stack overflow and adding new .conf files per board. - Deletes existing board .conf files, as they are not needed anymore. Signed-off-by: Andrej Butok <[email protected]>
The required jlink script was not added due to missing entry in the board check. Also change the check for app vs rad to be on SOC level. Signed-off-by: Håkon Amundsen <[email protected]>
- add uart support - enable the uart_async_api test example Signed-off-by: Neil Chen <[email protected]>
- enable flash support - verified tests/drivers/flash/common Signed-off-by: Neil Chen <[email protected]>
Don't `imply POSIX_MESSAGE_PASSING` when `POSIX_API=y` as this option has a non-trivial RAM implication in `HEAP_MEM_POOL_ADD_SIZE_MQUEUE`. The `mq_*` API is minimally used in-tree, with all users already enabling the symbol directly. Signed-off-by: Jordan Yates <[email protected]>
`pthread_setspecific` requires a stack in order to allocate the `struct pthread_key_data` data structure. On 64 bit systems this data structure is 32 bytes, resulting in 160 bytes usage for the default 5 supported threads. Signed-off-by: Jordan Yates <[email protected]>
The device tree entry for cva6 is currently missing a device tree node for the mtime and mtimecmp registers in the core-local interrupt controllers. This causes the RISC-V machine timer driver not to be built, causing build failures as the system clock is missing. This commit rectifies this by adding the corresponding device tree entry. Signed-off-by: Eric Ackermann <[email protected]>
In hardware, cva6 currently only provides global disable/enable functions for the Dcache and Icache. Disabling and re-enabling them also has the effect of flushing and invalidating the cache. Future cva6 SoCs will add support RISC-V's standardized cache management operations. This commit provides a default implementation for all methods currently part of the cache API. These implementations can be overwritten at board or SoC level, as they use weak linking. Signed-off-by: Eric Ackermann <[email protected]>
This commit adds the necessary configurations for building and testing cva6 boards (cv64a6_genesys_2, cv32a6_genesys_2) with twister. This has been validated against commit 8a9d7a832b7121dd6f9be61a380d1d89ebf2a5f3 of the cva6 hardware project. Signed-off-by: Eric Ackermann <[email protected]>
The original commit uses the incorrect value 42 for CONFIG_MAX_IRQ_PER_AGGREGATOR for the cva6 family of SoCs, which is the total number of IRQs in the system. This commit corrects this to 30, the number of IRQs for the PLIC. Signed-off-by: Eric Ackermann <[email protected]>
The nullpointer address (0x0) is mapped to the debug module in cva6, making it a valid address. Thus, in the coredump test, trigger an exception using k_panic() instead. Signed-off-by: Eric Ackermann <[email protected]>
In the default configuration, cv32a6 does not have an FPU and does not implement RISC-V's F and D extensions. Hence, the FPU flags should not be added. In the future, a second SoC for cv32a6 systems with FPU can be added. Signed-off-by: Eric Ackermann <[email protected]>
Provide proper adaptions as bootloader ROM offset, flash load offset and dts definitions for the nRF54H20 iron board to make it ready for the MCUBoot bootloader. Signed-off-by: Michal Kozikowski <[email protected]>
Adding sample configuration for nRF54H20dk 'iron' board. Signed-off-by: Michal Kozikowski <[email protected]>
Create new group for debugging and move all debugging APIs under this group. Signed-off-by: Anas Nashif <[email protected]>
Move under logging group. Signed-off-by: Anas Nashif <[email protected]>
This one appears in the top level of doxygen and should not be exposed as a Zephyr API. Signed-off-by: Anas Nashif <[email protected]>
move from currently top level to sensors where it is defined. Signed-off-by: Anas Nashif <[email protected]>
Those are no kernel permitives and belong under os services. Signed-off-by: Anas Nashif <[email protected]>
Add some clarity to some of the groups using @brief. Signed-off-by: Anas Nashif <[email protected]>
Move usermode mutex/semaphore under the usermode group. Signed-off-by: Anas Nashif <[email protected]>
- Remove duplicated conf/.overlay configuration for mimmxrt1170_evk A and B revisions that have the same content. - No change if .conf/.overlay have different content. Signed-off-by: Andrej Butok <[email protected]>
use phy_configure_link() instead of phy_api->cfg_link(). Signed-off-by: Fin Maaß <[email protected]>
Update the HW models module to:
d5b95fdd0260e8189e788d40d2863d1e2d4be159
Including the following:
d5b95fd grtc hal replacement: Fix bug in nrf_grtc_int_group_enable/
disable()
5f3641d GRTC: With a CC in the past evaluate immediately
Signed-off-by: Alberto Escolar Piedras <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.