All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Piotr Gregor <piotrgregor@rsyncme.org>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH] drivers: staging: Add driver for Amplicon PCIe215
Date: Fri, 1 Sep 2017 08:57:50 +0200	[thread overview]
Message-ID: <20170901065750.GA18770@kroah.com> (raw)
In-Reply-To: <20170831165454.nzd5xuanwwxxtezy@qq.home>

On Thu, Aug 31, 2017 at 05:54:58PM +0100, Piotr Gregor wrote:
> This is a small and simple driver for handling of external
> interrupt signal asserted on pins of Amplicon's PCIe215 board.
> There is already a Comedi driver subsystem in kernel which handles
> that (and more) board, but that framework while offering more
> flexibility brings also additional complexity at the cost of being generic.
> 
> In some cases the simpler, more compact solution may be preferred.

Note, having different drivers for the same hardware platform in the
kernel tree is a mess, and generally discouraged.  I've handled this in
the past and we hated every minute of it.

What is wrong with the comedi interface instead?

And custom ioctls for a single hardware device is horrid, what's wrong
with using the uio interface for something like this?

And finally, why staging?  While I know I wouldn't accept merging this
into the main portion of the kernel, why do you feel that adding this to
drivers/staging/ is ok?  What's so wrong with it (well, becides the
previous questions), that dumping it here is the properly location?

> The purpose of this driver is therefore to handle interrupt
> feature of the PCIe215, while being small, simple and reliable.

Why isn't comedi reliable?

thanks,

greg k-h

  reply	other threads:[~2017-09-01  6:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-31 16:54 [PATCH] drivers: staging: Add driver for Amplicon PCIe215 Piotr Gregor
2017-09-01  6:57 ` Greg Kroah-Hartman [this message]
2017-09-01  8:58   ` Piotr Gregor
2017-09-01  9:28     ` Greg Kroah-Hartman

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=20170901065750.GA18770@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piotrgregor@rsyncme.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.