linux-kernel - Re: Re: Re: [PATCH 4/8] Input: twl6040-vibra: Check the selected path for vibra

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 26 Sep 2011 09:41:01 +0300
From:	Péter Ujfalusi <peter.ujfalusi@...com>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc:	Samuel Ortiz <samuel.ortiz@...el.com>,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Liam Girdwood <lrg@...com>, alsa-devel@...a-project.org,
	linux-kernel@...r.kernel.org,
	Misael Lopez Cruz <misael.lopez@...com>,
	linux-input@...r.kernel.org
Subject: Re: Re: Re: [PATCH 4/8] Input: twl6040-vibra: Check the selected path for vibra

On Friday 23 September 2011 23:00:41 Dmitry Torokhov wrote:
> The application will get an error on read or write, like -ENODEV, and will
> hopefully "drop off".

Thank you for the answer, but I would still like to avoid zapping the input 
device runtime for now.
In order to do that, I need to build up some sort of notification infra for 
the twl6040 vibra (in the MFD driver) to create, and destroy the input device 
depending on the changes in the audio driver.
I'm also concerned about the needed LOC for this to implement, might be too 
overkill, since I would think that the twl6040 vibra driving method would not 
change runtime in any system.
As a note: the other vibra (twl4030-vibra) does not even let user space know, 
that it ignored the effect due to the routing selection. Returning -EBUSY is a 
bit better than that.. I know this is not a valid argument for anything ;)

Regards,
Péter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/