On Wed, Mar 11, 2015 at 04:13:28PM +0530, Anjana V Kumar wrote:
> Hi David,
Hi Anjana,
I'd be nice to bottom post your replies. That's the standard here on
community :)
>
> Its a single phy for both host and device modes.
Just a brainstorm:
AFAIU your phy is responsible for the ID detection, s
Hi David,
Its a single phy for both host and device modes.
Thanks
Anjana
On Wed, Mar 11, 2015 at 3:36 AM, David Cohen
wrote:
> Hi Anjana,
>
> On Tue, Mar 03, 2015 at 09:27:09AM +0800, Peter Chen wrote:
>> On Mon, Mar 02, 2015 at 11:47:31AM +0530, Anjana V Kumar wrote:
>> > Hi Peter,
>> >
>> > I
Hi Anjana,
On Tue, Mar 03, 2015 at 09:27:09AM +0800, Peter Chen wrote:
> On Mon, Mar 02, 2015 at 11:47:31AM +0530, Anjana V Kumar wrote:
> > Hi Peter,
> >
> > I will need to configure both the phy and the controller.
> >
> > Thanks
> > Anjana
> >
> > On Mon, Mar 2, 2015 at 11:24 AM, Peter Chen
On Mon, Mar 02, 2015 at 11:47:31AM +0530, Anjana V Kumar wrote:
> Hi Peter,
>
> I will need to configure both the phy and the controller.
>
> Thanks
> Anjana
>
> On Mon, Mar 2, 2015 at 11:24 AM, Peter Chen wrote:
> >
> >
> >> This is regarding the registering and handling of ID interrupt to swi
Hi Peter,
I will need to configure both the phy and the controller.
Thanks
Anjana
On Mon, Mar 2, 2015 at 11:24 AM, Peter Chen wrote:
>
>
>> This is regarding the registering and handling of ID interrupt to swich
>> between
>> host and device mode.
>>
>> My aim is to have OTG functionality for
> This is regarding the registering and handling of ID interrupt to swich
> between
> host and device mode.
>
> My aim is to have OTG functionality for a not-OTG phy.
>
> We wanted to register an ID interrupt which fires of change in ID value. Based
> on this ID value, we need to configure th
