Hi Lukasz,
Revisiting this old thread...
On 21-Jun-17 1:39 PM, Lukasz Majewski wrote:
> Hi Vignesh,
[...]
This is something to consult with Lukasz then.
>>>
>>> And it seems that we are heading to adding "gadget" infrastructure
>>> to DM.
>>>
>>
>> Yes, U-Boot is moving to DM for good and
On Tue, 27 Jun 2017 14:38:38 +0530
Vignesh R wrote:
>
>
> On Thursday 22 June 2017 06:30 PM, Lukasz Majewski wrote:
> > On Thu, 22 Jun 2017 17:42:38 +0530
> > Vignesh R wrote:
> >
> >>
> >>
> >> On Wednesday 21 June 2017 01:39 PM, Lukasz Majewski wrote:
> >>> Hi Vignesh,
> >>>
> Hi,
> >>
On Thursday 22 June 2017 06:30 PM, Lukasz Majewski wrote:
> On Thu, 22 Jun 2017 17:42:38 +0530
> Vignesh R wrote:
>
>>
>>
>> On Wednesday 21 June 2017 01:39 PM, Lukasz Majewski wrote:
>>> Hi Vignesh,
>>>
Hi,
On Tuesday 20 June 2017 07:14 PM, Lukasz Majewski wrote:
> Hi Marek,
On Thu, 22 Jun 2017 17:42:38 +0530
Vignesh R wrote:
>
>
> On Wednesday 21 June 2017 01:39 PM, Lukasz Majewski wrote:
> > Hi Vignesh,
> >
> >> Hi,
> >>
> >> On Tuesday 20 June 2017 07:14 PM, Lukasz Majewski wrote:
> >>> Hi Marek, Vignesh,
> >> [...]
> >
> > All gadget drivers like ether
On Wednesday 21 June 2017 01:39 PM, Lukasz Majewski wrote:
> Hi Vignesh,
>
>> Hi,
>>
>> On Tuesday 20 June 2017 07:14 PM, Lukasz Majewski wrote:
>>> Hi Marek, Vignesh,
>> [...]
>
> All gadget drivers like ether.c or f_mass_storage.c call
> usb_gadget_handle_interrupts() just passing
Hi Vignesh,
> Hi,
>
> On Tuesday 20 June 2017 07:14 PM, Lukasz Majewski wrote:
> > Hi Marek, Vignesh,
> [...]
> >>>
> >>> All gadget drivers like ether.c or f_mass_storage.c call
> >>> usb_gadget_handle_interrupts() just passing the index of the USB
> >>> instance. This does not help at all in dm
Hi,
On Tuesday 20 June 2017 07:14 PM, Lukasz Majewski wrote:
> Hi Marek, Vignesh,
[...]
>>>
>>> All gadget drivers like ether.c or f_mass_storage.c call
>>> usb_gadget_handle_interrupts() just passing the index of the USB
>>> instance. This does not help at all in dm case. What we would need
>>> i
Hi Marek, Vignesh,
> On 06/20/2017 02:00 PM, Vignesh R wrote:
> > Hi Marek,
> >
> > On Thursday 15 June 2017 10:27 PM, Marek Vasut wrote:
> >> On 06/14/2017 02:25 PM, Vignesh R wrote:
> >> [...]
> > /**
> > * dwc3_omap_uboot_init - dwc3 omap uboot initialization code
> > * @dev:
On 06/20/2017 02:00 PM, Vignesh R wrote:
> Hi Marek,
>
> On Thursday 15 June 2017 10:27 PM, Marek Vasut wrote:
>> On 06/14/2017 02:25 PM, Vignesh R wrote:
>> [...]
> /**
> * dwc3_omap_uboot_init - dwc3 omap uboot initialization code
> * @dev: struct dwc3_omap_device containing ini
Hi Marek,
On Thursday 15 June 2017 10:27 PM, Marek Vasut wrote:
> On 06/14/2017 02:25 PM, Vignesh R wrote:
> [...]
/**
* dwc3_omap_uboot_init - dwc3 omap uboot initialization code
* @dev: struct dwc3_omap_device containing initialization data
@@ -462,3 +487,145 @@ MODULE_A
On 06/14/2017 02:25 PM, Vignesh R wrote:
[...]
>>> /**
>>> * dwc3_omap_uboot_init - dwc3 omap uboot initialization code
>>> * @dev: struct dwc3_omap_device containing initialization data
>>> @@ -462,3 +487,145 @@ MODULE_ALIAS("platform:omap-dwc3");
>>> MODULE_AUTHOR("Felipe Balbi ");
>>> MOD
On Tuesday 13 June 2017 07:33 PM, Marek Vasut wrote:
> On 06/13/2017 02:10 PM, Vignesh R wrote:
>> From: Mugunthan V N
>>
>> Add a TI DWC3 peripheral driver with driver model support and the
>> driver will be bound by the DWC3 wrapper driver based on the
>> dr_mode device tree entry.
>>
>> Signe
On 06/13/2017 02:10 PM, Vignesh R wrote:
> From: Mugunthan V N
>
> Add a TI DWC3 peripheral driver with driver model support and the
> driver will be bound by the DWC3 wrapper driver based on the
> dr_mode device tree entry.
>
> Signed-off-by: Mugunthan V N
> Signed-off-by: Vignesh R
> ---
>
From: Mugunthan V N
Add a TI DWC3 peripheral driver with driver model support and the
driver will be bound by the DWC3 wrapper driver based on the
dr_mode device tree entry.
Signed-off-by: Mugunthan V N
Signed-off-by: Vignesh R
---
drivers/usb/dwc3/core.c | 57 +++
drivers/u
14 matches
Mail list logo
