Re: [PATCH v2 2/2] RISC-V: make use of variadic sbi_ecall

[Anirudh Srinivasan]

On Wed, Oct 07, 2026 at 08:46:57PM -0600, Paul Walmsley wrote:
> On Wed, 7 Oct 2026, Radim Krcmar wrote:
> 
> > 2026-10-06T03:55:12-06:00, Paul Walmsley <pjw@xxxxxxxxxx>:
> > > On Thu, 19 Jun 2025, Radim Krčmář wrote:
> > >
> > >> The new sbi_ecall doesn't have to list all 8 arguments anymore, so only
> > >> pass the actual numbers of arguments for each SBI function.
> > >> 
> > >> The remaining trailing 0 are intentional as they represent an argument.
> > >> 
> > >> SBI 0.1 shouldn't be using the sbi_ecall, because it's only for 0.2+,
> > >> but allow it by passing 0 is the reserved register.
> > >> 
> > >> Signed-off-by: Radim Krčmář <rkrcmar@xxxxxxxxxxxxxxxx>
> > >
> > > Thanks, queued for v7.4.  
> > >
> > > For everyone, not just Radim - probably it's worth looking through the 
> > > codebase to convert any SBI ecalls that were added over the past year that 
> > > weren't covered by this patch (e.g., the MPXY drivers) and to doublecheck 
> > > the overall argument counts.
> > 
> > I started working on a followup and noticed a bug.
> > 
> > Please squash the following change or just drop the second patch, since
> > we may be touching the same lines again soon, sorry about that.
> 
> Thanks, squashed in.

Thanks Paul. FYI this bug is causing earlycon console output to break
on blackhole because it uses the SBI HVC console for output. Radim's fix
should hopefully solve this.

> 
> 
> - Paul

> _______________________________________________
> linux-riscv mailing list
> linux-riscv@xxxxxxxxxxxxxxxxxxx
> http://lists.infradead.org/mailman/listinfo/linux-riscv