Re: [RFC 9/9] {fwctl,drm}/xe/pcode: Introduce xe_pcode_fwctl

[Jason Gunthorpe <jgg@nvidia.com>]

On Fri, Aug 22, 2025 at 03:33:17PM -0400, Rodrigo Vivi wrote:
> On Wed, May 07, 2025 at 07:04:44PM -0300, Jason Gunthorpe wrote:
> > On Wed, May 07, 2025 at 03:49:15PM -0400, Rodrigo Vivi wrote:
> > 
> > > One last thing since I have your attention here. Was any time in the previous
> > > fwctl discussions talked about the possibility of some extra usages for like
> > > FW flashing or in-field-repair/tests where big data needs to filled bypassing
> > > lockdown mode?
> > 
> > For FW flash I do suggest you try to use devlink's firmware flashing
> > interface. I think it would be really great if that could become a
> > cross-subsystem standard in Linux.
> 
> I took a look there and I do believe devlink works very well for fw flashing and
> it is also already prepared for basically any pci device without any change.
> Thanks for the suggestion.

Jiri also has generic plugin for fwupd:

https://github.com/fwupd/fwupd/pull/9053

So if you do the kernel side you get a whole ecosystem now..

> But now I have to ask you about 2 other use cases that are not under the
> umbrella of: configuration and provisioning, but perhaps at least partially
> under the umbrella of debug:
> 
> - In-field-test-and-repair
> - Error injection
> 
> Can fwctl be used for these use cases, supposing that it FW mailboxes
> commands and responses directly with no modification to the fwctl
> infra itself?

These sound like what fwctl was intended for, yes.

Jason