On Sun, May 10, 2026 at 06:07:01PM +0200, Greg KH wrote:
> On Sun, May 10, 2026 at 04:44:57AM -0400, Pramod Maurya wrote:
> > Add a YAML schema for the Xilinx AXI-Stream FIFO IP core (PG080).
> > The binding documents the three supported compatible strings and all
> > vendor-specific properties that the axis-fifo driver reads from the
> > device tree.
> > 
> > This resolves the following checkpatch.pl warnings in
> > drivers/staging/axis-fifo/axis-fifo.c:
> >   WARNING: DT compatible string "xlnx,axi-fifo-mm-s-4.1" appears un-documented
> >   WARNING: DT compatible string "xlnx,axi-fifo-mm-s-4.2" appears un-documented
> >   WARNING: DT compatible string "xlnx,axi-fifo-mm-s-4.3" appears un-documented
> > 
> > Signed-off-by: Pramod Maurya <pramod.nexgen@gmail.com>
> > ---
> > Changes in v2:
> > - Delete drivers/staging/axis-fifo/axis-fifo.txt as part of the
> >   conversion (was missing from v1)
> > - Add all Vivado-generated properties to the schema so that real
> >   hardware DT nodes pass validation with additionalProperties: false
> > - Update example to match a realistic Vivado-generated DT node
> >   including all properties
> > 
> >  .../bindings/misc/xlnx,axi-fifo-mm-s.yaml     | 265 ++++++++++++++++++
> >  MAINTAINERS                                   |   6 +
> >  drivers/staging/axis-fifo/axis-fifo.txt       |  96 -------
> >  3 files changed, 271 insertions(+), 96 deletions(-)
> >  create mode 100644 Documentation/devicetree/bindings/misc/xlnx,axi-fifo-mm-s.yaml
> 
> No, staging drivers need to be self-contained.  When/if the axis-fifo
> driver moves out of drivers/staging/ this can happen, but not until
> then.
> 
> You can convert this to yaml in-place if you want, AND you can test that
> the conversion is correct.  Do you have this hardware to test this with?

Copy-pasting from v1...
| Someone else submitted this conversion (which it is, despite you not
| removing the old file), and the commentary I provided for that patch
| applies here too:
| https://lore.kernel.org/all/20260227-unboxed-customary-7ce6eda1858c@spud/

I suspect that this could be a dma-engine and any patch doing a
conversion needs to justify why it is not.
pw-bot: changes-requested