[PATCH] soc: fsl: dpio: protect smp_processor_id when get processor id

2021-10-15 Thread Meng . Li
From: Meng Li When enable debug kernel configs,there will be calltrace as below: BUG: using smp_processor_id() in preemptible [] code: swapper/0/1 caller is debug_smp_processor_id+0x20/0x30 CPU: 6 PID: 1 Comm: swapper/0 Not tainted 5.10.63-yocto-standard #1 Hardware name: NXP Layerscape

[PATCH v2] soc: fsl: dpio: instead smp_processor_id with raw_smp_processor_id

2021-10-18 Thread Meng . Li
From: Meng Li When enable debug kernel configs,there will be calltrace as below: BUG: using smp_processor_id() in preemptible [] code: swapper/0/1 caller is debug_smp_processor_id+0x20/0x30 CPU: 6 PID: 1 Comm: swapper/0 Not tainted 5.10.63-yocto-standard #1 Hardware name: NXP Layerscape

[PATCH] driver: soc: dpio: use the whole functions to protect critical zone

2021-10-18 Thread Meng . Li
From: Meng Li In orininal code, use 2 function spin_lock() and local_irq_save() to protect the critical zone. But when enable the kernel debug config, there are below inconsistent lock state detected. WARNING: inconsistent lock state 5.10.63-yocto-standard #1 Not