On Thu, Dec 22, 2011 at 17:57:16, Nori, Sekhar wrote:
[...]
> >
> > Well, I have one idea. We can create a separate module in
> > arch/arm/mach-davinci/, named say ohci.c, put the shared code there and
> > pass
> > to it the GPIOs actually used via a function call. Or maybe use existing
>
On Wed, Dec 21, 2011 at 17:54:49, Sergei Shtylyov wrote:
> Hello.
>
> On 21-12-2011 16:05, I wrote:
>
> >> On Wed, Dec 21, 2011 at 12:50:02, Manjunathappa, Prakash wrote:
> >>> From: Ajay Kumar Gupta
>
> >>> On this board the OHCI port's power control and over-current signals from
> >>> TPS2065
Hello.
On 21-12-2011 16:05, I wrote:
On Wed, Dec 21, 2011 at 12:50:02, Manjunathappa, Prakash wrote:
From: Ajay Kumar Gupta
On this board the OHCI port's power control and over-current signals from
TPS2065 power switch are connected via GPIO2[4] and GPIO6[13] respectively,
so we can impleme
Hello.
On 21-12-2011 13:56, Nori, Sekhar wrote:
On Wed, Dec 21, 2011 at 12:50:02, Manjunathappa, Prakash wrote:
From: Ajay Kumar Gupta
On this board the OHCI port's power control and over-current signals from
TPS2065 power switch are connected via GPIO2[4] and GPIO6[13] respectively,
so we
Hi Prakash,
On Wed, Dec 21, 2011 at 12:50:02, Manjunathappa, Prakash wrote:
> From: Ajay Kumar Gupta
>
> On this board the OHCI port's power control and over-current signals from
> TPS2065 power switch are connected via GPIO2[4] and GPIO6[13] respectively,
> so we can implement the DA8xx OHCI gl
From: Ajay Kumar Gupta
On this board the OHCI port's power control and over-current signals from
TPS2065 power switch are connected via GPIO2[4] and GPIO6[13] respectively,
so we can implement the DA8xx OHCI glue layer's hooks for overriding the
root hub port's power and over-current status bits.
