Re: [RFC PATCH 1/1] Input: add new keycodes useful in mobile devices

[Dmitry Torokhov <dmitry.torokhov@gmail.com>]

On Mon, Oct 26, 2009 at 04:43:35PM +0200, Jani Nikula wrote:
> Hi Dmitry -
> 
> On Fri, 2009-10-23 at 09:13 +0200, ext Dmitry Torokhov wrote:
> > Hi Jani,
> > 
> > On Thu, Oct 22, 2009 at 12:32:20PM +0300, Jani Nikula wrote:
> 
> > > +#define SW_PROXIMITY		0x0b  /* set = proximity sensor covered */
> > 
> > Don't quite like the name for this one, any alternatives?
> 
> SW_PROXIMITY is admittedly pretty vague, but I don't quite know how
> specific you'd like it to be. The main idea is to indicate that the
> device is covered, for example because it's in your pocket or near your
> ear, so the UI should probably adapt to the situation (for example
> disable touchscreen and display on some devices). Someone might also use
> it as a "button" you don't have to touch.
> 
> How about one of these?
> 
> SW_FRONT_COVERED
> SW_FRONT_PROXIMITY
> SW_DISPLAY_COVERED
> SW_DISPLAY_PROXIMITY
> SW_EARPIECE_MODE (too specific IMHO)
> 

Actually I like the "earpiece mode" because it describes the intended
use. Another option I think would be SW_HOLSTER_MODE. Proximity made me
think alll kinds of things but not the "phone in a pocket" scenario...

-- 
Dmitry