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.
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
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
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
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
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
> 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
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
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:
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
10 matches
Mail list logo