Update: ARM Sub-Architecture Maintainers workshop at Kernel Summit 2011

[21cnbao@gmail.com (Barry Song)]

Hi Grant,
i found i am in the "Nominated, but have not yet responded " at the
URL http://www.elinux.org/Events/Kernel_Summit_2011_ARM_Subarch_Maintainership_Workshop.
i am sorry i will not attend.

2011/10/20 Jonathan Cameron <jic23@cam.ac.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
>
-barry