public inbox for kernelnewbies@kernelnewbies.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Kevin Bube <k.bube@web.de>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: [PATCH 0/2] UIO: Optional custom threaded IRQ handler
Date: Mon, 5 Jan 2026 13:45:41 +0100	[thread overview]
Message-ID: <2026010503-vitamins-slam-fa50@gregkh> (raw)
In-Reply-To: <87ikdgqm2m.fsf@web.de>

On Mon, Jan 05, 2026 at 01:29:53PM +0100, Kevin Bube wrote:
> Greg KH <gregkh@linuxfoundation.org> writes:
> > On Mon, Jan 05, 2026 at 11:21:48AM +0100, Kevin Bube wrote:
> >> Greg KH <gregkh@linuxfoundation.org> writes:
> >> > On Sat, Jan 03, 2026 at 09:06:29PM +0100, Kevin Bube wrote:
> >> >> Add an optional threaded IRQ handler to the generic UIO driver. This allows
> >> >> driver developers to keep the fast IRQ handler small and move tasks to the IRQ
> >> >> thread. We also update the documentation accordingly.
> >> >> 
> >> >> Kevin Bube (2):
> >> >>   UIO: Add optional IRQ thread callback
> >> >>   Documentation: Document threaded IRQ handler for UIO
> >> >> 
> >> >>  Documentation/driver-api/uio-howto.rst | 8 ++++++++
> >> >>  drivers/uio/uio.c                      | 6 +++++-
> >> >>  include/linux/uio_driver.h             | 2 ++
> >> >>  3 files changed, 15 insertions(+), 1 deletion(-)
> >> >
> >> > But as no in-kernel driver now uses this, it will just be removed again
> >> > :(
> >> >
> >> > Please always provide real users for api changes, otherwise we can't
> >> > determine if they are actually working or not.
> >> 
> >> I see. Thanks for taking a look.
> >
> > How was this tested if you don't have an actual user for it?  Why add it
> > if you don't have a user for it?
> 
> We have special hardware with a FPGA that requires its own customized
> driver at my dayjob. While the driver is GPL, the FPGA image is not (not
> my decision). So it makes little sense to include the driver in
> mainline.

There's no reason not to include it, so why not submit it?

> The patch is just a part of the whole change we make for our device. I
> sent it because I think it may be useful for others, too. But I
> understand that it is bad to add an API without knowing its users and
> not being able to test it. My misunderstanding was that the generic UIO
> driver is more of a framework to derive custom drivers.

We can't ever support out-of-tree drivers for obvious reasons, so just
submit your driver and then it should be fine.

thanks,

greg k-h

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

      parent reply	other threads:[~2026-01-05 12:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260103200631.4759-1-k.bube@web.de>
2026-01-04  8:41 ` [PATCH 0/2] UIO: Optional custom threaded IRQ handler Greg KH
     [not found]   ` <87ms2sqs03.fsf@web.de>
2026-01-05 10:25     ` Greg KH
     [not found]       ` <87ikdgqm2m.fsf@web.de>
2026-01-05 12:45         ` Greg KH [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=2026010503-vitamins-slam-fa50@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=k.bube@web.de \
    --cc=kernelnewbies@kernelnewbies.org \
    /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