From: "Ahmed S. Darwish" <darwish.07@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Rob Springer <rspringer@google.com>,
John Joseph <jnjoseph@google.com>, Simon Que <sque@chromium.org>,
Todd Poynor <toddpoynor@google.com>,
linux-kernel@vger.kernel.org, devel@linuxdriverproject.org
Subject: Re: [GIT PULL] Staging/IIO driver patches for 4.19-rc1
Date: Tue, 28 Aug 2018 10:38:17 +0000 [thread overview]
Message-ID: <20180828103817.GB1397@do-kernel> (raw)
In-Reply-To: <20180818155724.GA22569@kroah.com>
[ re-send; forgotten lkml CC added; sorry ]
Hi,
On Sat, 18 Aug 2018 17:57:24 +0200, Greg KH wrote:
[...]
> addition of some new IIO drivers. Also added was a "gasket" driver from
> Google that needs loads of work and the erofs filesystem.
>
Why are we adding __a whole new in-kernel framework__ for
developing basic user-space drivers?
We already have a frameowrk for that, and it's UIO. [1] The UIO
code is a very stable and simple subsystem; it's also heavily used
in the embedded industry..
I've looked at the gasket documentation [2], and the first user
of this new in-kernel API [3], and this is almost replicating UIO
it's not funny. [4] True, the gasket APIs adds some extra new
conveniences (PCI BAR re-mapping, MSI, ..), but there's no
technical reason this cannot be added to the UIO code instead.
More-over, the exposed user-space API is just some ioctls. So if
google hase some shipped user-space code that is using this,
hopefully the driver can still be re-implemented through UIO
without changing these bits..
Thanks,
[1] https://www.kernel.org/doc/html/v4.18/driver-api/uio-howto.html
[2] drivers/staging/gasket/gasket_core.h :: struct gasket_driver_desc
[3] drivers/staging/gasket/apex_driver.c
[4] include/linux/uio_driver.h
--
Darwi
http://darwish.chasingpointers.com
next prev parent reply other threads:[~2018-08-28 10:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-18 15:57 [GIT PULL] Staging/IIO driver patches for 4.19-rc1 Greg KH
2018-08-18 18:00 ` Linus Torvalds
2018-08-19 6:07 ` Greg Kroah-Hartman
2018-08-28 10:38 ` Ahmed S. Darwish [this message]
2018-08-28 11:20 ` Todd Poynor
2018-08-28 12:36 ` Greg KH
2018-08-28 14:30 ` Ahmed S. Darwish
2018-09-10 8:16 ` Greg KH
2018-09-10 15:28 ` [PATCH] staging: gasket: TODO: re-implement using UIO Ahmed S. Darwish
2018-11-07 0:20 ` RFC: staging: gasket: " Todd Poynor
2018-11-07 9:20 ` Greg KH
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=20180828103817.GB1397@do-kernel \
--to=darwish.07@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=jnjoseph@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rspringer@google.com \
--cc=sfr@canb.auug.org.au \
--cc=sque@chromium.org \
--cc=toddpoynor@google.com \
--cc=torvalds@linux-foundation.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