lib: sbi_ipi: Make .ipi_clear always target the current hart

All existing users of this operation target the current hart, and it
seems unlikely that a future user will need to clear the pending IPI
status of a remote hart. Simplify the logic by changing .ipi_clear (and
its wrapper sbi_ipi_raw_clear()) to always operate on the current hart.

This incidentally fixes a bug introduced in commit 78c667b6fc ("lib:
sbi: Prefer hartindex over hartid in IPI framework"), which changed the
.ipi_clear parameter from a hartid to a hart index, but failed to update
the warm_init functions to match.

Fixes: 78c667b6fc ("lib: sbi: Prefer hartindex over hartid in IPI framework")
Signed-off-by: Samuel Holland <samuel.holland@sifive.com>
Reviewed-by: Anup Patel <anup@brainfault.org>
This commit is contained in:
Samuel Holland
2024-10-25 11:59:46 -07:00
committed by Anup Patel
parent db8f03e512
commit be9752a071
5 changed files with 14 additions and 20 deletions

View File

@@ -41,9 +41,9 @@ static void plicsw_ipi_send(u32 hart_index)
writel_relaxed(BIT(pending_bit), (void *)pending_reg);
}
static void plicsw_ipi_clear(u32 hart_index)
static void plicsw_ipi_clear(void)
{
u32 target_hart = sbi_hartindex_to_hartid(hart_index);
u32 target_hart = current_hartid();
ulong reg = plicsw.addr + PLICSW_CONTEXT_BASE + PLICSW_CONTEXT_CLAIM +
PLICSW_CONTEXT_STRIDE * target_hart;
@@ -68,7 +68,7 @@ static struct sbi_ipi_device plicsw_ipi = {
int plicsw_warm_ipi_init(void)
{
/* Clear PLICSW IPI */
plicsw_ipi_clear(current_hartindex());
plicsw_ipi_clear();
return 0;
}