Fix the compile error when input driver is enabled.
Error message:
In file included from zephyr/zephyr/include/zephyr/sys/util_macro.h:34,
from zephyr/zephyr/include/zephyr/irq_multilevel.h:15,
from zephyr/zephyr/include/zephyr/devicetree.h:20,
from zephyr/zephyr/include/zephyr/device.h:12,
from zephyr/zephyr/drivers/input/input_gpio_keys.c:9:
zephyr/zephyr/include/zephyr/toolchain/gcc.h:87:36:
error: static assertion failed:
"zephyr-code must be specified to use the input-gpio-keys driver"
Signed-off-by: Jason Yu <zejiang.yu@nxp.com>
Let's use the native_posix entropy driver by now,
as the real target relies on the PSA one, and we
currently do not have plans to include that.
Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
This is not yet possible.
So let's add a check that provides an easy to understanding
error message instead of a bunch of kconfig and build warnings.
Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
These tests run fine in this board, let's provide an
overlay and enable them.
Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
By default, the QSPI region is marked as EXTMEM and inaccessible
(see #57467), mark the first 64MB as IO on stm32f769i_disco.
Signed-off-by: Armin Brauns <armin.brauns@embedded-solutions.at>
According to the datasheet, fRSCLK (Clock Frequency for READ instructions)
is 66MHz; it doesn't mention 72MHz anywhere.
Signed-off-by: Armin Brauns <armin.brauns@embedded-solutions.at>
Access to this region should no longer be requested via UICR, because it
will be statically reserved by secure domain firmware.
Signed-off-by: Grzegorz Swiderski <grzegorz.swiderski@nordicsemi.no>
The gpio-emul driver does not actually require any reg property,
since it is not in the physical memory map of any device. So
let's remove that property from the bindings.
Signed-off-by: Chris Friedt <cfriedt@tenstorrent.com>
Remove all CAN controller "bus-speed" and "bus-speed-data"
properties. These all use the default bitrates set via Kconfig.
Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
SDHC twister tag indicates that the board supports an SD host controller
driver. Since the ST SDMMC support is provided directly via a disk
driver, SDHC tests are not supported on ST boards. Drop this tag in
order to avoid twister failures running the SDHC tests on these
platforms.
Signed-off-by: Daniel DeGrasse <daniel.degrasse@nxp.com>
PHYTEC has multiple offices in different locations like
the US, France, India and China. The headquarter is located in
Germany. Since now 50% of the PHYTEC boards are from the US
office, we should drop 'Messtechnik GmbH', which is the offical
title of the German office, and keep the name more general.
Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
This commit should add all the functionality needed for the entropy
driver to work when PM is enabled.
Signed-off-by: Ioannis Karachalios <ioannis.karachalios.px@renesas.com>
It is enough to test watchdog driver on the application core.
Otherwise, at least three samples/tests fail due to missing
overlay file for nrf54h20dk/nrf54h20/cpurad.
Signed-off-by: Sebastian Głąb <sebastian.glab@nordicsemi.no>
On this board, the CAN transceivers are not GPIO controlled, but passive,
and should not be represented by the "can-transceiver-gpio" compatible (as
this leads to driver compilation warnings due to missing GPIO properties).
Fixes: c8faa1e380
Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
This commit makes the devicetrees of the targets that are based on the QEMU
`virt` machine more consistent with the rest of the RISC-V targets in
Zephyr by:
* adding the `riscv,isa` property
* adding a compatible string which uniquely identifies the `virt` core
Signed-off-by: Filip Kokosinski <fkokosinski@antmicro.com>
Add support for USDHC0 controller on FRDM_MCXN947 board. This support
was verified using the `tests/subsys/sd/sdmmc` and
`tests/subsys/sd/sdio` testcases. Note that this board does not ship
with the SD header (J12) populated by default, so the user must populate
one.
Signed-off-by: Daniel DeGrasse <daniel.degrasse@nxp.com>
The CSI can connect to either a camera sensor (as on i.MX RT10xx) or
a MIPI CSI-2 receiver (as on i.MX RT11xx). To be generic, change the
naming from sensor to source.
Signed-off-by: Phi Bang Nguyen <phibang.nguyen@nxp.com>
This commit should add all the functionality needed for the DISPLAY
driver to work when PM is enabled.
Signed-off-by: Ioannis Karachalios <ioannis.karachalios.px@renesas.com>
Enable PXP on RT1050 EVK, and apply LVGL settings optimized for PXP
support. These settings will enable PXP rotation to function as expected
when using LVGL with the RT1050.
Signed-off-by: Daniel DeGrasse <daniel.degrasse@nxp.com>
The naming of these two options was problematic, since it's both of them
are about vendor extensions, even though one has _EXT in the name and
the other doesn't. Just merge one option into the other. This has a
slight overhead on the controller side of enabling some more vendor
features if BT_HCI_VS is enabled, but that should hopefully be
acceptable.
Signed-off-by: Johan Hedberg <johan.hedberg@gmail.com>
Pin muxing for i2c6 and csi should be separated as i2c is initialized
before csi. Otherwise, i2c6 bus device will not be ready when the
camera sensor on this bus initializes.
Signed-off-by: Phi Bang Nguyen <phibang.nguyen@nxp.com>
esp32s3 contains 2 cpus: procpu and appcpu.
appcpu has very limited peripherals support for now.
This updated esp32s3_touch board to list only support peripherals.
Signed-off-by: Sylvio Alves <sylvio.alves@espressif.com>
This board uses a ULPI PHY to provide HS (USB 2.0) connectivitiy instead of
the internal PHY, which only supports FW (USB 1.x).
Signed-off-by: Armin Brauns <armin.brauns@embedded-solutions.at>
Configure to use XMCD as the bootheader by default instead of DCD. As
XMCD gives a better SDRAM memory access speed.
As an example, the Pixel Processing Pipeline is 13 ms faster with XMCD
compared to DCD as the bootheader.
Signed-off-by: Trung Hieu Le <trunghieu.le@nxp.com>
Currently, only DCD bootheader was supported to configure the SDRAM.
On IMX RT1170, XMCD can be used as an alternative boot header to DCD.
XMCD is more advanced than DCD and enhances SDRAM access speed.
This is benefit for SDRAM access application.
Signed-off-by: Trung Hieu Le <trunghieu.le@nxp.com>
Adds chain length and colour mapping properties to LED strip devices
on boards where these parameters are now required
Signed-off-by: Jamie McCrae <spam@helper3000.net>
Add the possibility to flash nucleo-f746zg board using west
STM32CubeProgrammer runner.
Signed-off-by: Abderrahmane Jarmouni <abderrahmane.jarmouni-ext@st.com>
This commit is to fix some GPIO test case build issue:
https://github.com/zephyrproject-rtos/zephyr/issues/72619
In fact, the issue is introduce by expander GPIO PR:
https://github.com/zephyrproject-rtos/zephyr/pull/69330
It is used to add GPIO expander support, in this PR, dts node layout is:
lpi2c {
MFD driver {
gpio driver {
}
}
}
The initial idea is to disable all these node by default in order to keep
a minimal default image, but expander GPIO PR only disabled lpi2c and MFD
driver node, but enabled gpio driver node, so gpio driver will report
building error as it depends on expander and i2c which are disabled, so
this fix is to disable gpio node. If we want to use expander gpio, we
need to enable i2c, expander and gpio nodes simultaneously.
Some GPIO test cases have been enabled on i.mx93 EVK board by enabling
onchip GPIO controller in the overlay, for example:
tests/drivers/gpio/gpio_basic_api/boards/imx93_evk_mimx9352_a55.overlay
Signed-off-by: Jiafei Pan <Jiafei.Pan@nxp.com>
Include 'zephyr,bt-c2h-uart' in 'chosen' node to make it possible to use
HCI raw mode over UART. This was tested on real board with 'hci_uart'
sample, with Linux machine as a host (kernel 6.8, BlueZ 5.75).
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
