> -----Original Message-----
> From: Andrew Lunn <[email protected]>
> Sent: Wednesday, November 12, 2025 7:42 AM
> To: Shenwei Wang <[email protected]>
> Cc: Linus Walleij <[email protected]>; Bjorn Andersson
> <[email protected]>; Mathieu Poirier <[email protected]>; Rob
> Herring <[email protected]>; Krzysztof Kozlowski <[email protected]>; Conor
> Dooley <[email protected]>; Shawn Guo <[email protected]>; Sascha
> Hauer <[email protected]>; Jonathan Corbet <[email protected]>; Bartosz
> Golaszewski <[email protected]>; Pengutronix Kernel Team
> <[email protected]>; Fabio Estevam <[email protected]>; Peng Fan
> <[email protected]>; [email protected];
> [email protected]; [email protected]; linux-arm-
> [email protected]; [email protected]; linux-
> [email protected]; dl-linux-imx <[email protected]>
> Subject: [EXT] Re: [PATCH v5 3/5] docs: staging: gpio-rpmsg: gpio over rpmsg
> bus
>
> Since this has not been merged yet, there are no existing systems.
>
In this context, "system" refers to both Linux and the remote firmware. The
remote firmware
for i.MX platforms has already been released and widely used by our customers.
Maintaining
compatibility with the existing firmware would provide a better solution for
customers.
Thanks,
Shenwei
> It is well known that what gets merged into mainline is often different to the
> initial out of tree version. You just need to deal with it. One option you
> have is to
> set the vendor byte to 1, so indicating NXP. If Linux uses vendor 0, it might
> be
> your out of tree vendor driver, not the in kernel driver. Just document in the
> specification vendor 0 is reserved.
>
> You are going to have to modify your firmware anyway, level interrupts are
> broken. And this is an example of why quirks are needed.
>
> Andrew
