On 09/06/16 17:11, Alan Stern wrote:
> On Thu, 9 Jun 2016, Sergei Shtylyov wrote:
>
>> Hello.
>>
>> On 6/9/2016 10:31 AM, Roger Quadros wrote:
>>
>>> The OTG core will use struct otg_hcd_ops to interface
>>> with the HCD controller.
>>
>>Host controller driver (HCD)
On 09/06/16 17:11, Alan Stern wrote:
> On Thu, 9 Jun 2016, Sergei Shtylyov wrote:
>
>> Hello.
>>
>> On 6/9/2016 10:31 AM, Roger Quadros wrote:
>>
>>> The OTG core will use struct otg_hcd_ops to interface
>>> with the HCD controller.
>>
>>Host controller driver (HCD)
On Thu, 9 Jun 2016, Sergei Shtylyov wrote:
> Hello.
>
> On 6/9/2016 10:31 AM, Roger Quadros wrote:
>
> > The OTG core will use struct otg_hcd_ops to interface
> > with the HCD controller.
>
> Host controller driver (HCD) controller? Maybe just HC? :-)
> >>>
> >>> OK.
> >>
>
On Thu, 9 Jun 2016, Sergei Shtylyov wrote:
> Hello.
>
> On 6/9/2016 10:31 AM, Roger Quadros wrote:
>
> > The OTG core will use struct otg_hcd_ops to interface
> > with the HCD controller.
>
> Host controller driver (HCD) controller? Maybe just HC? :-)
> >>>
> >>> OK.
> >>
>
Hello.
On 6/9/2016 10:31 AM, Roger Quadros wrote:
The OTG core will use struct otg_hcd_ops to interface
with the HCD controller.
Host controller driver (HCD) controller? Maybe just HC? :-)
OK.
OTOH, my googling has shown that HCD may stand for both HC driver and HC
device... The
Hello.
On 6/9/2016 10:31 AM, Roger Quadros wrote:
The OTG core will use struct otg_hcd_ops to interface
with the HCD controller.
Host controller driver (HCD) controller? Maybe just HC? :-)
OK.
OTOH, my googling has shown that HCD may stand for both HC driver and HC
device... The
On 08/06/16 15:10, Sergei Shtylyov wrote:
> On 6/8/2016 3:04 PM, Roger Quadros wrote:
>
The OTG core will use struct otg_hcd_ops to interface
with the HCD controller.
>>>
>>>Host controller driver (HCD) controller? Maybe just HC? :-)
>>
>> OK.
>
>OTOH, my googling has shown
On 08/06/16 15:10, Sergei Shtylyov wrote:
> On 6/8/2016 3:04 PM, Roger Quadros wrote:
>
The OTG core will use struct otg_hcd_ops to interface
with the HCD controller.
>>>
>>>Host controller driver (HCD) controller? Maybe just HC? :-)
>>
>> OK.
>
>OTOH, my googling has shown
On 6/8/2016 3:04 PM, Roger Quadros wrote:
The OTG core will use struct otg_hcd_ops to interface
with the HCD controller.
Host controller driver (HCD) controller? Maybe just HC? :-)
OK.
OTOH, my googling has shown that HCD may stand for both HC driver and HC
device... The host
On 6/8/2016 3:04 PM, Roger Quadros wrote:
The OTG core will use struct otg_hcd_ops to interface
with the HCD controller.
Host controller driver (HCD) controller? Maybe just HC? :-)
OK.
OTOH, my googling has shown that HCD may stand for both HC driver and HC
device... The host
Hi,
On 08/06/16 14:39, Sergei Shtylyov wrote:
> Hello.
>
> On 6/8/2016 12:03 PM, Roger Quadros wrote:
>
>> The OTG core will use struct otg_hcd_ops to interface
>> with the HCD controller.
>
>Host controller driver (HCD) controller? Maybe just HC? :-)
OK.
>
>> The main purpose of this
Hi,
On 08/06/16 14:39, Sergei Shtylyov wrote:
> Hello.
>
> On 6/8/2016 12:03 PM, Roger Quadros wrote:
>
>> The OTG core will use struct otg_hcd_ops to interface
>> with the HCD controller.
>
>Host controller driver (HCD) controller? Maybe just HC? :-)
OK.
>
>> The main purpose of this
Hello.
On 6/8/2016 12:03 PM, Roger Quadros wrote:
The OTG core will use struct otg_hcd_ops to interface
with the HCD controller.
Host controller driver (HCD) controller? Maybe just HC? :-)
The main purpose of this interface is to avoid directly
calling HCD APIs from the OTG core as they
Hello.
On 6/8/2016 12:03 PM, Roger Quadros wrote:
The OTG core will use struct otg_hcd_ops to interface
with the HCD controller.
Host controller driver (HCD) controller? Maybe just HC? :-)
The main purpose of this interface is to avoid directly
calling HCD APIs from the OTG core as they
The OTG core will use struct otg_hcd_ops to interface
with the HCD controller.
The main purpose of this interface is to avoid directly
calling HCD APIs from the OTG core as they
wouldn't be defined in the built-in symbol table if
CONFIG_USB is m.
Signed-off-by: Roger Quadros
The OTG core will use struct otg_hcd_ops to interface
with the HCD controller.
The main purpose of this interface is to avoid directly
calling HCD APIs from the OTG core as they
wouldn't be defined in the built-in symbol table if
CONFIG_USB is m.
Signed-off-by: Roger Quadros
Acked-by: Peter
16 matches
Mail list logo