From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bin Gao <bin.gao@linux.intel.com>
Cc: Guenter Roeck <linux@roeck-us.net>, Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] drivers/misc: add rawio framework and drivers
Date: Wed, 23 Oct 2013 00:48:35 +0100 [thread overview]
Message-ID: <20131022234835.GB12031@kroah.com> (raw)
In-Reply-To: <20131022185004.GC53231@bingao-desk1.fm.intel.com>
On Tue, Oct 22, 2013 at 11:50:04AM -0700, Bin Gao wrote:
> On Tue, Oct 22, 2013 at 10:14:00AM -0700, Guenter Roeck wrote:
> > >
> > > You can already do this today for PCI with the UIO framework, right?
> > > Why duplicate that functionality here with another userapce API that we
> > > will then have to maintain for the next 40+ years?
> > >
> > Same for i2c, where the same functionality is supported through i2c-tools and
> > the i2c-dev driver. Adding i2c-tools to initramfs and/or to the root file system
> > should not be that much of an issue, much less than having to maintain two APIs
> > for the same purpose.
> >
> > Guenter
>
> For PCI and memory mapped I/O devices, we have the runtime pm issue that has to
> be addressed from kernel space.
Then create a UIO pci driver and you should be fine, right? That's what
others do today and it works quite well for them.
greg k-h
next prev parent reply other threads:[~2013-10-22 23:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 0:03 [PATCH 0/4] drivers/misc: add rawio framework and drivers Bin Gao
2013-10-22 5:44 ` Greg Kroah-Hartman
2013-10-22 17:14 ` Guenter Roeck
2013-10-22 18:50 ` Bin Gao
2013-10-22 23:48 ` Greg Kroah-Hartman [this message]
2013-10-22 18:19 ` Bin Gao
2013-10-22 23:47 ` 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=20131022234835.GB12031@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=bin.gao@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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