Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

l2cc: Don't repeat disabling the cache when the cache is already disabled #9048

Merged
merged 1 commit into from Apr 25, 2023

Conversation

zyfeier
Copy link
Contributor

@zyfeier zyfeier commented Apr 20, 2023

Summary

When l2cc is already in disable state, performing a disable operation again will flush incorrect cache data to memory.
So, when it is found that the L2 cache is in a disabled state during startup, no flash operation is performed. Only when it is necessary to disable the L2 cache, a flush operation is performed.

Impact

L2 cache

Testing

sabre-6quad:smp

@xiaoxiang781216
Copy link
Contributor

@zyfeier please rebase your change.

…abled

When l2cc is already in disable state, performing a disable operation
again will flush incorrect cache data to memory

Signed-off-by: zhangyuan21 <zhangyuan21@xiaomi.com>
@masayuki2009
Copy link
Contributor

sabre-6quad:smp

@zyfeier
Did you test this PR on a real board (i.e. sabre-6quad board)?

@zyfeier
Copy link
Contributor Author

zyfeier commented Apr 24, 2023

sabre-6quad:smp

@zyfeier Did you test this PR on a real board (i.e. sabre-6quad board)?

Yes, test with sabre-6quad board and bes2003 board.

@xiaoxiang781216 xiaoxiang781216 merged commit 6605f95 into apache:master Apr 25, 2023
26 checks passed
@zyfeier zyfeier deleted the l2_cache_2 branch April 27, 2023 01:55
@jerpelea jerpelea added this to To-Add in Release Notes - 12.2.0 Jun 13, 2023
@jerpelea jerpelea moved this from To-Add to In Progress in Release Notes - 12.2.0 Jun 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

None yet

3 participants