Skip to content

hal_ethos_u: Update to upstream commit for ethosu_config_select#431

Open
SrinivasRagolu-AlifSemi wants to merge 1 commit intoalifsemi:mainfrom
SrinivasRagolu-AlifSemi:feature/update-hal-ethos-u-commit
Open

hal_ethos_u: Update to upstream commit for ethosu_config_select#431
SrinivasRagolu-AlifSemi wants to merge 1 commit intoalifsemi:mainfrom
SrinivasRagolu-AlifSemi:feature/update-hal-ethos-u-commit

Conversation

@SrinivasRagolu-AlifSemi
Copy link
Copy Markdown
Contributor

Taking upstream commit db2caeb33975acbcd4db1c517120c0eada1798ac to get ethosu_config_select platform hook changes.

Add ethosu_config_select platform hook

Allow config and hence port selection to be done at run-time based on region address, avoiding need to recompile C code for linker map changes, and permitting an application to have one model in SRAM and another in external memory.

Change-Id: I425ee1ad2598b65a3c891261a7eff00e9565bdbe

Taking upstream commit db2caeb33975acbcd4db1c517120c0eada1798ac
to get ethosu_config_select platform hook changes.

Add ethosu_config_select platform hook

Allow config and hence port selection to be done at run-time based on
region address, avoiding need to recompile C code for linker map
changes, and permitting an application to have one model in SRAM and
another in external memory.

Change-Id: I425ee1ad2598b65a3c891261a7eff00e9565bdbe
Signed-off-by: Kevin Bracey <kevin.bracey@alifsemi.com>
Signed-off-by: Jonny Svärd <jonny.svaerd@arm.com>
Signed-off-by: Srinivasa Rao Ragolu <srinivasa@alifsemi.com>
@JuhoEskeli-AlifSemi
Copy link
Copy Markdown
Contributor

Is there reason not taking the latest commit version?

@JuhoEskeli-AlifSemi
Copy link
Copy Markdown
Contributor

Is there reason not taking the latest commit version?

I see there's caching changes which would then need to be considered. So is the idea to just make a safe jump forward which should not cause additional rework?

@SrinivasRagolu-AlifSemi
Copy link
Copy Markdown
Contributor Author

Is there reason not taking the latest commit version?

Juho, when I go through the other top commits its more of documentation and cache weak function changes. This commit is stable per Kevin Bracy, who tested it on the ML toolkit side as well.

@SrinivasRagolu-AlifSemi
Copy link
Copy Markdown
Contributor Author

Is there reason not taking the latest commit version?

I see there's caching changes which would then need to be considered. So is the idea to just make a safe jump forward which should not cause additional rework?

Actually, those cache functions are weak functions and are overridden by our own implementation, which works cache management perfectly fine. Rather than a safe jump, its stable commit jump.

SrinivasRagolu-AlifSemi added a commit to SrinivasRagolu-AlifSemi/sdk-alif that referenced this pull request Mar 18, 2026
The PR refers to alifsemi/zephyr_alif/pull/431

Signed-off-by: Srinivasa Rao Ragolu <srinivasa@alifsemi.com>
@JuhoEskeli-AlifSemi
Copy link
Copy Markdown
Contributor

JuhoEskeli-AlifSemi commented Mar 18, 2026

In ML toolkit we seem to be at commit 60b4fbf76af8bff11c316588e77b7d626ab65e75 (HEAD, tag: 25.08-rc2, tag: 25.08-rc1, tag: 25.08, tag: 25.05-rc2, tag: 25.05, origin/main, origin/HEAD, main)

@SrinivasRagolu-AlifSemi
Copy link
Copy Markdown
Contributor Author

In ML toolkit we seem to be at commit 60b4fbf76af8bff11c316588e77b7d626ab65e75 (HEAD, tag: 25.08-rc2, tag: 25.08-rc1, tag: 25.08, tag: 25.05-rc2, tag: 25.05, origin/main, origin/HEAD, main)

db2caeb33975acbcd4db1c517120c0eada1798ac is required and suggested Kevin's commit. Do you suggest me to bump to latest commit?

@JuhoEskeli-AlifSemi
Copy link
Copy Markdown
Contributor

I discussed this with @kjbracey and we'll do as you originaly proposed. Cache changes can wait.

@SrinivasRagolu-AlifSemi
Copy link
Copy Markdown
Contributor Author

I discussed this with @kjbracey and we'll do as you originaly proposed. Cache changes can wait.

Thanks for the confirmation.

@jheiskan81
Copy link
Copy Markdown
Contributor

Please check CI check patch error

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants