diff options
| author | Markus Stockhausen <markus.stockhausen@gmx.de> | 2022-09-30 08:03:38 +0200 |
|---|---|---|
| committer | Sander Vanheule <sander@svanheule.net> | 2022-10-01 09:22:32 +0200 |
| commit | b7aab1958591e62900e0275bc9cd80d10a4f9f53 (patch) | |
| tree | e0efa9b4f1d5be5bc517e4d92d7b8d00e9ed61ee /target/toolchain/files | |
| parent | 2b12da1313706cdd14791f329899de11ce9a35eb (diff) | |
| download | upstream-b7aab1958591e62900e0275bc9cd80d10a4f9f53.tar.gz upstream-b7aab1958591e62900e0275bc9cd80d10a4f9f53.tar.bz2 upstream-b7aab1958591e62900e0275bc9cd80d10a4f9f53.zip | |
realtek: SMP handling of R4K timer interrupts
Until now there has been no good explanation why we mess with the R4K
timer on SMP. After extensive testing and looking at the SDK code it
becomes clear what it is all about.
When we disable the CEVT_R4K module (we will do with the new timer
driver) the R4K timer hardware still fires interrupts on the secondary
CPU. To get around this we have two options:
- Disable IRQ 7
- Stop the counter completely
This patch selects option two because this is the root of evil.. To be
on the safe side we will do it only in case the CEVT_R4K module is
disabled.
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
Diffstat (limited to 'target/toolchain/files')
0 files changed, 0 insertions, 0 deletions