From: Michal Simek <michal.simek@amd•com>
To: Grewstad <dogestad24@gmail•com>, Greg KH <gregkh@linuxfoundation•org>
Cc: radhey.shyam.pandey@amd•com, Andrew Lunn <andrew@lunn•ch>,
jic23@kernel•org, linux-staging@lists•linux.dev,
linux-arm-kernel@lists•infradead.org,
linux-kernel@vger•kernel.org, jacobsfeder@gmail•com, "Katakam,
Harini" <harini.katakam@amd•com>
Subject: Re: [RFC] drivers/staging/axis-fifo: Looking for users
Date: Wed, 3 Jun 2026 10:18:58 +0200 [thread overview]
Message-ID: <b05f069e-a1dd-43a5-b73d-d4c6bbb0807f@amd.com> (raw)
In-Reply-To: <CAD03fjb=_kW9=q9YV4qnQ5GD=HMB5Bx7pf3+AFcgDR2gVc1V6Q@mail.gmail.com>
Hi,
On 6/1/26 09:15, Grewstad wrote:
> Hi,
> The AXI Stream FIFO driver has been in staging since 2018. I was trying to
> understand whether there are real in-tree users of this hardware today, and
> what the expected direction for graduating the driver out of staging might be.
>
> The only in tree reference to this driver that i found is
> drivers/ethernet/xilinx/xilinx_axienet_main.c, which states:
>
> * TODO:
> * - Add Axi Fifo support.
>
> From this, it appears AXI Stream FIFO support may be used for some AXI
> Ethernet hardware configurations. However, I’m not sure whether there are
> any other in-tree users of the AXI Stream FIFO IP besides Ethernet, or
> whether Ethernet is the primary intended consumer.
It is clear that driver in current state can't be used with axi ethernet out of
box because pretty much it is just about user interface for fifo via char device
fops. But we are talking about the same IP used in specific scenario and this
driver doesn't implement integration which can be used in ethernet driver.
>
> If there are no other in-tree users, it’s unclear whether this driver should
> remain a standalone staging driver or be integrated into a specific subsystem
> like networking.
I don't think you will find out any in-tree user because driver purpose is
different. It is about providing a user way via char device to push data to axi
streaming interface which can be consumed by user logic. It is generic way how
to push data there without writing specialized kernel driver for custom HW.
> Can you let me know if there are any known in-tree users for this driver,
> whether it has a large enough user base to justify its existence in
> the kernel tree,
> and what the hardware's real use cases are?
I think this is leaf driver which provide a way to axi fifo streaming interface
where stream is connected to custom HW which consumes it. I can understand that
this can be very useful for a lot of people who wants to process data from user
space via custom logic with using streaming interface.
And I don't have any issue to agree to move the driver out of staging to common
location.
Thanks,
Michal
prev parent reply other threads:[~2026-06-03 8:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 7:15 [RFC] drivers/staging/axis-fifo: Looking for users Grewstad
2026-06-03 8:18 ` Michal Simek [this message]
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=b05f069e-a1dd-43a5-b73d-d4c6bbb0807f@amd.com \
--to=michal.simek@amd$(echo .)com \
--cc=andrew@lunn$(echo .)ch \
--cc=dogestad24@gmail$(echo .)com \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=harini.katakam@amd$(echo .)com \
--cc=jacobsfeder@gmail$(echo .)com \
--cc=jic23@kernel$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-staging@lists$(echo .)linux.dev \
--cc=radhey.shyam.pandey@amd$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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