Commit 81d76d1
committed
ipc4: harden IPC4 pipeline triggering logic
Using IPC4_MOD_ID() is not the best way to check if IPC4 is enabled. For
module ID == 0, IPC4_MOD_ID() returns 0 for both IPC3 and IPC4. Module
ID 0 is a valid IPC4 BASEFW ID. Since BASEFW is never added to a pipeline,
this change doesn't fix any real problem. However, it's just more
appropriate and safer to use IS_ENABLED(CONFIG_IPC_MAJOR_4): if module ID
data becomes corrupted (zeroed) at runtime, this shouldn't make debugging
even harder by causing unexpected pipeline behavior.
Signed-off-by: Serhiy Katsyuba <serhiy.katsyuba@intel.com>1 parent 60283dc commit 81d76d1
4 files changed
Lines changed: 4 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
369 | 369 | | |
370 | 370 | | |
371 | 371 | | |
372 | | - | |
| 372 | + | |
373 | 373 | | |
374 | 374 | | |
375 | 375 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
267 | 267 | | |
268 | 268 | | |
269 | 269 | | |
270 | | - | |
| 270 | + | |
271 | 271 | | |
272 | 272 | | |
273 | 273 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
140 | 140 | | |
141 | 141 | | |
142 | 142 | | |
143 | | - | |
| 143 | + | |
144 | 144 | | |
145 | 145 | | |
146 | 146 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
229 | 229 | | |
230 | 230 | | |
231 | 231 | | |
232 | | - | |
| 232 | + | |
233 | 233 | | |
234 | 234 | | |
235 | 235 | | |
| |||
0 commit comments