Re: [PATCH 1/5] Input: bu21013_ts - Request a regulator that actually exists

2012-11-27 Thread Lee Jones
On Mon, 26 Nov 2012, Dmitry Torokhov wrote: > On Mon, Nov 26, 2012 at 12:16:18PM +, Lee Jones wrote: > > On Wed, 14 Nov 2012, Lee Jones wrote: > > > > > Currently the BU21013 Touch Screen driver requests a regulator by the > > > name of 'V-TOUCH', which doesn't exist anywhere in the kernel.

Re: [PATCH 1/5] Input: bu21013_ts - Request a regulator that actually exists

2012-11-27 Thread Lee Jones
On Mon, 26 Nov 2012, Dmitry Torokhov wrote: On Mon, Nov 26, 2012 at 12:16:18PM +, Lee Jones wrote: On Wed, 14 Nov 2012, Lee Jones wrote: Currently the BU21013 Touch Screen driver requests a regulator by the name of 'V-TOUCH', which doesn't exist anywhere in the kernel. The

Re: [PATCH 1/5] Input: bu21013_ts - Request a regulator that actually exists

2012-11-26 Thread Dmitry Torokhov
On Mon, Nov 26, 2012 at 12:16:18PM +, Lee Jones wrote: > On Wed, 14 Nov 2012, Lee Jones wrote: > > > Currently the BU21013 Touch Screen driver requests a regulator by the > > name of 'V-TOUCH', which doesn't exist anywhere in the kernel. The > > correct name, as referenced in platform

Re: [PATCH 1/5] Input: bu21013_ts - Request a regulator that actually exists

2012-11-26 Thread Lee Jones
On Wed, 14 Nov 2012, Lee Jones wrote: > Currently the BU21013 Touch Screen driver requests a regulator by the > name of 'V-TOUCH', which doesn't exist anywhere in the kernel. The > correct name, as referenced in platform regulator code is 'avdd'. Here, > when we request a regulator, we use the

Re: [PATCH 1/5] Input: bu21013_ts - Request a regulator that actually exists

2012-11-26 Thread Lee Jones
On Wed, 14 Nov 2012, Lee Jones wrote: Currently the BU21013 Touch Screen driver requests a regulator by the name of 'V-TOUCH', which doesn't exist anywhere in the kernel. The correct name, as referenced in platform regulator code is 'avdd'. Here, when we request a regulator, we use the

Re: [PATCH 1/5] Input: bu21013_ts - Request a regulator that actually exists

2012-11-26 Thread Dmitry Torokhov
On Mon, Nov 26, 2012 at 12:16:18PM +, Lee Jones wrote: On Wed, 14 Nov 2012, Lee Jones wrote: Currently the BU21013 Touch Screen driver requests a regulator by the name of 'V-TOUCH', which doesn't exist anywhere in the kernel. The correct name, as referenced in platform regulator code

Re: [PATCH 1/5] Input: bu21013_ts - Request a regulator that actually exists

2012-11-23 Thread Lee Jones
> Currently the BU21013 Touch Screen driver requests a regulator by the > name of 'V-TOUCH', which doesn't exist anywhere in the kernel. The > correct name, as referenced in platform regulator code is 'avdd'. Here, > when we request a regulator, we use the correct name instead. > > Cc: Dmitry

Re: [PATCH 1/5] Input: bu21013_ts - Request a regulator that actually exists

2012-11-23 Thread Lee Jones
Currently the BU21013 Touch Screen driver requests a regulator by the name of 'V-TOUCH', which doesn't exist anywhere in the kernel. The correct name, as referenced in platform regulator code is 'avdd'. Here, when we request a regulator, we use the correct name instead. Cc: Dmitry Torokhov

[PATCH 1/5] Input: bu21013_ts - Request a regulator that actually exists

2012-11-14 Thread Lee Jones
Currently the BU21013 Touch Screen driver requests a regulator by the name of 'V-TOUCH', which doesn't exist anywhere in the kernel. The correct name, as referenced in platform regulator code is 'avdd'. Here, when we request a regulator, we use the correct name instead. Cc: Dmitry Torokhov Cc:

[PATCH 1/5] Input: bu21013_ts - Request a regulator that actually exists

2012-11-14 Thread Lee Jones
Currently the BU21013 Touch Screen driver requests a regulator by the name of 'V-TOUCH', which doesn't exist anywhere in the kernel. The correct name, as referenced in platform regulator code is 'avdd'. Here, when we request a regulator, we use the correct name instead. Cc: Dmitry Torokhov