From: Grewstad <dogestad24@gmail.com>
To: Ovidiu Panait <ovidiu.panait.oss@gmail.com>
Cc: Dan Carpenter <error27@gmail.com>,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev,
Jacob Feder <jacobsfeder@gmail.com>
Subject: Re: [PATCH] staging: axis-fifo: remove driver
Date: Wed, 3 Jun 2026 08:50:32 +0530 [thread overview]
Message-ID: <CAD03fjb2WJM++ymkdqWs8CTEatevJB8iYNjsqDYe81y27iDfXg@mail.gmail.com> (raw)
In-Reply-To: <CAD03fjZdaFPAy3qr8zM-Nn8wNdRG7Sz6i5+6tNLHx1sbd551Tg@mail.gmail.com>
Follow-up:
Worst-case scenario, a large group of people is using the driver,
they will complain and we can always bring it back,
Thanks,
Arihan Bhor
On Wed, Jun 3, 2026 at 8:48 AM Grewstad <dogestad24@gmail.com> wrote:
>
> On Wed, Jun 3, 2026 at 2:56 AM Ovidiu Panait
> <ovidiu.panait.oss@gmail.com> wrote:
>
> > I was using this driver to play around with an FPGA board I have (Arty
> > Z7-20), so not for commercial purposes. This IP provides a convenient
> > way to move data to/from a custom IP in the FPGA. I am using it mostly
> > for testing.
>
> Are you still using it?
>
> > I think there are no in-tree users mainly because the IP it talks to
> > lives in the FPGA fabric, and drivers for custom FPGA IP blocks
> > generally don't get upstreamed.
> >
> > However, there is the problem of what subsystem this belongs to. It was
> > suggested to be turned into a DMA controller to get it moved out of staging:
> > https://lore.kernel.org/all/20260227-unboxed-customary-7ce6eda1858c@spud/
>
> This is the main reason i suggested its deletion. it is very difficult to group
> it into any particular subsystem because at a low level it is just a
> 'dumb buffer'. If we do not know its end users and which software uses it,
> it will probably be very difficult to move it out of staging.
>
> > Here are people using it and running into issues in Jan 2025.
> > https://adaptivesupport.amd.com/s/question/0D54U00008zRBdISAW/vitis-is-not-creating-a-driver-entry-for-axififomm-43?language=zh_CN
> > Someone provides a work around:
> > https://adaptivesupport.amd.com/s/question/0D54U00008sLBuMSAW/how-to-use-the-axi-stream-fifo-drivers-xllfifoh-xllfifogc-etc-in-the-project?language=en_US
> > Then Ovidiu Panait fixed the bug in Sep by adding the correct
> > compatible.
>
> There are obviously some users, but in my honest opinion too few,
> too minor and too unverified to justify its maintenance in the kernel,
> especially because we have no feedback loop for the development of the
> driver.
>
> >I ’ve gotten a few emails over the years from people using it, and there is also development happening in parallel on the original github repo:
> > https://github.com/jacobfeder/axisfifo
>
> This project has basically ground to a halt now, three commits in 2025 and
> basically dead for a year now.
>
> Thanks,
> Arihan Bhor
>
>
> > But I am not sure that this fits as a DMA controller, as it has no DMA
> > capabilities. The CPU moves every word individually to and from a register.
> >
> > My understanding is that the real Xilinx dmaengine IP is
> > drivers/dma/xilinx/xilinx_dma.c and this IP is just a simpler, register
> > based alternative to move data between the CPU and the FPGA fabric.
next prev parent reply other threads:[~2026-06-03 3:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 10:31 Arihan Bhor
2026-06-02 11:37 ` Dan Carpenter
2026-06-02 13:01 ` Grewstad
2026-06-02 13:11 ` Dan Carpenter
2026-06-02 21:26 ` Ovidiu Panait
2026-06-03 3:18 ` Grewstad
2026-06-03 3:20 ` Grewstad [this message]
2026-06-03 12:25 ` Grewstad
2026-06-03 13:25 ` Michal Simek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAD03fjb2WJM++ymkdqWs8CTEatevJB8iYNjsqDYe81y27iDfXg@mail.gmail.com \
--to=dogestad24@gmail.com \
--cc=error27@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jacobsfeder@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=ovidiu.panait.oss@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®