On 04/10/2013 10:40 PM, Felipe Balbi wrote:
Currently the driver hard-codes USBPCTRL0 register to 0. It is wrong since this
register contains board-specific USB ports configuration and so its value should
be somehow passed via the platform data. Add file with
the USBPCTRL0 bit #define's and
Hi,
On Wed, Apr 10, 2013 at 09:44:33PM +0400, Sergei Shtylyov wrote:
> Currently the driver hard-codes USBPCTRL0 register to 0. It is wrong
> since this
> register contains board-specific USB ports configuration and so its value
> should
> be somehow passed via the platform
Hello.
On 04/10/2013 09:16 PM, Felipe Balbi wrote:
Currently the driver hard-codes USBPCTRL0 register to 0. It is wrong since this
register contains board-specific USB ports configuration and so its value should
be somehow passed via the platform data. Add file with
the USBPCTRL0 bit #define
Hi,
On Wed, Apr 10, 2013 at 06:03:49PM +0400, Sergei Shtylyov wrote:
> On 10-04-2013 13:00, Felipe Balbi wrote:
>
> >>Currently the driver hard-codes USBPCTRL0 register to 0. It is wrong since
> >>this
> >>register contains board-specific USB ports configuration and so its value
> >>should
> >
On 10-04-2013 13:00, Felipe Balbi wrote:
Currently the driver hard-codes USBPCTRL0 register to 0. It is wrong since this
register contains board-specific USB ports configuration and so its value should
be somehow passed via the platform data. Add file with
the USBPCTRL0 bit #define's and 'str
Hi,
On Wed, Apr 10, 2013 at 02:37:49AM +0400, Sergei Shtylyov wrote:
> Currently the driver hard-codes USBPCTRL0 register to 0. It is wrong since
> this
> register contains board-specific USB ports configuration and so its value
> should
> be somehow passed via the platform data. Add file wit
Currently the driver hard-codes USBPCTRL0 register to 0. It is wrong since this
register contains board-specific USB ports configuration and so its value should
be somehow passed via the platform data. Add file with
the USBPCTRL0 bit #define's and 'struct rcar_phy_platform_data' containing the
v