Updates the hal_adi revision to the latest, picking up changes for usb,
dual core, and secure boot.
Signed-off-by: Maureen Helm <maureen.helm@analog.com>
Some modem's reply "NO CARRIER" on the ATD command, until we are
connected to the network. This causes first dial-up attempt to fail.
When waiting for retry-timer, we might receive "+CEREG:" or "+CGEV:"
events, indicating that we are connected.
We should re-trigger the dial-up script immediately, instead of waiting
for timer.
When the dial up script succeed, we don't anymore receive "+CEREG" so
that should be handled in await_registered state.
Signed-off-by: Seppo Takalo <seppo.takalo@nordicsemi.no>
The DBI configuration was incorrectly using bitwise OR to set the
color_coding field instead of direct assignment. The 'mode' field
was being used when 'color_coding' should have been set.
Signed-off-by: Kate Wang <yumeng.wang@nxp.com>
In the function mc_cgm_clock_control_on, in first switch-case
was added a default-case which returns -ENOTSUP.
The fist switch-case is followed by two switch-cases (for adc, lpcmp),
and one if-condition (for tempsens).
If none of the cases in the first switch is fulfilled,
(e.g. trying to enable clock for adc) function early returns -ENOTSUP,
and the rest of the code becomes UNREACHABLE.
This bugfix groups all the switches and the if-condition (for tempsens),
in one main switch and keeps the return ENOTSUP as the default case,
considering that this return was added for a reason.
Signed-off-by: Martin Martincek <martin.martincek@nxp.com>
Apply PINCTRL_STATE_SLEEP on suspend and PINCTRL_STATE_DEFAULT
on resume. If a sleep pinctrl state is defined in the board DTS,
pins will be reconfigured on suspend. If not defined, the call
is a no-op.
Signed-off-by: Jacob Wienecke <jacob.wienecke@nxp.com>
Apply PINCTRL_STATE_SLEEP on suspend and PINCTRL_STATE_DEFAULT
on resume. If a sleep pinctrl state is defined in the board DTS,
pins will be reconfigured on suspend. If not defined, the call
is a no-op.
Signed-off-by: Jacob Wienecke <jacob.wienecke@nxp.com>
Apply PINCTRL_STATE_SLEEP on suspend and PINCTRL_STATE_DEFAULT on resume
so that pins are in low-power configuration if defined in the dts
Signed-off-by: Jacob Wienecke <jacob.wienecke@nxp.com>
Apply PINCTRL_STATE_SLEEP on suspend and PINCTRL_STATE_DEFAULT on resume
to ensure pins take on the DTS defined sleep state if one is defined.
TURN_ON already applies PINCTRL_STATE_DEFAULT (could be removed
potentially). RESUME handles the case where the device suspends without
full power-off.
Signed-off-by: Jacob Wienecke <jacob.wienecke@nxp.com>
Apply PINCTRL_STATE_SLEEP on suspend and PINCTRL_STATE_DEFAULT on resume
so that pin configuration is updated for low power modes.
Previously the suspend and resume actions were empty, leaving pins in
their active configuration during sleep. On SoCs like RW6xx where pad
control registers survive low power modes, this allos boards to define
sleep pinctrl states with appropriate pull or drive setting s to minimize
leakage.
Signed-off-by: Jacob Wienecke <jacob.wienecke@nxp.com>
The RW612 will enter PM_STATE_RUNTIME_IDLE mode when idle but the
average current is higher than expected. The expected current should be
around 15mA but the actual current is nearly 18mA.
By disabling AVPLL and TDDR clock in clock_init, the current of
PM_STATE_RUNTIME_IDLE mode is ok, which is around 15.5mA
Signed-off-by: Hui Bai <hui.bai@nxp.com>
Fix broken FS26 watchdog field extraction and refresh checks.
Correct the device status macro, simple watchdog write error
handling, related register field helper macros, and use integer
duty-cycle values when selecting the watchdog window.
Signed-off-by: Yves Wang <zhengjia.wang@nxp.com>
Select the ECDHE-RSA ciphersuite to enable TLS 1.2 protocol
support. This was missed when commit c879937755 updated other
TLS samples to use ciphersuite Kconfigs after the removal of
implicit crypto feature selection from NET_SOCKETS_SOCKOPT_TLS.
Without this, the build fails with implicit declaration errors
for mbedtls_ssl_get_session() and mbedtls_ssl_set_session(),
as MBEDTLS_SSL_CLI_C is never defined.
Signed-off-by: Sylvio Alves <sylvio.alves@espressif.com>
implement configure_ramp api
drop set_max_velocity and set_max_acceleration from
stepper_tmcm3216.h
Signed-off-by: Jilay Pandya <jilay.pandya@outlook.com>
Function for calculating acceleration in the timebase of
the motion controller using clock_frequency and input
acceleration in Hz/s
Signed-off-by: Jilay Pandya <jilay.pandya@outlook.com>
Make usage of the macro VIDEO_FMT_IS_YUV/RGB/BAYER in order to
check the colorspace of a format.
Signed-off-by: Alain Volmat <alain.volmat@foss.st.com>
Add categories of pixel formats along with macros to detect
whether a pixel format is part of that category.
This can be used to detect multiple properties in a
maintainable way.
Signed-off-by: Josuah Demangeon <me@josuah.net>
The API documentation does not match the implementation behavior. When
`overwrite` is false, the function always lengthens the buffer. The
position of the cursor has no effect. The function always advances the
cursor position, so mention this first.
Signed-off-by: Cesar Vandevelde <cesar.vandevelde@gmail.com>
When writing a full-screen with a single buffer, stm32_ltdc_write() calls
stm32_ltdc_sync_frame() which resets the semaphore, sets the given buffer
to pend_buf, enables LTDC line interrupt and waits for the semaphore to be
given. However, the semaphore is never given by stm32_ltdc_global_isr()
because it skips given it when front_buf != pend_buf which is the case
because they are the same because there is just a single buffer and
front_buf == pend_buf.
The solution is not to call stm32_ltdc_sync_frame() when the same buffer is
used.
Signed-off-by: Ilia Kharin <akscram@gmail.com>
When stm32_ltdc_sync_frame() is called, it resets a semaphore, enables LTDC
line interrupt and waits until the semaphore is given. When the interrupt
occurs, stm32_ltdc_global_isr() is invoked and it gives the semaphore only
when front_buf != pend_buf. That is, if stm32_ltdc_sync_frame() is called
with pend_buf equal to front_buf, it would wait forever for the semaphore
to be given. Hence, a deadlock occurs. In order to catch such situation,
an assert is added in stm32_ltdc_sync_frame() when it's called with
pend_buf which is equal to front_buf.
Signed-off-by: Ilia Kharin <akscram@gmail.com>
Add policy to keep the open pull request list focused on contributions
that are actively progressing and have a realistic path to merge.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
1.The color_coding in mipi_dbi_config shall not be extracting it from
the bus_type field and shall have dedicated color_coding field.
2.Update device tree binding to include pinctrl support and
declare mipi-dbi bus compatibility.
Signed-off-by: Kate Wang <yumeng.wang@nxp.com>
Added is31fl3197@50 to overlay
Also updated GIGA board yaml file to say that it supports i2c
And updated sample to mention it
Signed-off-by: Kurt Eckhardt <kurte@rockisland.com>
Removed the driver knowing anything about what color each channel is.
When you output to an LED with a buffer it simply writes the
channels out with buffer.
Also removed the assumptions that the leds are either
a) RGB or b) 3 channels and instead use them the way they are defined.
That is for example if we have 4 channels, we could define an LED
with just one color in it and we could define another with three.
The user can define 4 leds each with color yellow.
For each LED it counts how many buffers were used by previous LEDs and
starts there and outputs N channels.
Decided it looked cleaner to use helper function write channels, so
implemented it and added it to the call table.
Updated sample:
It manually computes which channel maps to red, green and blue and then
uses those indexes to map the table of colors to the right channels.
Signed-off-by: Kurt Eckhardt <kurte@rockisland.com>
more refactoring, don't use the 94 registers everywhere.
Introduce structure, with registers and fixed values, and use it.
Signed-off-by: Kurt Eckhardt <kurte@rockisland.com>
In preparation to allow this driver to support more than
one IS31FL319x object such as ...97, rename the
source file and the functions to make them more
generic.
I also changed the enumeration/creation of object
to generate the right names for the current 94 objects
Renamed the Kconfig file. Updated CMakeLists.txt to
check for different condition to build source file
The samples driver is31fl3194 was also renamed to
is31fl319x. All of the references to use 9x instead
of 94. The updated sample required an update to the
doc script redirect.py to reflect the new name.
Signed-off-by: Kurt Eckhardt <kurte@rockisland.com>
