Hi! > > > > NAK. > > > > > > > > LEDs do not need extra overhead, and vibrator control should not go > > > > through LED subsystem. > > > > > > > > Input subsystem includes support for vibrations and force > > > > feedback. Please use that instead. > > > > > > I thought we are already over this discussion. As of now, the support > > > of vibrator through ledtrig is documented > > > (Documentation/leds/ledtrig-transient.txt) and there are users using > > > it. Stop misleading people. No _users_ are using Android on mainline kernel, as there is not a single Android phone supported by mainline kernel. > > I also thought we are over with that discussion. > > > > Yes, I'm working on fixing the docs. > > > > What mainline users are doing that? > > Please refer to patch: > https://patchwork.kernel.org/patch/8664831/ and > https://android.googlesource.com/platform%2Fhardware%2Flibhardware/+/61701df363310a5cbd95e3e1638baa9526e42c9b > > I don't think currently there are drivers in the mainline using it > yet, the reason being most of the Android devices are still on 4.4 > kernel which still uses the legacy timed_output device. Ok. I'm sorry commit 61701df363310a5cbd95e3e1638baa9526e42c9b pushed your libhardware into wrong direction, but that is exactly what happened. LED subsystem is not suitable for vibrations. We have input subsystem for that, it is handling vibrations for 10+ years, and for example Nokia N900 cellphone (which is supported by mainline) uses them. Please fix libhardware accordingly. Thank you, Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Attachment:
signature.asc
Description: Digital signature
