Re: [PATCH 03/10] Input: bu21013_ts - Request a regulator that actually exists

2012-10-02 Thread Linus Walleij
On Tue, Oct 2, 2012 at 10:13 AM, 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,

[PATCH 03/10] Input: bu21013_ts - Request a regulator that actually exists

2012-10-02 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 03/10] Input: bu21013_ts - Request a regulator that actually exists

2012-10-02 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

Re: [PATCH 03/10] Input: bu21013_ts - Request a regulator that actually exists

2012-10-02 Thread Linus Walleij
On Tue, Oct 2, 2012 at 10:13 AM, Lee Jones lee.jo...@linaro.org 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