On 14/06/16 17:21, Alan Stern wrote:
> On Tue, 14 Jun 2016, Roger Quadros wrote:
>
>> +Alan
>>
>> On 10/06/16 16:07, Roger Quadros wrote:
>>> The OTG core will use struct otg_hcd_ops to interface
>>> with the HCD (Host Controller Driver).
>>>
>>> The main purpose of this interface is to avoid dire
On Tue, 14 Jun 2016, Roger Quadros wrote:
> +Alan
>
> On 10/06/16 16:07, Roger Quadros wrote:
> > The OTG core will use struct otg_hcd_ops to interface
> > with the HCD (Host Controller Driver).
> >
> > The main purpose of this interface is to avoid directly
> > calling HCD APIs from the OTG cor
+Alan
On 10/06/16 16:07, Roger Quadros wrote:
> The OTG core will use struct otg_hcd_ops to interface
> with the HCD (Host Controller Driver).
>
> 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 tabl
The OTG core will use struct otg_hcd_ops to interface
with the HCD (Host Controller Driver).
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-
The OTG core will use struct otg_hcd_ops to interface
with the HCD (Host Controller Device).
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-
5 matches
Mail list logo