Hi Oleksij,
On Wed, 2016-07-06 at 12:32 +0200, fixed-term.Oleksij.Rempel wrote:
>
> On 06.07.2016 11:30, Alexey Brodkin wrote:
> >
> > Hi Oleksij,
> >
> > On Wed, 2016-07-06 at 11:09 +0200, fixed-term.Oleksij.Rempel wrote:
> > >
> > >
> > > On 06.07.2016 10:45, Alexey Brodkin wrote:
> > > >
This patch adds the devicetree documentation required for Rockchip
USB3.0 core wrapper consisting of USB3.0 IP from Synopsys.
It supports DRD mode, and could operate in device mode (SS, HS, FS)
and host mode (SS, HS, FS, LS).
Signed-off-by: William Wu
---
Changes in v6:
- rename bus_clk, and add
This series add support for rockchip dwc3 driver,
and add additional optional properties for specific
platforms (e.g., rockchip rk3399 platform).
William Wu (5):
usb: dwc3: of-simple: add compatible for rockchip rk3399
usb: dwc3: add dis_u2_freeclk_exists_quirk
usb: dwc3: add phyif_utmi_quir
Add a quirk to clear the GUSB3PIPECTL.DELAYP1TRANS bit,
which specifies whether disable delay PHY power change
from P0 to P1/P2/P3 when link state changing from U0
to U1/U2/U3 respectively.
Signed-off-by: William Wu
---
Changes in v6:
- use '-' instead of '_' in dts (Rob Herring)
Changes in v5:
Rockchip platform merely enable usb3 clocks and
populate its children. So we can use this generic
glue layer to support Rockchip dwc3.
Signed-off-by: William Wu
---
Changes in v6:
- None
Changes in v5:
- change compatible from "rockchip,dwc3" to "rockchip,rk3399-dwc3" (Heiko)
Changes in v4:
- N
Add a quirk to configure the core to support the
UTMI+ PHY with an 8- or 16-bit interface. UTMI+ PHY
interface is hardware property, and it's platform
dependent. Normall, the PHYIf can be configured
during coreconsultant. But for some specific usb
cores(e.g. rk3399 soc dwc3), the default PHYIf
conf
Add a quirk to clear the GUSB2PHYCFG.U2_FREECLK_EXISTS bit,
which specifies whether the USB2.0 PHY provides a free-running
PHY clock, which is active when the clock control input is active.
Signed-off-by: William Wu
---
Changes in v6:
- use '-' instead of '_' in dts (Rob Herring)
Changes in v5:
BugLink: http://bugs.launchpad.net/bugs/1498667
As reported in BugLink, this device has an issue with Linux Power
Management so adding a quirk. This quirk was reccomended by Alan Stern:
http://lkml.iu.edu/hypermail/linux/kernel/1606.2/05590.html
Signed-off-by: Joseph Salisbury
Cc: stable
---
Hi,
[auto build test ERROR on balbi-usb/next]
[also build test ERROR on v4.7-rc6 next-20160706]
[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/Krzysztof-Opasiak/usb-gadget-legacy-Add-udc-module
On 07/06/2016 09:02 PM, Greg KH wrote:
> On Wed, Jul 06, 2016 at 08:58:14PM -0400, Joseph Salisbury wrote:
>> BugLink: http://bugs.launchpad.net/bugs/1498667
>>
>> As reported in BugLink, this device has an issue with Linux Power
>> Management so adding a quirk. This quirk was reccomended by Alan
On Wed, Jul 06, 2016 at 08:58:14PM -0400, Joseph Salisbury wrote:
> BugLink: http://bugs.launchpad.net/bugs/1498667
>
> As reported in BugLink, this device has an issue with Linux Power
> Management so adding a quirk. This quirk was reccomended by Alan Stern:
>
> http://lkml.iu.edu/hypermail/li
BugLink: http://bugs.launchpad.net/bugs/1498667
As reported in BugLink, this device has an issue with Linux Power
Management so adding a quirk. This quirk was reccomended by Alan Stern:
http://lkml.iu.edu/hypermail/linux/kernel/1606.2/05590.html
Signed-off-by: Joseph Salisbury
Cc: stable
---
On 07/06/2016 07:10 PM, Greg KH wrote:
> On Wed, Jul 06, 2016 at 05:53:47PM -0400, Joseph Salisbury wrote:
>> BugLink: http://bugs.launchpad.net/bugs/1498667
>>
>> As reported in BugLink, this device has an issue with Linux Power Management
>> so
>> adding a quirk. This quirk was reccomended by
On Wed, Jul 06, 2016 at 05:53:47PM -0400, Joseph Salisbury wrote:
> BugLink: http://bugs.launchpad.net/bugs/1498667
>
> As reported in BugLink, this device has an issue with Linux Power Management
> so
> adding a quirk. This quirk was reccomended by Alan Stern:
>
> http://lkml.iu.edu/hypermail
On Wed, Jul 06, 2016 at 08:00:55PM +0200, Ziutek Putek wrote:
> [1.] Booting from Sandisk USB stick fails and stops on Dell Latitude E5420
> Laptop.
>
> [2.] On mainline kernel I get error:
> [ 18.414128] usb 2-1.4: device descriptor read/64, error -110
> [ 23.601028] usb 2-1.4: device descriptor
BugLink: http://bugs.launchpad.net/bugs/1498667
As reported in BugLink, this device has an issue with Linux Power Management so
adding a quirk. This quirk was reccomended by Alan Stern:
http://lkml.iu.edu/hypermail/linux/kernel/1606.2/05590.html
Signed-off-by: Joseph Salisbury
Cc: stable
--
On 06/28/2016 11:40 AM, Alan Stern wrote:
> On Tue, 28 Jun 2016, Joseph Salisbury wrote:
>
>> On 06/24/2016 08:06 AM, Joseph Salisbury wrote:
>>> On 06/22/2016 12:14 PM, Greg KH wrote:
On Wed, Jun 22, 2016 at 11:38:43AM -0400, Joseph Salisbury wrote:
> Hi Rupesh,
>
> A kernel bug r
Hi,
[auto build test WARNING on balbi-usb/next]
[also build test WARNING on v4.7-rc6 next-20160706]
[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/Krzysztof-Opasiak/usb-gadget-legacy-Add-udc
On Wed, 6 Jul 2016, Oliver Neukum wrote:
> On Tue, 2016-07-05 at 15:48 +0200, Micha* Pecio wrote:
> > So this patch should go to 3.18+ to fix those crashes. I think I've
> > posted my findings to linux-usb but apparently they were missed or
> > forgotten and I forgot about this matter too.
>
> If
[1.] Booting from Sandisk USB stick fails and stops on Dell Latitude E5420
Laptop.
[2.] On mainline kernel I get error:
[ 18.414128] usb 2-1.4: device descriptor read/64, error -110
[ 23.601028] usb 2-1.4: device descriptor read/64, error -71
[ 23.777126] usb 2-1.4: new high-speed USB device numb
Hi,
sorry that it took sooo long but I was out of office for over a month.
On 06/09/2016 09:45 AM, Krzysztof Opasiak wrote:
(...)
>> Yes, currently, we can't do that even the gadget is module, but the
>> change may not be small. Now, we have configfs, it is not so necessary
>> to add this fu
Hi,
Sorry for my late response but I was out of office for quite a long time.
On 06/21/2016 09:58 AM, Felipe Balbi wrote:
> Krzysztof Opasiak writes:
>
>> 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:
Cur
Currently it is possible to build in some subset of usb functions
*OR* some gadget module. This is limited only by Kconfig not
any functionality.
This patch removes this limitation. With this patch it is possible
to set up all build combinations:
1) Multiple gadgets build in
2) Part of functions b
Add new module parameter called "udc" to all legacy gadgets.
By using this parameter user can choose a controller towhich
this gadget should be bound.
This may be useful esp. when having multiple controllers
or multiple gadget builtin.
When value for this param is not provided then old behaviour
On Wed, Jul 6, 2016 at 3:42 PM, Johan Hovold wrote:
> [ +CC: linux-usb, for real this time ;) ]
>
> On Wed, Jul 06, 2016 at 02:40:25PM +0530, Malith Yapa wrote:
>> On Wed, Jul 6, 2016 at 2:13 PM, Johan Hovold wrote:
>> > [ Please avoid top-posing. ]
>> >
>> > On Wed, Jul 06, 2016 at 03:49:15AM +0
[ +CC: linux-usb, for real this time ;) ]
On Wed, Jul 06, 2016 at 02:40:25PM +0530, Malith Yapa wrote:
> On Wed, Jul 6, 2016 at 2:13 PM, Johan Hovold wrote:
> > [ Please avoid top-posing. ]
> >
> > On Wed, Jul 06, 2016 at 03:49:15AM +, Malith Yapa wrote:
> >> I'm polling a couple of input bi
The LAN_WAKE_EN is not used to determine if the device could support
WOL. It is used to signal a GPIO pin when a WOL event occurs. The WOL
still works even though it is disabled.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
d
Hi Oleksij,
On Wed, 2016-07-06 at 11:09 +0200, fixed-term.Oleksij.Rempel wrote:
>
> On 06.07.2016 10:45, Alexey Brodkin wrote:
> >
> > Hi Oleksij,
> >
> > On Wed, 2016-07-06 at 10:38 +0200, fixed-term.Oleksij.Rempel wrote:
> > >
> > >
> > > On 06.07.2016 10:32, Alexey Brodkin wrote:
> > > >
The LAN_WAKE_EN is not used to determine if the device could support
WOL. It is used to sigal a GPIO pin when a WOL event occurs. The WOL
still works even though it is disabled.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
di
Hi Oleksij,
On Wed, 2016-07-06 at 10:38 +0200, fixed-term.Oleksij.Rempel wrote:
>
> On 06.07.2016 10:32, Alexey Brodkin wrote:
> >
> > Hi Oleksij,
> >
> > On Wed, 2016-07-06 at 10:24 +0200, fixed-term.Oleksij.Rempel wrote:
> > >
> > >
> > > Hm... this Endpoint should be Interrupt, not Bulk.
[ Please avoid top-posing. ]
On Wed, Jul 06, 2016 at 03:49:15AM +, Malith Yapa wrote:
> I'm polling a couple of input bits as well as 16 bit memory registers from
> a PLC (xinje) using libmodbus.
Ah, so just normal tty use.
> Feb 23 09:59:34 localhost kernel: [16960.073287] usb 5-1: USB disc
Hi Oleksij,
On Wed, 2016-07-06 at 10:24 +0200, fixed-term.Oleksij.Rempel wrote:
>
> Hm... this Endpoint should be Interrupt, not Bulk. If you search for
> lsusb of this kind of adapter all of them list EP3 and EP4 as Interrupt.
>
> what did went wrong here? Is it not working in USB High Speed mo
On Tue, 2016-07-05 at 15:48 +0200, Micha* Pecio wrote:
> So this patch should go to 3.18+ to fix those crashes. I think I've
> posted my findings to linux-usb but apparently they were missed or
> forgotten and I forgot about this matter too.
If it doesn't go into stable, you ought to submit it the
Hi Oleksij,
On Tue, 2016-07-05 at 21:01 +0200, Oleksij Rempel wrote:
> Am 05.07.2016 um 19:31 schrieb Alexey Brodkin:
> >
> > Hi Oleksij,
> >
> > On Tue, 2016-07-05 at 19:23 +0200, Oleksij Rempel wrote:
> > >
> > > Hi,
> > >
> > > Am 05.07.2016 um 14:20 schrieb Alexey Brodkin:
> > > >
> > > >
34 matches
Mail list logo
