From: jic23@cam.ac.uk (Jonathan Cameron)
To: linux-arm-kernel@lists.infradead.org
Subject: Update: ARM Sub-Architecture Maintainers workshop at Kernel Summit 2011
Date: Thu, 20 Oct 2011 15:55:55 +0100 [thread overview]
Message-ID: <4EA0367B.7090300@cam.ac.uk> (raw)
In-Reply-To: <20111020144641.GC6100@sirena.org.uk>
On 10/20/11 15:46, Mark Brown wrote:
> On Thu, Oct 20, 2011 at 10:25:15PM +0800, Barry Song wrote:
>
>> as Jonathan knows, i was one of main authors of those drivers in
>> drivers/staging/iio. one problem for iio is now most people still
>> write sensor drivers based on input subsystem or others but not iio.
>> and Android HAL or other frameworks prefer input _event as well.
>> so to push iio ahead, we might push related app ahead too.
>
> Well, that's not entirely clear - one of the reasons for discussing an
> in kernel API is so that drivers for these subsystems can make use of
> IIO channels. Another big blocker for deployment of IIO right now is
> that it's in staging, fixing that will probably help enormously.
That and push in kernel APIs. Working on that though. Note however they
will be dependent on at least the first three sets of patches in
our original master move out of staging plan. So lots of other stuff
to get fixed up first. Some of which is probably going to be controversial.
Direct user space code will exist for the usecases we were originally
targeting, but where it makes sense, Mark has convinced me of the need
to push things out through input / hmwon. Guenter doesn't seem against
so that's a start. Dmitry has always pushed for this (though last
time we talked about it, plan was a userspace bridge).
We'll still want to be very careful to keep any users that go into
mainline on the straight an narrow wrt to pushing stuff through those
subsystems that doesn't belong.
Jonathan
next prev parent reply other threads:[~2011-10-20 14:55 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 6:00 Update: ARM Sub-Architecture Maintainers workshop at Kernel Summit 2011 Grant Likely
2011-08-30 6:27 ` Igor Grinberg
2011-08-30 13:44 ` Grant Likely
2011-08-30 14:00 ` Igor Grinberg
2011-08-30 19:17 ` [Ksummit-2011-discuss] " Chris Ball
2011-08-30 12:55 ` Nicolas Ferre
2011-08-30 13:56 ` Wolfram Sang
2011-08-30 14:42 ` David Brown
2011-08-30 16:58 ` Paul Walmsley
2011-08-30 19:51 ` Olof Johansson
2011-08-30 23:42 ` Stephen Warren
2011-08-31 5:50 ` Marek Szyprowski
2011-08-30 23:10 ` Pavel Machek
2011-08-31 1:29 ` Marek Vasut
2011-08-31 2:31 ` Bryan Wu
2011-08-31 2:58 ` Marek Vasut
2011-08-31 3:07 ` Bryan Wu
2011-08-31 18:57 ` Grant Likely
2011-08-31 2:57 ` Bryan Wu
2011-08-31 2:59 ` Marek Vasut
2011-08-31 3:08 ` Bryan Wu
2011-08-31 4:01 ` Marek Vasut
2011-08-31 5:52 ` Eric Miao
2011-08-31 15:15 ` Marc Zyngier
2011-09-27 13:25 ` Igor Grinberg
2011-10-12 9:14 ` Igor Grinberg
2011-10-12 9:19 ` Catalin Marinas
2011-10-17 17:36 ` Igor Grinberg
2011-10-12 15:33 ` Nicolas Pitre
2011-10-17 17:31 ` Igor Grinberg
2011-10-12 10:01 ` Catalin Marinas
2011-10-12 15:00 ` Nicolas Pitre
2011-10-17 8:54 ` Catalin Marinas
2011-10-17 10:56 ` Marek Vasut
2011-10-20 13:35 ` Linus Walleij
2011-10-20 13:48 ` Jonathan Cameron
2011-10-20 14:25 ` Barry Song
2011-10-20 14:46 ` Mark Brown
2011-10-20 14:55 ` Jonathan Cameron [this message]
2011-10-21 9:39 ` Barry Song
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=4EA0367B.7090300@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=linux-arm-kernel@lists.infradead.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.