On Sat, May 18, 2013 at 08:56:59AM +0200, Jean-Francois Moine wrote:
> On Thu, 16 May 2013 20:26:18 +0100
> Russell King wrote:
>
> > When switching between various drivers for this device, it's possible
> > that some critical registers are left containing values which affect
> > the device opera
On Sat, May 18, 2013 at 08:56:59AM +0200, Jean-Francois Moine wrote:
> On Thu, 16 May 2013 20:26:18 +0100
> Russell King wrote:
>
> > When switching between various drivers for this device, it's possible
> > that some critical registers are left containing values which affect
> > the device opera
On Thu, 16 May 2013 20:26:18 +0100
Russell King wrote:
> When switching between various drivers for this device, it's possible
> that some critical registers are left containing values which affect
> the device operation. One such case encountered is the VIP output
> mux register. This defaults
On Thu, 16 May 2013 20:26:18 +0100
Russell King wrote:
> When switching between various drivers for this device, it's possible
> that some critical registers are left containing values which affect
> the device operation. One such case encountered is the VIP output
> mux register. This defaults
When switching between various drivers for this device, it's possible
that some critical registers are left containing values which affect
the device operation. One such case encountered is the VIP output
mux register. This defaults to 0x24 on powerup, but other drivers may
set this to 0x12. Thi
When switching between various drivers for this device, it's possible
that some critical registers are left containing values which affect
the device operation. One such case encountered is the VIP output
mux register. This defaults to 0x24 on powerup, but other drivers may
set this to 0x12. Thi
