1. the MCXA family use MRCC to reset peripheral
2. MRCC register, 0: hold in reset, 1: release from reset
3. usage as blow
syscon: syscon@xxx {
...
reset: reset {
compatible = "nxp,mrcc-reset";
#reset-cells = <1>;
};
};
Signed-off-by: Peter Wang <chaoyi.wang@nxp.com>
Change 4c86a5cc8d moved a select
from Kconfig.asc to Kconfig.bap (amongst some other changes
from select to depends), but inverted the PAC_{SRC,SNK} from
ASCS_ASE_{SRC,SNK} condition.
Signed-off-by: Mike J. Chen <mjchen@google.com>
(NUM_IRQS-1) IRQ is taken on this soc, so set CONFIG_TEST_IRQ_NUM to a
different available IRQ to avoid test failure.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
DT properties like 'tolerance-microvolt', 'min-microvolt',
'max-microvolt' are using microvolt unit, so update the
test case to use microvolt. In addition, using uv is more
accurate than mv. For some regulators, using mv will lose
precision and cause the test case to fail.
Signed-off-by: Zhaoxiang Jin <Zhaoxiang.Jin_1@nxp.com>
This platform is enabled incorrectly and it is not trivial to fix, but
need to hotfix CI because issue is related to linkage and causing a
build error
Signed-off-by: Declan Snyder <declan.snyder@nxp.com>
Rename this board folder to a more generic name since some other similar
boards will be added.
Add MCX-N5XX-EVK to MCXN EVK board folder. It is an almost identical
board to MCXN 9XX EVK with some slightly different things populated and
of course having the MCXN547 SOC instead of MCXN947.
Signed-off-by: Declan Snyder <declan.snyder@nxp.com>
This was previously only selected when the 2.4GHz driver was
enabled, but SubG can be enabled without the 2.4GHz driver.
Build tested using:
```
west build -b beagleconnect_freedom -d \
build/bcf/ot_coap samples/net/openthread/coap
west flash -d build/bcf/ot_coap
```
Signed-off-by: Jason Kridner <jkridner@beagleboard.org>
Add support for configuring and enabling DLL2. A few things have been
simplified (common PMUC, just store frequency, etc.).
Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>
Button 0 and LED 0 share a GPIO pin on bg27 boards. Remove the
`led0` alias in a board overlay to make the button sample work
out of the box.
Signed-off-by: Aksel Skauge Mellbye <aksel.mellbye@silabs.com>
Reformat devicetree files:
* Sort nodes by unit address or name
* Sort properties by category and name
Add missing properties to existing nodes.
Signed-off-by: Aksel Skauge Mellbye <aksel.mellbye@silabs.com>
Set #address-cells and #size-cells on usart0. Since usarts can
be used for both UART and SPI, this property shouldn't be set
in SoC-level DTS, since it makes it harder to switch compatible.
Signed-off-by: Aksel Skauge Mellbye <aksel.mellbye@silabs.com>
Fixed the include directive for mchp_pinctrl_pinmux_sam.h
by replacing quotes with angle brackets.
Signed-off-by: Arunprasath P <arunprasath.p@microchip.com>
- Update the path of pinctrl.h in sama7g54_ek.dts
- Select CONFIG_MICROCHIP_SAM for sama7g5 family devices
- Add SAM group Kconfig symbol for proper family grouping
- Rename PIC32C Kconfig symbol to MICROCHIP_PIC32C
and update references
- Update west.yml for hal-microchip re-organization
Signed-off-by: Arunprasath P <arunprasath.p@microchip.com>
The brief on the existing test_rtio_await_ function mentioned testing
that an await operation would immediately complete ("be skipped") if
the SQE were signalled prior to being submitted. The function didn't
actually test this, though.
Add a new test function for testing this specific case.
Remove the misleading part of the brief around the existing test.
Rename test_rtio_await_ to be more concise on the test it performs.
Signed-off-by: Emil Dahl Juhl <emil@s16s.ai>
The intention behind using an RTIO_OP_AWAIT tied to an rtio_iodev is
to get a guarantee that an entire transaction can be handled without
interruptions or parallel work taking place on the rtio_iodev.
This guarantee can only be met when SQEs are bundled together using
RTIO_SQE_TRANSACTION as they will otherwise be considered individual
pieces of work, hence allowing some unrelated piece of work to get
scheduled in-between the rest.
When just using RTIO_SQE_CHAINED, the rtio_iodev would still block
during the entire RTIO_OP_AWAIT, but the following SQE in the chain can
be preempted by an unrelated SQE.
Modify this specific test case to use RTIO_SQE_TRANSACTION as this will
match the intention.
Signed-off-by: Emil Dahl Juhl <emil@s16s.ai>
Add support for runtime and devicetree configuration of themocouple
type, ADC resolution, filter coefficient and cold junction temperature
resolution. Extend device specific sensor channels to include cold
junction temperature, delta tempereature, hot junction temperature and
raw ADC values while still maintaining backwards compability with the
existing SENSOR_CHAN_AMBIENT_TEMP channel.
Signed-off-by: Thomas Schmid <tom@lfence.de>
Add new sample lpdac_opamp_lpadc for frdm_mcxa156.
In this example:
1. The LPDAC outputs a 300mv voltage to the
non-inverting terminal of the OPAMP.
2. The OPAMP operates in the non-inverting amplifier
mode, the inverting terminal of the OPAMP is grounded.
3. The channel 0 of the LPADC is connected to the output
of the OPAMP, and the channel 1 of the LPADC is connected
to the output of the DAC (the non-inverting input terminal
of the OPAMP).
4. The ideal sampling range of OPAMP output channel is
specified by 'ideal-sample-range', and 'nxp,opamps' are
used to specify LPADC samples which OPAMP's output and
which ADC channel is connected to the OPAMP output.
5. The OPAMP non-inverting input is 300mV, and the OPAMP
gain is initialized to 1. Therefore, the first round OPAMP
output (~300mV) will not reach the minimum value of the
'ideal-sampling-range'. Therefore, the ADC driver will
increase the OPAMP gain through 'opamp_set_gain'. The second
round OPAMP output (~900mV) is still below the minimum value,
so the gain will continue to increase. The third round OPAMP
output (~1500mV) is already in the ideal range, so the gain
will not be adjusted later.
Signed-off-by: Zhaoxiang Jin <Zhaoxiang.Jin_1@nxp.com>
Introduce new binding properties for the LPADC DT
and update the driver to consume them.
Users can use these properties to obtain the opamp
device bound to the ADC and dynamically adjust the
opamp gain so that the opamp output is within the
ADC ideal sample range.
Signed-off-by: Zhaoxiang Jin <Zhaoxiang.Jin_1@nxp.com>
1. Added opamp driver and example support to release
notes for release 4.3.
2. Add documentation for the opamp peripheral.
Signed-off-by: Zhaoxiang Jin <Zhaoxiang.Jin_1@nxp.com>
