Repository navigation
Fix TI downstream compliance checks - #81
Merged
Aman-Lachhiramka-ti merged 4 commits intoOct 12, 2026
Merged
Aman-Lachhiramka-ti merged 4 commits into
Aman-Lachhiramka-ti merged 4 commits into
Conversation
commit 8f2673a upstream. Updated parsing due to filename changes. Signed-off-by: Swift Tian <swift.tian@ambiq.com>
XIP in Zephyr is a software configuration concept (CONFIG_XIP). The MSPI
feature gated by MSPI_XIP only memory-maps the device into the SoC
address space; the mapped region can be used for plain data access as
well as code execution. Rename the feature to MEMMAP to reflect what it
actually does:
- CONFIG_MSPI_XIP -> CONFIG_MSPI_MEMMAP
- CONFIG_FLASH_MSPI_XIP_READ -> CONFIG_FLASH_MSPI_MEMMAP_READ
- struct mspi_xip_cfg -> struct mspi_memmap_cfg
- enum mspi_xip_permit / MSPI_XIP_READ_* -> mspi_memmap_permit /
MSPI_MEMMAP_READ_*
- mspi_xip_config() -> mspi_memmap_config(), driver API entry
xip_config -> memmap_config
- MSPI_XIP_CONFIG_DT{,_INST,_NO_CHECK} -> MSPI_MEMMAP_CONFIG_DT{,...}
- MSPI_XIP_CFG_STRUCT_DECLARE / MSPI_XIP_BASE_ADDR_{DECLARE,INIT} ->
MSPI_MEMMAP_*
- devicetree property xip-config -> memmap-config
Vendor HAL symbols (am_hal_mspi_xip_*) and DesignWare register names,
where XIP is the hardware documentation terminology, are unchanged.
The MSPI API is experimental, so no deprecated aliases are provided;
a migration guide entry is added in a separate commit. Add missing
Doxygen comments on new API symbols. Add missing SPDX header to the
nrf54h20dk code_relocation_nocopy overlay touched by this rename.
Fixes zephyrproject-rtos#104657
Signed-off-by: Richard Wheatley <richard.wheatley@ambiq.com>
---
Some of this patch was applied earlier by me, assuming that touching non-TI
files wouldn't cause compliance check failures, however it does cause
failures. So this patch contains rest of the changes from the upstream
patch.
Upstream SHA : 24ac9af
Other Downstream SHA : c5cd8af
Signed-off-by: Amneesh Singh <amneesh@ti.com>
commit 6072d48 upstream. Update the MSPI peripheral documentation for the XIP to MEMMAP rename: reference mspi_memmap_config(), the memmap-config devicetree property and CONFIG_MSPI_MEMMAP instead of the removed XIP names. Signed-off-by: Richard Wheatley <richard.wheatley@ambiq.com>
natto1784
force-pushed
the
v4.4.0-ti/drivers/mspi
branch
from
October 12, 2026 05:19
e745799 to
37c9e0d
Compare
commit 03a1af1 upstream. Describe the M95P32 page EEPROM on an MSPI bus. Signed-off-by: Mohammad Odeh <zephyr@exalt.ps>
natto1784
changed the title
Aman-Lachhiramka-ti
merged commit Oct 12, 2026
8bd82b0
into
TexasInstruments:v4.4.0-ti-next
10 of 14 checks passed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Remaining changes from the MSPI rename patchset. I was not aware that not cherry picking other vendors would cause compliance failures, hence only picked changes relevant to TI. However this causes failing compliance checks.
This is required for fixing the failing compliance checks at TI downstream.