[nrf fromlist] manifest: hal_nordic update #2208
Closed
Conversation
This file contains 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
|
The following west manifest projects have been modified in this Pull Request:
Note: This message is automatically posted and updated by the Manifest GitHub Action. |
JuhaKortesalmi
force-pushed
the
NRFX-6062_SW_MA_Power_Seq
branch
12 times, most recently
from
c0fdbd6 to
9275ea7
Compare
This reverts commit a3a28db. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>
Fix the noise during boot. Upstream PR #: 80858 Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>
In case the driver UP fails, the FMAC context will be NULL, so, add a NULL check in the DOWN. Fixes a crash seen when working with unprogrammed OTP (no MAC) that fails the interface UP. Upstream PR #: 80858 Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>
This is needed to ensure Wi-Fi can always be used. Upstream PR #: 80822 Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>
Some spi drivers do not allow the send buffer and receive buffer to be empty at the same time, if this happens it will cause the spi to be unable to communicate with the nrf7002, so add the receive buffer for the discard byte in the spim_xfer_rx. Fix #80686 Upstream PR #: 80787 Signed-off-by: Hongquan Li <hongquan.prog@gmail.com>
With introduction of Raw modes, nRF70 driver now advertises get_c
onfig OP, but doesn't implement all types.
This causes problems two-fold with checksum calculations:
1. The "config" isn't uninitialized, so, every call returns differnet
values. So, for UDP header checksum would be done and
pkt->chksumdone would be set. But for IPv4 header checksum might be
skipped.
2. Even if we initialize to zero, then network stack gets all zeros
and calculates checksum by itself rendering offload moot.
There is another problem in nrfconnect#1, as there is only single flag for pkt for
all checksum, nRF70 driver sees this and tells UMAC to skip checksum for
the entire packet. The design isn't coherent, and should be converted to
communicate per-type checksum status (some are filled by network stack
and some HW).
But as nRF70 support all checksum offloads, advertise all types for both
RX and TX.
Upstream PR #: 80882
Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>
DCDC regulator on nRF54L may not always works as intended. Tune the fix addressing that. Upstream PR #: 80635 Signed-off-by: Nikodem Kastelik <nikodem.kastelik@nordicsemi.no>
…ags" This reverts commit d005a17. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>
…lts flag" This reverts commit a5eb552. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>
Pass passive scan and offloaded raw tx feature flags to OSAL. Upstream PR #: 80328 Signed-off-by: Kapil Bhatt <kapil.bhatt@nordicsemi.no>
The CONFIG_ prefix should be removed when passing to OSAL code. Upstream PR #: 80328 Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>
With the newly introduced settling time for PLLS, we are seeing a peak performance drop of 3Mbps in Zperf benchmarks, and also other performance tests are also impacted. This settling time was introduced based on observations in lab and not because of any real problem or bug reported, so, for now, use zero settling time (same as earlier) till we fully investigate and understand the impacts and need. Fixes #80951. Upstream PR #: 80952 Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>
…ower modes RX FIFO flushing on RXTO event should only be performed when UARTE peripheral might be disable during inactivity and that happens when low power modes is enabled or when device runtime PM is used. Flushing was incrementing flush_cnt which was not used (flushed data is not copied to the next buffer) which was causing data loss and invalid RX data length reporting. Upstream PR #: 80968 Signed-off-by: Krzysztof Chruściński <krzysztof.chruscinski@nordicsemi.no>
During cherry-pick the directory wasn't renamed. Upstream PR #: 82335 Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>
Fix the missing define to OSAL code. Upstream PR #: 82335 Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>
This helps maintaining of various modes in nRF Wi-Fi driver. Upstream PR #: 82335 Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>
Low Power mode can only be entered when there are no active DMA transfers. Move the Suspend and Resume processing to thread to allow waiting for the DMA available semaphore in USB Suspend handler. Signed-off-by: Tomasz Moń <tomasz.mon@nordicsemi.no> (cherry picked from commit 4dfae0b)
DMA transfers do not execute when the USBD peripheral is in Low Power mode. Make sure that there is no DMA active transfer when entering Low Power mode and that new DMA transfers are not started when in Low Power mode because the transfer won't ever finish. Signed-off-by: Tomasz Moń <tomasz.mon@nordicsemi.no> (cherry picked from commit cb1e7d6)
…Interface Respond with a Request Error in default and addressed states. Signed-off-by: Johann Fischer <johann.fischer@nordicsemi.no> (cherry picked from commit 1a5ab2c) Signed-off-by: Tomasz Moń <tomasz.mon@nordicsemi.no>
The NAKSts bit may be set on isochronous OUT endpoints when incomplete ISO OUT interrupt is raised. The code would then assume that endpoint is already disabled and would not perform the endpoint disable procedure. This in turn was essentially halting any transmission on the isochronous endpoint, abruptly terminating the data stream. Fix the issue by always following full endpoint disable procedure on isochronous endpoints. Signed-off-by: Tomasz Moń <tomasz.mon@nordicsemi.no> (cherry picked from commit 8b212d8)
… IN interrupt When handling incomplete iso IN interrupt mark current transfer as complete and program the endpoint with any subsequently queued packet. Program the endpoint directly in interrupt handler because the data must be programmed before SOF (by the time incomplete iso IN interrupt is raised there is less than 20% * 125 us = 25 us before SOF). Signed-off-by: Tomasz Moń <tomasz.mon@nordicsemi.no> (cherry picked from commit edbb053)
…dpoints Application is expected to call usbd_uac2_send() on each enabled USB Streaming Output Terminal (isochronous IN data endpoint) exactly once every SOF. The class is bookkeeping queued transfers to make it easier to determine component at fault when things go wrong. However, this approach only works fine if the underlying USB device controller buffers the data to be sent on next SOF and reports the transfer completion immediately after data is buffered (e.g. nRF52 USBD). While DWC2 otg also requires the SW to arm endpoint with data for the next SOF, unlike nRF52 USBD the transfer is only considered complete after either the IN token for isochronous endpoint is received or after the Periodic Frame Interval elapses without IN token. This design inevitably requires the application to be able to have at least two buffers for isochronous IN endpoints. Support dual buffering on IN data endpoints to facilitate sending isochronous IN data on every SOF regardless of the underlying USB device controller design. Signed-off-by: Tomasz Moń <tomasz.mon@nordicsemi.no> (cherry picked from commit c19d34c)
…ndition Endpoint disable function is racing against bus traffic. If the bus traffic leads to transfer completion immediately before the endpoint disable is executed, then the transfer complete interrupt will remain set when the endpoint is disabled. For OUT endpoints this leads to "No buffer for ep" errors, while for IN endpoint this can lead to double buffer pull which causes assertion failure. The proper solution would be to change endpoint disable to not actually wait for the individual events (and accept that the endpoint may not need to be disabled because the transfer can just finish). For the time being workaround the issue by clearing XferCompl bit on endpoint disable. Signed-off-by: Tomasz Moń <tomasz.mon@nordicsemi.no> (cherry picked from commit a26d3c2)
Accessing DWC2 otg core registers before the clock starts results in complete system hang. Add a 1 us busy wait to make sure that software won't access registers before the clock is started. Signed-off-by: Tomasz Moń <tomasz.mon@nordicsemi.no> (cherry picked from commit df36b16)
This reverts commit 1eef25b. Signed-off-by: Adam Kondraciuk <adam.kondraciuk@nordicsemi.no>
…fig" This reverts commit dab9c11. Signed-off-by: Adam Kondraciuk <adam.kondraciuk@nordicsemi.no>
This reverts commit 1cc6e15. Signed-off-by: Adam Kondraciuk <adam.kondraciuk@nordicsemi.no>
Due to the possibility of simultaneous accesess to LRCCONF registers, additional management is required. Signed-off-by: Adam Kondraciuk <adam.kondraciuk@nordicsemi.no> (cherry picked from commit 9b25285)
Add `idle` and `s2ram` power states for nRF54H20 cpuapp and cpurad. Also the substate `idle_cache_disable` added. Signed-off-by: Adam Kondraciuk <adam.kondraciuk@nordicsemi.no> (cherry picked from commit e786c1f)
IRQs must be disabled before starting any procedures to prepare for low-power states. Signed-off-by: Adam Kondraciuk <adam.kondraciuk@nordicsemi.no> (cherry picked from commit be1f405)
JuhaKortesalmi
force-pushed
the
NRFX-6062_SW_MA_Power_Seq
branch
from
eb3c113 to
20e5eb8
Compare
…lator Since nrfx 3.9 integration, configuration is executed in MDK SystemInit(). Upstream PR #: 82268 Signed-off-by: Nikodem Kastelik <nikodem.kastelik@nordicsemi.no>
…F54L anomaly 31 This workaround will be replaced with a variant executed at SystemInit() level, once MDK implements it. Upstream PR #: 82268 Signed-off-by: Nikodem Kastelik <nikodem.kastelik@nordicsemi.no>
…or nRF54L05 & L10 MDK 8.68.1 uses nRF54L15_XXAA symbol for determining whether given errata is applicable or not for nRF54L Series SoCs. This causes all erratas to be disabled for nRF54L05 and nRF54L10. To mitigate this DEVELOP_IN_NRF54L15 symbol needs to be defined, and removed once new MDK is integrated. Upstream PR #: 82268 Signed-off-by: Nikodem Kastelik <nikodem.kastelik@nordicsemi.no>
Add missing nodes: i2c23, i2c24, spi23, spi24, uart23, uart24. Signed-off-by: Krzysztof Chruściński <krzysztof.chruscinski@nordicsemi.no> (cherry picked from commit d87bafe)
NRFS support for control P11 power switch. Upstream PR #: 80657 Signed-off-by: Juha Kortesalmi <juha.kortesalmi@nordicsemi.no>
JuhaKortesalmi
force-pushed
the
NRFX-6062_SW_MA_Power_Seq
branch
from
20e5eb8 to
6f6b5ca
Compare
jukkar
requested review from
anangl,
de-nordic,
nordic-krch and
a team
as code owners
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.
Upstream PR #: 80657