On Wed, May 11, 2016 at 06:08:15PM +0530, Sandhya Bankar wrote:
> Unnecessary [platform|pci]_set_drvdata() have been removed since the driver
> core clears the driver data to NULLafter device release or on probe failure.
> There is no need to manually clear the
> device driver data to NULL.
On Thu, Jun 02, 2016 at 05:14:05PM +0200, Hans de Goede wrote:
> From: Reinder de Haan
>
> At least the EHCI/OHCI found on the Allwinnner H3 SoC needs multiple
> reset lines, the controller will not initialize while the reset for
> its companion is still asserted, which
On Thu, Jun 02, 2016 at 09:37:28AM +0800, Lu Baolu wrote:
> In some Intel platforms, a single usb port is shared between USB host
> and device controllers. The shared port is under control of a switch
> which is defined in the Intel vendor defined extended capability for
> xHCI.
>
> This patch
On Thu, Jun 02, 2016 at 09:37:23AM +0800, Lu Baolu wrote:
> Add support to retrieve fixed voltage configure information through
> ACPI interface. This is needed for Intel Bay Trail devices, where a
> GPIO is used to control the USB vbus.
>
> Signed-off-by: Lu Baolu
>
Use compatible "atmel,sama5d2-ohci" to be capable of suspending
ports while sleep to save the power consumption.
Signed-off-by: Wenyou Yang
---
Changes in v3: None
Changes in v2:
- Use the new compatible for ohci-node.
arch/arm/boot/dts/sama5d2.dtsi | 2 +-
1 file
In order to the save power consumption, as a workaround, suspend
forcibly the USB PORTA/B/C via set the SUSPEND_A/B/C bits of OHCI
Interrupt Configuration Register in the SFRs while OHCI USB suspend.
This suspend operation must be done before the USB clock is disabled,
resume after the USB clock
To save the power consumption, add a new compatible to support forcibly
suspend the USB PORTA/B/C via OHCI Interrupt Configuration SFR Register.
Changes in v3:
- Change the compatible description for more precise.
Changes in v2:
- Add compatible to support forcibly suspend the ports.
- Add
On Tue, Jun 07, 2016 at 01:22:37PM +0300, Felipe Balbi wrote:
>
> Hi,
>
> Peter Chen writes:
> >> >> > kbuild test robot writes:
> >> >> >> tree:
> >> >> >> https://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git
> >> >> >> testing/next
Hi,
> -Original Message-
> From: Felipe Balbi [mailto:felipe.ba...@linux.intel.com]
> Sent: Tuesday, June 07, 2016 11:05 PM
> To: Roger Quadros ; Lu Baolu ;
> Jun Li ; Peter Chen
> Cc: Mathias Nyman
On Wed, Jun 08, 2016 at 08:49:55AM +0800, Herbert Xu wrote:
> On Tue, Jun 07, 2016 at 03:03:11PM -0700, Greg KH wrote:
> >
> > Ok, but usually drivers/usb/misc/ patches go through my tree :)
>
> Sorry. But I do wonder whether this driver should be moved as
> it is just an hwrng device like every
On Tue, Jun 07, 2016 at 03:03:11PM -0700, Greg KH wrote:
>
> Ok, but usually drivers/usb/misc/ patches go through my tree :)
Sorry. But I do wonder whether this driver should be moved as
it is just an hwrng device like every other driver under hw_random,
except for the fact that it happens to be
tree: https://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git
testing/next
head: fc4d1f3f522648d92d0c046beedbc1469979499a
commit: 74e51eb7b5b4f7ab33c099c20def3dce0c699006 [64/67] usb: gadget: move
gadget API functions to udc-core
config: arm-hisi_defconfig (attached as .config)
This patch adds a firmware check for the uPD720201K8-711-BAC-A
and uPD720202K8-711-BAA-A variant. Both of these chips are listed
in Renesas' R19UH0078EJ0500 Rev.5.00 "User's Manual: Hardware" as
devices which need a firmware in order to work as they do not have
support to load the firmware from an
On Tue, Jun 07, 2016 at 06:53:45PM +0800, Herbert Xu wrote:
> On Fri, Jun 03, 2016 at 12:13:06PM +0100, Bob Ham wrote:
> > Two patches to add support for the Araneus Alea I USB RNG to the
> > chaoskey driver. The first simply includes the Alea I as a device,
> > the second fixes an issue with the
On Tue, Jun 07, 2016 at 06:30:56PM +0800, Tang Jianqiang wrote:
> Hi Mathias && Balbi and ALL,
>We hit one hang issue when using DWC3 XHCI host mode to play Video
> for Isochronous transfer.
>Both usb-audio module and XHCI driver output errors.
> Our kernel version is 3.18.x.
That is
Hi,
[auto build test ERROR on usb/usb-testing]
[also build test ERROR on v4.7-rc2 next-20160607]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Ben-Dooks/USB-core-fix-missing-include-linux-usb
The RTL8153-AD supports a persistent system specific MAC address.
This means a device plugged into two different systems with host side
support will show different (but persistent) MAC addresses.
This information for the system's persistent MAC address is burned in when
the system HW is built and
The helper function usb_of_get_child_node() is defined in the
header but this was not included. Fix the warning
about usb_of_get_child_node() not being declared by adding the
right include. Fixes:
drivers/usb/core/of.c:31:20: warning: symbol 'usb_of_get_child_node' was not
declared. Should it
Hi! Another problem which I found now:
On Tuesday 07 June 2016 10:33:47 Mario Limonciello wrote:
> + ret = hex2bin(buf, obj->string.pointer + 9, 6);
> + if (!(ret == 0 && is_valid_ether_addr(buf))) {
> + netif_warn(tp, probe, tp->netdev,
> +"Invalid MAC
On Tue, 7 Jun 2016, Michał Pecio wrote:
> > Greg, in principle this should go to -stable. However, it looks like
> > this might break some applications that currently sort-of work, even
> > though they shouldn't. Therefore we have decided not to mark this
> > patch for -stable at present.
>
On Tue, Jun 07, 2016 at 07:06:00PM +0200, Marc Haber wrote:
> On Fri, Jun 03, 2016 at 08:35:11AM -0700, Greg KH wrote:
> > On Fri, Jun 03, 2016 at 08:53:58AM +0200, Marc Haber wrote:
> > > On Mon, May 30, 2016 at 01:47:12PM -0700, Greg KH wrote:
> > > > On Mon, May 30, 2016 at 09:02:54PM +0200,
On Tue, Jun 07, 2016 at 04:12:29PM +0200, Heiko Stübner wrote:
> Hi Guenter,
>
> Am Dienstag, 7. Juni 2016, 06:19:45 schrieb Guenter Roeck:
> > On Tue, Jun 7, 2016 at 2:54 AM, Heiko Stübner wrote:
> > > Hi Frank,
> > >
> > > Am Montag, 6. Juni 2016, 17:20:04 schrieb Frank Wang:
On Fri, Jun 03, 2016 at 08:35:11AM -0700, Greg KH wrote:
> On Fri, Jun 03, 2016 at 08:53:58AM +0200, Marc Haber wrote:
> > On Mon, May 30, 2016 at 01:47:12PM -0700, Greg KH wrote:
> > > On Mon, May 30, 2016 at 09:02:54PM +0200, Marc Haber wrote:
> > > > Hi,
> > > >
> > > > on my Bananapis, in
On Mon, Jun 06, 2016 at 04:28:08PM +0300, Heikki Krogerus wrote:
[ ... ]
>
> I would prefer lower case letters. I don't know the SIDs there are at
> them moment, other then Display Port. Do you know them?
>
SIDs:
0xff00 - power delivery
0xff01 - displayport
0xff02 - MHL
> Greg, in principle this should go to -stable. However, it looks like
> this might break some applications that currently sort-of work, even
> though they shouldn't. Therefore we have decided not to mark this
> patch for -stable at present.
This means leaving three longterm branches with a
The RTL8153-AD supports a persistent system specific MAC address.
This means a device plugged into two different systems with host side
support will show different (but persistent) MAC addresses.
This information for the system's persistent MAC address is burned in when
the system HW is built and
On Tue, 7 Jun 2016, Hans de Goede wrote:
> Hi,
>
> On 06-06-16 19:03, Alan Stern wrote:
> > On Mon, 6 Jun 2016, Hans de Goede wrote:
> >
> >> Hi,
> >>
> >> On 06-06-16 16:48, Greg Kroah-Hartman wrote:
> >>> On Mon, Jun 06, 2016 at 01:44:23PM +0200, Hans de Goede wrote:
> Hi All,
>
>
Hi,
Roger Quadros writes:
>> I might be able to find some time to implement a proof of concept which
>> would allow your platforms to get dual-role with code we already have,
>> but I need DWC3's OTG support which, I'm assuming, you already have :-)
>>
>> If you wanna try
On Tue, 7 Jun 2016, Chung-Geol Kim wrote:
> =
> At *remove USB(3.0) Storage
> sequence <1> --> <5> ((Problem Case))
> =
> VOLD
>
On Tue, 7 Jun 2016, Brian Park wrote:
> Hi,
> I need help with getting http://www.linux-usb.org/gadget/usb.c
> working on my Beagle Bone Black based embedded board. I'm using TI
> Processor SDK 2.00.02.11 with their linux kernel
> linux-4.1.18+gitAUTOINC+bbe8cfc1da-gbbe8cfc. My application is
On Tue, 7 Jun 2016, Michał Pecio wrote:
> > That's clear enough.
> >
> > ISO IN 1007 bytes -> 793 us
> > INT IN 32 bytes -> 35 us
> > --
> > 825 us
> >
> > The additional requirements are:
> >
> > ISO IN 48 bytes -> 45 us
On Tue, 7 Jun 2016, Michał Pecio wrote:
> Since ed_schedule begins with marking the ED as "operational",
> the ED may be left in such state even if scheduling actually
> fails.
>
> This allows future submission attempts to smuggle this ED to the
> hardware behind the scheduler's back and without
Hi Guenter,
Am Dienstag, 7. Juni 2016, 06:19:45 schrieb Guenter Roeck:
> On Tue, Jun 7, 2016 at 2:54 AM, Heiko Stübner wrote:
> > Hi Frank,
> >
> > Am Montag, 6. Juni 2016, 17:20:04 schrieb Frank Wang:
> >> The newer SoCs (rk3366, rk3399) take a different usb-phy IP block
> >>
On 07/06/16 16:09, Felipe Balbi wrote:
>
> Hi,
>
> (guys, please make sure to break lines at 80-columns)
>
> Roger Quadros writes:
>> @@ -2853,6 +2852,23 @@ static irqreturn_t dwc3_interrupt(int irq, void
>> *_evt)
>>int dwc3_gadget_init(struct dwc3 *dwc)
>>
On 07/06/16 16:04, Felipe Balbi wrote:
>
> Hi,
>
> Roger Quadros writes:
>>> But you said I must run an unnecessary OTG state machine, even thought it
>>> has nothing to do with my system, only because the two sides of my port
>>> mux device is a host and peripheral controller.
Mario Limonciello [mailto:mario_limoncie...@dell.com]
[...]
> + ret = hex2bin(buf, obj->string.pointer + 9, 6);
> + if (ret < 0 || !is_valid_ether_addr(buf)) {
> + netif_warn(tp, probe, tp->netdev, "Invalid MAC\n");
> + goto amacout;
Hi,
(guys, please make sure to break lines at 80-columns)
Roger Quadros writes:
> @@ -2853,6 +2852,23 @@ static irqreturn_t dwc3_interrupt(int irq, void
> *_evt)
>int dwc3_gadget_init(struct dwc3 *dwc)
>{
>intret;
> +
Hi,
Roger Quadros writes:
>> But you said I must run an unnecessary OTG state machine, even thought it
>> has nothing to do with my system, only because the two sides of my port
>> mux device is a host and peripheral controller.
>
> We have a minimal dual-role state machine that
On 07/06/16 12:53, Lu Baolu wrote:
> Hi,
>
> On 06/07/2016 11:03 AM, Jun Li wrote:
>> Hi Roger
>>
>>>
>>> For Mux devices implementing dual-role, the mux device driver _must_ use
>>> OTG/dual-role core API so that a common ABI is presented to user space for
>>> OTG/dual-role.
>> That's the only
On Sunday 29 May 2016 12:38:24 Pali Rohár wrote:
> > From fd67b58e3538c0732750ecad915cde736da099dc Mon Sep 17 00:00:00 2001
> > From: =?UTF-8?q?Pali=20Roh=C3=A1r?=
> > Date: Sat, 9 Jan 2016 16:57:59 +0100
> > Subject: [PATCH] musb: debugfs: Add support in testmode for
On 07/06/16 12:27, Lu Baolu wrote:
> Hi,
>
> On 06/07/2016 02:34 PM, Jun Li wrote:
On 06/07/2016 11:03 AM, Jun Li wrote:
>> Hi Roger
>>
For Mux devices implementing dual-role, the mux device driver _must_
use OTG/dual-role core API so that a common ABI is
On 07/06/16 14:49, Grygorii Strashko wrote:
> On 06/07/2016 12:34 PM, Roger Quadros wrote:
>> On 02/06/16 14:52, Grygorii Strashko wrote:
>>> On 06/01/2016 10:46 AM, Roger Quadros wrote:
Implementations might use different IRQs for
host, gadget and OTG so use named interrupt resources
On 06/07/2016 12:34 PM, Roger Quadros wrote:
> On 02/06/16 14:52, Grygorii Strashko wrote:
>> On 06/01/2016 10:46 AM, Roger Quadros wrote:
>>> Implementations might use different IRQs for
>>> host, gadget and OTG so use named interrupt resources
>>> to allow Device tree to specify the 3
>-Original Message-
>From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-ow...@vger.kernel.org]
>On Behalf Of Krzysztof Opasiak
>Sent: Tuesday, June 07, 2016 3:46 PM
>To: Peter Chen
>Cc: Krzysztof Opasiak ; ba...@kernel.org; Greg Kroah-
On Fri, Jun 03, 2016 at 12:13:06PM +0100, Bob Ham wrote:
> Two patches to add support for the Araneus Alea I USB RNG to the
> chaoskey driver. The first simply includes the Alea I as a device,
> the second fixes an issue with the timeout on the first read.
>
> Bob Ham (2):
> hwrng: chaoskey -
Hi Mathias && Balbi and ALL,
We hit one hang issue when using DWC3 XHCI host mode to play Video
for Isochronous transfer.
Both usb-audio module and XHCI driver output errors.
Our kernel version is 3.18.x.
And already include Mathias's commit:
1> xhci: fix off by one error in TRB
Since ed_schedule begins with marking the ED as "operational",
the ED may be left in such state even if scheduling actually
fails.
This allows future submission attempts to smuggle this ED to the
hardware behind the scheduler's back and without linking it to
the ohci->eds_in_use list.
The former
It's know that Intel's SoCs' dwc3 integration is
peripheral-only since Intel implements its own
portmux for role-swapping. In order to prevent dwc3
from ever registering and XHCI platform_device,
let's just set dr-mode to peripheral-only on Intel
SoCs.
Signed-off-by: Felipe Balbi
We shouldn't change a host-only dwc3 to gadget-only
if driver is built as gadget-only. Fix that up here.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/core.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/dwc3/core.c
Hi,
Peter Chen writes:
>> >> > kbuild test robot writes:
>> >> >> tree: https://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git
>> >> >> testing/next
>> >> >> head: 89fe2b5ab11cdf6a67d4492d893e70e330aa7060
>> >> >> commit:
Hi,
Just to add my tested-by to the patch sent by Grygorii Strashko on 03/31/2016
(https://lkml.org/lkml/2016/3/31/609).
The patch was tested on a v4.6 kernel, running in a Juno r1 development board,
being the USB 3.0 Host prototyped in a FPGA.
Tested-by: Joao Pinto
Hi,
On Tue, Jun 7, 2016 at 11:06 AM, Peter Chen wrote:
>
>
>>-Original Message-
>>From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-ow...@vger.kernel.org]
>>On Behalf Of Krzysztof Opasiak
>>Sent: Tuesday, June 07, 2016 3:46 PM
>>To: Peter Chen
Hi,
On 06-06-16 19:03, Alan Stern wrote:
On Mon, 6 Jun 2016, Hans de Goede wrote:
Hi,
On 06-06-16 16:48, Greg Kroah-Hartman wrote:
On Mon, Jun 06, 2016 at 01:44:23PM +0200, Hans de Goede wrote:
Hi All,
While looking at libusb today I ended up looking at the
reap-after-disconnect code.
On Tue, Jun 07, 2016 at 12:36:13PM +0300, Felipe Balbi wrote:
>
> Hi,
>
> Peter Chen writes:
> > On Mon, Jun 06, 2016 at 04:16:17PM +0300, Felipe Balbi wrote:
> >>
> >> Hi,
> >>
> >> Felipe Balbi writes:
> >> > [ Unknown signature status ]
Hi Frank,
Am Montag, 6. Juni 2016, 17:20:04 schrieb Frank Wang:
> The newer SoCs (rk3366, rk3399) take a different usb-phy IP block
> than rk3288 and before, and most of phy-related registers are also
> different from the past, so a new phy driver is required necessarily.
>
> Signed-off-by:
Hi,
On 06/07/2016 11:03 AM, Jun Li wrote:
> Hi Roger
>
>>
>> For Mux devices implementing dual-role, the mux device driver _must_ use
>> OTG/dual-role core API so that a common ABI is presented to user space for
>> OTG/dual-role.
> That's the only point we have concern, do dual role switch
Hi,
Roger Quadros writes:
>> Roger Quadros writes:
>>> On 30/05/16 14:35, Felipe Balbi wrote:
this patch implements the most basic pm_runtime
support for dwc3. Whenever USB cable is dettached,
then we will allow core to runtime_suspend.
Hi,
Brian Park writes:
> I need help with getting http://www.linux-usb.org/gadget/usb.c working
> on my Beagle Bone Black based embedded board. I'm using TI Processor
> SDK 2.00.02.11 with their linux kernel
> linux-4.1.18+gitAUTOINC+bbe8cfc1da-gbbe8cfc. My application
Hi,
Peter Chen writes:
> On Mon, Jun 06, 2016 at 04:16:17PM +0300, Felipe Balbi wrote:
>>
>> Hi,
>>
>> Felipe Balbi writes:
>> > [ Unknown signature status ]
>> >
>> > Hi,
>> >
>> > kbuild test robot writes:
>> >>
On 02/06/16 14:52, Grygorii Strashko wrote:
> On 06/01/2016 10:46 AM, Roger Quadros wrote:
>> Implementations might use different IRQs for
>> host, gadget and OTG so use named interrupt resources
>> to allow Device tree to specify the 3 interrupts.
>>
>> Following are the interrupt names
>>
>>
Felipe,
On 01/06/16 11:06, Felipe Balbi wrote:
>
> Hi,
>
> Roger Quadros writes:
>> Implementations might use different IRQs for
>> host, gadget and OTG so use named interrupt resources
>> to allow Device tree to specify the 3 interrupts.
>>
>> Following are the interrupt names
On 06/03/2016 04:02 AM, Rob Herring wrote:
>> Optional properties:
>> - reset-gpios : contains a list of GPIO specifiers. The reset GPIOs are
>> asserted
>> @@ -16,6 +22,7 @@ Optional properties:
>>See ../clocks/clock-bindings.txt for details.
>> - clock-names : Must include the following
Hi,
On 06/07/2016 02:34 PM, Jun Li wrote:
>> > On 06/07/2016 11:03 AM, Jun Li wrote:
>>> > > Hi Roger
>>> > >
> >>
> >> For Mux devices implementing dual-role, the mux device driver _must_
> >> use OTG/dual-role core API so that a common ABI is presented to user
> >> space for
On Tue, 07 Jun 2016, Lee Jones wrote:
> On Tue, 07 Jun 2016, Peter Griffin wrote:
>
> > Hi,
> >
> > On Mon, 06 Jun 2016, Lee Jones wrote:
> >
> > > Phasing out generic reset line requests enables us to make some better
> > > decisions on when and how to (de)assert said lines. If an
Felipe,
On 30/05/16 15:42, Felipe Balbi wrote:
>
> Hi,
>
> Roger Quadros writes:
>> On 30/05/16 14:35, Felipe Balbi wrote:
>>> this patch implements the most basic pm_runtime
>>> support for dwc3. Whenever USB cable is dettached,
>>> then we will allow core to runtime_suspend.
Signed-off-by: Frank Wang
---
Changes in v4:
- Used 'phy-supply' instead of 'vbus_*-supply'.
Changes in v3:
- Added 'clocks' and 'clock-names' optional properties.
- Specified 'otg-port' and 'host-port' as the sub-node name.
Changes in v2:
- Changed vbus_host
The newer SoCs (rk3366, rk3399) take a different usb-phy IP block
than rk3288 and before, and most of phy-related registers are also
different from the past, so a new phy driver is required necessarily.
Signed-off-by: Frank Wang
---
Changes in v4:
- Removed some
The newer SoCs (rk3366, rk3399) of Rock-chip take a different usb-phy
IP block than rk3288 and before, and most of phy-related registers are
also different from the past, so a new phy driver is required necessarily.
These series patches add phy-rockchip-inno-usb2.c and the corresponding
On Tue, 07 Jun 2016, Peter Griffin wrote:
> Hi,
>
> On Mon, 06 Jun 2016, Lee Jones wrote:
>
> > Phasing out generic reset line requests enables us to make some better
> > decisions on when and how to (de)assert said lines. If an 'exclusive'
> > line is requested, we know a device *requires* a
On Monday 06 June 2016 10:38 PM, Lee Jones wrote:
> On the STiH410 B2120 development board the ports on the Generic PHY
> share their reset lines with each other. New functionality in the
> reset subsystems forces consumers to be explicit when requesting
> shared/exclusive reset lines.
>
>
On Monday 06 June 2016 09:26 PM, Lee Jones wrote:
> On the STiH410 B2120 development board the MiPHY28lp shares its reset
> line with the Synopsys DWC3 SuperSpeed (SS) USB 3.0 Dual-Role-Device
> (DRD). New functionality in the reset subsystems forces consumers to
> be explicit when requesting
Hi,
On Mon, 06 Jun 2016, Lee Jones wrote:
> Phasing out generic reset line requests enables us to make some better
> decisions on when and how to (de)assert said lines. If an 'exclusive'
> line is requested, we know a device *requires* a reset and that it's
> preferable to act upon a request
On Mon, 06 Jun 2016, Lee Jones wrote:
> On the STiH410 B2120 development board the ST EHCI IP shares its reset
> line with the OHCI IP. New functionality in the reset subsystems forces
> consumers to be explicit when requesting shared/exclusive reset lines.
>
> Signed-off-by: Lee Jones
Hi Lee,
On Mon, 06 Jun 2016, Lee Jones wrote:
> On the STiH410 B2120 development board the MiPHY28lp shares its reset
> line with the Synopsys DWC3 SuperSpeed (SS) USB 3.0 Dual-Role-Device
> (DRD). New functionality in the reset subsystems forces consumers to
> be explicit when requesting
On Mon, 06 Jun 2016, Lee Jones wrote:
> On the STiH410 B2120 development board the MiPHY28lp shares its reset
> line with the Synopsys DWC3 SuperSpeed (SS) USB 3.0 Dual-Role-Device
> (DRD). New functionality in the reset subsystems forces consumers to
> be explicit when requesting
On Mon, 06 Jun 2016, Lee Jones wrote:
> On the STiH410 B2120 development board the ports on the Generic PHY
> share their reset lines with each other. New functionality in the
> reset subsystems forces consumers to be explicit when requesting
> shared/exclusive reset lines.
>
> Signed-off-by:
On Mon, Jun 06, 2016 at 03:35:35PM +0200, Oliver Neukum wrote:
> On Mon, 2016-06-06 at 16:28 +0300, Heikki Krogerus wrote:
>
> > I would prefer lower case letters. I don't know the SIDs there are at
> > them moment, other then Display Port. Do you know them?
> >
> > I don't think we can ever
Hi Kishon & Heiko,
On 2016/6/7 15:45, Kishon Vijay Abraham I wrote:
Hi,
On Tuesday 07 June 2016 09:01 AM, Frank Wang wrote:
Hi Heiko,
On 2016/6/7 10:59, Frank Wang wrote:
Hi Heiko & Mark,
On 2016/6/6 20:33, Heiko Stübner wrote:
Am Montag, 6. Juni 2016, 12:27:54 schrieb Mark Rutland:
On
Hi Frank,
Am Dienstag, 7. Juni 2016, 11:31:59 schrieb Frank Wang:
> On 2016/6/7 10:59, Frank Wang wrote:
> > On 2016/6/6 20:33, Heiko Stübner wrote:
> >> Am Montag, 6. Juni 2016, 12:27:54 schrieb Mark Rutland:
> >>> On Mon, Jun 06, 2016 at 05:20:03PM +0800, Frank Wang wrote:
> Signed-off-by:
Hi! Below are my comments, all about coding style.
On Monday 06 June 2016 12:19:29 Mario Limonciello wrote:
> The RTL8153-AD supports a persistent system specific MAC address.
> This means a device plugged into two different systems with host side
> support will show different (but persistent)
Hi,
On Tuesday 07 June 2016 09:01 AM, Frank Wang wrote:
> Hi Heiko,
>
> On 2016/6/7 10:59, Frank Wang wrote:
>> Hi Heiko & Mark,
>>
>> On 2016/6/6 20:33, Heiko Stübner wrote:
>>> Am Montag, 6. Juni 2016, 12:27:54 schrieb Mark Rutland:
On Mon, Jun 06, 2016 at 05:20:03PM +0800, Frank Wang
Hi,
On Tue, Jun 7, 2016 at 3:27 AM, Peter Chen wrote:
> On Mon, Jun 06, 2016 at 09:40:33PM +0200, Krzysztof Opasiak wrote:
>> Currently it is possible to build in some subset of usb functions
>> *OR* some gadget module. This is limited only by Kconfig not
>> any
Hi Baolu
> -Original Message-
> From: Lu Baolu [mailto:baolu...@linux.intel.com]
> Sent: Tuesday, June 07, 2016 2:27 PM
> To: Jun Li ; Roger Quadros ; Peter Chen
>
> Cc: felipe.ba...@linux.intel.com; Mathias Nyman
Hi Jun,
On 06/07/2016 11:03 AM, Jun Li wrote:
> Hi Roger
>
>>
>> For Mux devices implementing dual-role, the mux device driver _must_ use
>> OTG/dual-role core API so that a common ABI is presented to user space for
>> OTG/dual-role.
> That's the only point we have concern, do dual role switch
On 06/06/2016 10:43 PM, Heiko Stübner wrote:
> Hi,
>
> Am Mittwoch, 1. Juni 2016, 10:02:09 schrieb Krzysztof Kozlowski:
>> My third approach for a USB power sequence which fixes usb3503+lan
>> on Odroid U3 board if it was initialized by bootloader
>> (e.g. for TFTP boot).
>
> I was just tackling
85 matches
Mail list logo