[PATCH v2] irqchip: gic-v3-its: irq_pipeline: Fix OOB context in-band lock warning for ITS lock

[linz <powertree@163.com>]

Thank you for your feedback

Under 6.6.63-dovetail2 environment, raw_spinlock_t for the ITS node lock triggers out‑of‑band context warning in irq‑pipeline code.
As suggested by Florian, hybrid_spinlock_t should be limited to struct irq_desc and irqchip internals. ITS node lock is more suitable to use hard_spinlock_t.

After replacing raw_spinlock_t with hard_spinlock_t, the call‑trace warning disappears and system runs stably.

In addition, the gic‑v3 irqchip already has IRQCHIP_PIPELINE_SAFE flag, while its_irq_chip lacks this flag.
Enabling IRQCHIP_PIPELINE_SAFE for its_irq_chip has no effect to resolve the warning.

Signed-off-by: zhanglin <powertree@163.com>
---
 drivers/irqchip/irq-gic-v3-its.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/irqchip/irq-gic-v3-its.c b/drivers/irqchip/irq-gic-v3-its.c
index 0e57735eac..3f2b02b8f4 100644
--- a/drivers/irqchip/irq-gic-v3-its.c
+++ b/drivers/irqchip/irq-gic-v3-its.c
@@ -94,7 +94,7 @@ struct its_device;
  * list.
  */
 struct its_node {
-	raw_spinlock_t		lock;
+	hard_spinlock_t		lock;
 	struct mutex		dev_alloc_lock;
 	struct list_head	entry;
 	void __iomem		*base;
-- 
2.34.1