Signed-off-by: Yoshihiro Shimoda yoshihiro.shimoda...@renesas.com
---
arch/arm/boot/dts/r8a7791.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/r8a7791.dtsi b/arch/arm/boot/dts/r8a7791.dtsi
index d343099..cdf4b46 100644
--- a/arch/arm/boot/dts/r8a7791.dtsi
Since the PHY of USB3.0 and EHCI/OHCI ch2 are the same, the USB3.0
driver cannot use the phy driver when the EHCI/OHCI ch2 already used it:
phy phy-e6590100.usb-phy.3: phy init failed -- -16
xhci-hcd: probe of ee00.usb failed with error -16
If so, we have to unbind the EHCI/OHCI ch2, and
This series is based on Simon's renesas.git branch and
renesas-devel-20141007-v3.17 tag. If we use the generic phy
driver for R-Car Gen2 (drivers/phy/phy-rcar-gen2.c), we can use
the USB3.0 on lager.
Yoshihiro Shimoda (2):
ARM: shmobile: r8a7790: add USB3.0 device node
ARM: shmobile: lager:
This patch is based on Simon's renesas.git branch and
renesas-devel-20141007-v3.17 tag.
Since koelsch and henninger doesn't have a USB3.0 connector,
I submit a patch for r8a7791.dtsi only.
Yoshihiro Shimoda (1):
ARM: shmobile: r8a7791: add USB3.0 device node
arch/arm/boot/dts/r8a7791.dtsi |
Signed-off-by: Yoshihiro Shimoda yoshihiro.shimoda...@renesas.com
---
arch/arm/boot/dts/r8a7790.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/r8a7790.dtsi b/arch/arm/boot/dts/r8a7790.dtsi
index 2380fd5..16f8646 100644
--- a/arch/arm/boot/dts/r8a7790.dtsi
(2014/10/08 15:24), Yoshihiro Shimoda wrote:
This patch is based on Simon's renesas.git branch and
renesas-devel-20141007-v3.17 tag.
Since koelsch and henninger doesn't have a USB3.0 connector,
I submit a patch for r8a7791.dtsi only.
Yoshihiro Shimoda (1):
ARM: shmobile: r8a7791: add
-Original Message-
From: Johan Hovold [mailto:jhov...@gmail.com] On Behalf Of Johan Hovold
Sent: Monday, October 06, 2014 7:03 PM
To: Muthu Mani
Cc: Samuel Ortiz; Lee Jones; Wolfram Sang; linux-...@vger.kernel.org; Linus
Walleij; Alexandre Courbot; linux-g...@vger.kernel.org;
-Original Message-
From: Alexandre Courbot [mailto:gnu...@gmail.com]
Sent: Tuesday, October 07, 2014 3:34 PM
To: Muthu Mani
Cc: Samuel Ortiz; Lee Jones; Wolfram Sang; Linus Walleij; Greg Kroah-
Hartman; linux-...@vger.kernel.org; linux-g...@vger.kernel.org; linux-
Hi Oussama,
On 10/07/2014 02:02 PM, Oussama Ghorbel wrote:
The USB OTG port does not work since v3.16 on omap platform.
This is a regression introduced by the commit
eb82a3d846fa (phy: omap-usb2: Balance pm_runtime_enable() on probe failure
and remove).
This because the call to
On Tue, Oct 07, 2014 at 11:07:53AM -0400, Alan Stern wrote:
That's the difference. It appears to be caused by a bug in xhci-hcd.
Does the patch below fix the problem?
Hi,
Your patch fixes it for me. So now USB port works well.
Thanks!
Index: usb-3.17/drivers/usb/host/xhci-hub.c
On Tue, 2014-10-07 at 20:01 +0530, Naveen Kumar Parna wrote:
The new patch clears the halt condition.
I mean usb_clear_halt( ) returned zero.
That probably means that the device doesn't just
produce spurious stalls. Does hcidump show anything
when the stalls happen?
Regards
On Thu, Sep 25, 2014 at 07:07:31PM +0300, Octavian Purdila wrote:
+static void dln2_rx_transfer(struct dln2_dev *dln2, struct urb *urb,
+ u16 handle, u16 rx_slot)
+{
+ struct dln2_mod_rx_slots *rxs = dln2-mod_rx_slots[handle];
+ struct dln2_rx_context *rxc;
On Tue, Oct 07, 2014 at 09:01:27PM +0300, Octavian Purdila wrote:
On Tue, Oct 7, 2014 at 8:10 PM, Johan Hovold jo...@kernel.org wrote:
On Mon, Oct 06, 2014 at 03:17:22PM +0300, Octavian Purdila wrote:
On Fri, Oct 3, 2014 at 8:12 PM, Johan Hovold jo...@kernel.org wrote:
On Thu, Sep 25,
Provide interface for setting for_device function designated in a
configuration for handling setup requests directed to device.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
---
drivers/usb/gadget/configfs.c | 50 ++-
1 file changed, 49
There are some hosts (e.g. with a popular, proprietary operating system),
which issue setup requests directed at a device even though they mean
setup requests directed at a particular interface (usb function).
This series adds optional for_device attribute in struct usb_configuration.
If the
Some not-so-well-behaving USB hosts with a popular proprietary operating
system sometimes issue per-device requests even though they mean requests
for a particular function, e.g. for ptp (picture transfer protocol).
This patch adds optional for_device function in usb_configuration so that
it can
USB gadgets composed with configfs lack suspend and resume
methods. This patch uses composite_suspend()/composite_resume()
the same way e.g. composite_setup() or composite_disconnect()
are used in a configfs-based gadget.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
---
Since Felipe
Sometimes it might be desirable to prohibit removing a symbolic link
in configfs. One example is USB gadget: when a gadget is already bound,
if USB function symlink (used to associate USB functions with USB
configurations) is removed, the gadget must be thrown away, too.
A better solution would be
Hi,
-Original Message-
From: Mike Nazarewicz [mailto:m...@google.com] On Behalf Of Michal
Nazarewicz
Sent: Tuesday, October 07, 2014 10:08 PM
To: Alan Stern; Felipe Balbi
Cc: Krzysztof Opasiak; 'Robert Baldyga';
gre...@linuxfoundation.org; linux-usb@vger.kernel.org; linux-
hcidump does not show anything when the stalls happen.
Here is the hcidump log:
[root@banunxcas29 np03]# hcidump -x -t
HCI sniffer - Bluetooth packet analyzer ver 2.1
device: hci0 snap_len: 1028 filter: 0x
Corresponding usbmon log
8801265343c0 2826295762 C Ii:1:021:1
On 10/8/2014 8:51 AM, Yoshihiro Shimoda wrote:
Enable HS-USB device for the Lager board, defining the GPIO that the driver
should check when probing. Since this board doesn't have the OTG ID pin, we
assume that GP5_18 (USB0_PWEN) is an ID pin because it is 1 when the SW5 is
in position 2-3
This NULL check sets off a static checker warning because we already
dereferenced card earlier in the function. However, since card is
never NULL so we can just remove the check.
Signed-off-by: Dan Carpenter dan.carpen...@oracle.com
diff --git a/drivers/usb/gadget/function/u_uac1.c
On Wed, 2014-10-08 at 15:51 +0530, Naveen Kumar Parna wrote:
hcidump does not show anything when the stalls happen.
There is nothing in all logs. Do you see the problem
with single devices?
Regards
Oliver
--
To unsubscribe from this list: send the line unsubscribe
On Thu, Sep 25, 2014 at 07:07:32PM +0300, Octavian Purdila wrote:
diff --git a/Documentation/ABI/testing/sysfs-bus-i2c-busses-dln2
b/Documentation/ABI/testing/sysfs-bus-i2c-busses-dln2
new file mode 100644
index 000..ad55af6
--- /dev/null
+++
On Wed, Oct 8, 2014 at 12:23 PM, Johan Hovold jo...@kernel.org wrote:
On Thu, Sep 25, 2014 at 07:07:31PM +0300, Octavian Purdila wrote:
+static void dln2_rx_transfer(struct dln2_dev *dln2, struct urb *urb,
+ u16 handle, u16 rx_slot)
+{
+ struct dln2_mod_rx_slots
Hi Roger,
Should I resend this v2 version of the patch to sta...@vger.kernel.org
which is suitable for v3.17 and which will require a very tiny adaptation?
Or I should resend the first version of this patch which is suitable for
3.16 but might seems confusing a little sine I'm resend the
On Wed, Oct 8, 2014 at 1:42 PM, Johan Hovold jo...@kernel.org wrote:
On Thu, Sep 25, 2014 at 07:07:32PM +0300, Octavian Purdila wrote:
diff --git a/Documentation/ABI/testing/sysfs-bus-i2c-busses-dln2
b/Documentation/ABI/testing/sysfs-bus-i2c-busses-dln2
new file mode 100644
index
-Original Message-
From: Mike Nazarewicz [mailto:m...@google.com]
I don't really see that happening. For the gadget to start all
descriptors need to be known. Functionfs will know the descriptors
only once the user space daemon provides them. Therefore, with the
current features
Provide interface for setting for_device function designated in a
configuration for handling setup requests directed to device.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
---
Documentation/ABI/testing/configfs-usb-gadget | 4 +++
drivers/usb/gadget/configfs.c |
There are some hosts (e.g. with a popular, proprietary operating system),
which issue setup requests directed at a device even though they mean
setup requests directed at a particular interface (usb function).
This series adds optional for_device attribute in struct usb_configuration.
If the
Some not-so-well-behaving USB hosts with a popular proprietary operating
system sometimes issue per-device requests even though they mean requests
for a particular function, e.g. for ptp (picture transfer protocol).
This patch adds optional for_device function in usb_configuration so that
it can
Oussama,
On 10/08/2014 01:54 PM, Oussama Ghorbel wrote:
Hi Roger,
Should I resend this v2 version of the patch to sta...@vger.kernel.org which
is suitable for v3.17 and which will require a very tiny adaptation?
Or I should resend the first version of this patch which is suitable for 3.16
On Tue, Oct 07 2014, David Cohen david.a.co...@linux.intel.com wrote:
The commit '2e4c7553cd usb: gadget: f_fs: add aio support' broke the
quirk implemented to align buffer size to maxpacketsize on out endpoint.
As result, functionfs does not work on Intel platforms using dwc3 driver
(i.e. Bay
On Wed, Oct 08, 2014 at 01:54:07PM +0300, Octavian Purdila wrote:
On Wed, Oct 8, 2014 at 12:23 PM, Johan Hovold jo...@kernel.org wrote:
On Thu, Sep 25, 2014 at 07:07:31PM +0300, Octavian Purdila wrote:
+static void dln2_rx_transfer(struct dln2_dev *dln2, struct urb *urb,
+
On Wed, Oct 8, 2014 at 3:04 PM, Johan Hovold jo...@kernel.org wrote:
On Wed, Oct 08, 2014 at 01:54:07PM +0300, Octavian Purdila wrote:
On Wed, Oct 8, 2014 at 12:23 PM, Johan Hovold jo...@kernel.org wrote:
On Thu, Sep 25, 2014 at 07:07:31PM +0300, Octavian Purdila wrote:
+static void
Do you see the problem with single devices?
If I connect only one device to system then I did not see this issue.
Usually I will use 8 devices(all with the same firmware) for testing.
I tried different method to get some clue. First I disconnected all
the devices and rebooted the system and
Hi,
On Wed, Oct 08, 2014 at 01:32:31PM +0200, Andrzej Pietrasiewicz wrote:
Some not-so-well-behaving USB hosts with a popular proprietary operating
system sometimes issue per-device requests even though they mean requests
for a particular function, e.g. for ptp (picture transfer protocol).
On Wed, 2014-10-08 at 18:31 +0530, Naveen Kumar Parna wrote:
Later connected third device(hci2) and after 2mins observed –EPIPE for
hci2(hci2 urb 880124f11cc0 status -32 count 0)
This points to a problem in the USB HC driver.
Can you enable debugging in that driver.
Regards
On Wed, Oct 08, 2014 at 02:42:56PM +0300, Roger Quadros wrote:
Oussama,
On 10/08/2014 01:54 PM, Oussama Ghorbel wrote:
Hi Roger,
Should I resend this v2 version of the patch to sta...@vger.kernel.org
which is suitable for v3.17 and which will require a very tiny adaptation?
Or I
Nothing to send then.
Oussama
On 10/08/2014 02:26 PM, Greg KH wrote:
On Wed, Oct 08, 2014 at 02:42:56PM +0300, Roger Quadros wrote:
Oussama,
On 10/08/2014 01:54 PM, Oussama Ghorbel wrote:
Hi Roger,
Should I resend this v2 version of the patch to sta...@vger.kernel.org which is
suitable for
On 10/07/2014 06:07 PM, Alan Stern wrote:
On Mon, 6 Oct 2014, Dmitry Nezhevenko wrote:
What does the debugging log show if you don't disable wakeup?
$It looks like same, but later it resumes once again.
[ 2836.134277] hub 2-0:1.0: state 7 ports 6 chg evt
[ 2836.134340] hub
This points to a problem in the USB HC driver.
Can you enable debugging in that driver.
Is it enabling dynamic debugging?
Could you please point me the steps to enable debugging in USB HC driver?
Thanks,
Naveen
On Wed, Oct 8, 2014 at 6:47 PM, Oliver Neukum oneu...@suse.de wrote:
On
On Wed, 8 Oct 2014, Oliver Neukum wrote:
On Wed, 2014-10-08 at 18:31 +0530, Naveen Kumar Parna wrote:
Later connected third device(hci2) and after 2mins observed –EPIPE for
hci2(hci2 urb 880124f11cc0 status -32 count 0)
This points to a problem in the USB HC driver.
Can you enable
On Tue, 7 Oct 2014, Gene Heskett wrote:
I have some update firmware on a vfat key. While that system reports the
key as being plugged in when I do the insertion, when I ask its update
facility to do an update, the sandisks led blinks a time or 2 reports it
can't find the update.
Have
On Tue, 7 Oct 2014, Michal Nazarewicz wrote:
On Tue, 7 Oct 2014, Felipe Balbi wrote:
Right, but if we allow this, I can already see folks abusing to
connect to the host early and only when necessary do some trickery to
e.g. start adbd (not saying Android will do this, just using it as an
On Wed, 8 Oct 2014, Mathias Nyman wrote:
Index: usb-3.17/drivers/usb/host/xhci-hub.c
===
--- usb-3.17.orig/drivers/usb/host/xhci-hub.c
+++ usb-3.17/drivers/usb/host/xhci-hub.c
@@ -1136,13 +1136,11 @@ int
On Wed, 8 Oct 2014, Alan Stern wrote:
What actually happened on Dmitry's system is a little strange. When he
plugged in the device there was a wakeup request, and the
port-connect-status-change bit was set. But the port-connect-status
bit was _not_ set, even after a 100 ms delay, so the
Hi,
With today's linus/master and with greg/usb-next I keep getting random
kernel oops from find_get_entry() (see below):
[ 47.700065] Unable to handle kernel paging request at virtual address
[ 47.707667] pgd = c0004000
[ 47.710506] [] *pgd=ae7f6821, *pte=,
Hi,
SCM-based USB-SCSI converters work with multi-LUN devices. I tested an MPL
MCDISK-D dual PCMCIA SCSI device in a Windows XP VM (with SCM driver
installed). Windows detected cards in both slots and added drive letters
for them.
With Linux however, only the lower slot (LUN 0) is detected. It
Hi,
On Fri, Sep 05, 2014 at 02:32:16PM -0700, Paul E. McKenney wrote:
On Thu, Sep 04, 2014 at 03:04:03PM -0500, Felipe Balbi wrote:
Hi,
On Thu, Sep 04, 2014 at 02:25:35PM -0500, Felipe Balbi wrote:
On Thu, Sep 04, 2014 at 12:16:42PM -0700, Paul E. McKenney wrote:
On Thu, Sep 04,
On Tue, Oct 07, 2014 at 07:31:44PM -0500, Felipe Balbi wrote:
Hi,
Hi Felipe,
On Tue, Oct 07, 2014 at 05:18:06PM -0700, David Cohen wrote:
The commit '2e4c7553cd usb: gadget: f_fs: add aio support' broke the
did that commit non-aio or is only aio broken ?
That commit broke the quirk on
On Tue, Oct 07, 2014 at 07:32:56PM -0500, Felipe Balbi wrote:
Hi again,
On Tue, Oct 07, 2014 at 05:18:06PM -0700, David Cohen wrote:
The commit '2e4c7553cd usb: gadget: f_fs: add aio support' broke the
quirk implemented to align buffer size to maxpacketsize on out endpoint.
As result,
Hi,
On Wed, Oct 08, 2014 at 12:13:22PM -0500, Felipe Balbi wrote:
On Fri, Sep 05, 2014 at 02:32:16PM -0700, Paul E. McKenney wrote:
On Thu, Sep 04, 2014 at 03:04:03PM -0500, Felipe Balbi wrote:
Hi,
On Thu, Sep 04, 2014 at 02:25:35PM -0500, Felipe Balbi wrote:
On Thu, Sep 04, 2014
Hello.
Here's the set of 3 patches against Simon Horman's 'renesas.git' repo,
'renesas-devel-20141007-v3.17' tag. Here we add the HS-USB device tree support
on the R8A7791/Koelsch/Henninger reference boards. The patchset requires the
USB PHY driver (already merged by Kishon and Greg) and the
From: Yoshihiro Shimoda yoshihiro.shimoda...@renesas.com
Define the R8A7791 generic part of the HS-USB device node. It is up to the board
file to enable the device.
Signed-off-by: Yoshihiro Shimoda yoshihiro.shimoda...@renesas.com
[Sergei: fixed summary, added changelog]
Signed-off-by: Sergei
From: Yoshihiro Shimoda yoshihiro.shimoda...@renesas.com
Enable HS-USB device for the Koelsch board, defining the GPIO that the driver
should check when probing (which is the ID output from MAX3355 OTG chip).
Note that there will be pinctrl-related error messages if both internal PCI
and HS-USB
From: Yoshihiro Shimoda yoshihiro.shimoda...@renesas.com
Enable HS-USB device for the Henninger board, defining the GPIO that the driver
should check when probing (which is the ID output from MAX3355 OTG chip).
Note that there will be pinctrl-related error messages if both internal PCI
and
Oops, this should have been [PATCH v 0/3]... :-/
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, Oct 08, 2014 at 10:02:44PM +0400, Sergei Shtylyov wrote:
From: Yoshihiro Shimoda yoshihiro.shimoda...@renesas.com
Enable HS-USB device for the Koelsch board, defining the GPIO that the driver
should check when probing (which is the ID output from MAX3355 OTG chip).
Note that there
On Wed, Oct 08, 2014 at 10:07:50PM +0400, Sergei Shtylyov wrote:
Hello.
On 10/08/2014 10:05 PM, Felipe Balbi wrote:
From: Yoshihiro Shimoda yoshihiro.shimoda...@renesas.com
Enable HS-USB device for the Koelsch board, defining the GPIO that the
driver
should check when probing (which
On 10/08/2014 10:08 PM, Felipe Balbi wrote:
From: Yoshihiro Shimoda yoshihiro.shimoda...@renesas.com
Enable HS-USB device for the Koelsch board, defining the GPIO that the driver
should check when probing (which is the ID output from MAX3355 OTG chip).
Note that there will be
On Wed, Oct 08, 2014 at 11:57:14AM -0500, Felipe Balbi wrote:
Hi,
With today's linus/master and with greg/usb-next I keep getting random
kernel oops from find_get_entry() (see below):
[ 47.700065] Unable to handle kernel paging request at virtual address
[ 47.707667] pgd =
Hello.
On 10/08/2014 10:05 PM, Felipe Balbi wrote:
From: Yoshihiro Shimoda yoshihiro.shimoda...@renesas.com
Enable HS-USB device for the Koelsch board, defining the GPIO that the driver
should check when probing (which is the ID output from MAX3355 OTG chip).
Note that there will be
On Wed, Oct 08, 2014 at 10:11:59PM +0400, Sergei Shtylyov wrote:
On 10/08/2014 10:08 PM, Felipe Balbi wrote:
From: Yoshihiro Shimoda yoshihiro.shimoda...@renesas.com
Enable HS-USB device for the Koelsch board, defining the GPIO that the
driver
should check when probing (which is the ID
So testing managed to configure musb in DMA mode but not load the
matching cppi41 driver for DMA. This results in
|musb-hdrc musb-hdrc.0.auto: Failed to request rx1.
|musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517
|platform musb-hdrc.0.auto: Driver musb-hdrc requests
Yet another device affected by this.
Tested-by: Kevin Fenzi ke...@scrye.com
Signed-off-by: Adel Gadllah adel.gadl...@gmail.com
---
drivers/usb/core/quirks.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/usb/core/quirks.c b/drivers/usb/core/quirks.c
index 92125f9..cbbe701 100644
Hi,
Here is yet another device that need those quirks.
See: https://bugzilla.redhat.com/show_bug.cgi?id=1149509
Adel Gadllah (2):
USB: quirks: enable device-qualifier quirk for another Elan
touchscreen
HID: usbhid: enable always-poll quirk for Elan Touchscreen 016f
This device needs the quirk as well.
Tested-by: Kevin Fenzi ke...@scrye.com
Signed-off-by: Adel Gadllah adel.gadl...@gmail.com
---
drivers/hid/hid-ids.h | 1 +
drivers/hid/usbhid/hid-quirks.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/hid/hid-ids.h
From: Hayes Wang hayesw...@realtek.com
Date: Tue, 7 Oct 2014 13:36:30 +0800
Use mutex to avoid that the serial hw settings would be interrupted
by other settings. Although there is no problem now, it makes the
driver more safe.
Signed-off-by: Hayes Wang hayesw...@realtek.com
I think a much
Hello.
Here's the set of 2 patches against Simon Horman's 'renesas.git' repo,
'renesas-devel-20141007-v3.17' tag. Here we add the HS-USB device tree support
on the R8A7790/Lager reference board. The patchset requires the USB PHY
driver (already merged by Kishon and Greg) and the generic PHY
From: Yoshihiro Shimoda yoshihiro.shimoda...@renesas.com
Define the R8A7790 generic part of the HS-USB device node. It is up to the board
file to enable the device.
Signed-off-by: Yoshihiro Shimoda yoshihiro.shimoda...@renesas.com
[Sergei: fixed summary, added changelog]
Signed-off-by: Sergei
Hi,
On Wed, Oct 08, 2014 at 10:55:58AM -0700, David Cohen wrote:
On Tue, Oct 07, 2014 at 07:32:56PM -0500, Felipe Balbi wrote:
Hi again,
On Tue, Oct 07, 2014 at 05:18:06PM -0700, David Cohen wrote:
The commit '2e4c7553cd usb: gadget: f_fs: add aio support' broke the
quirk
From: Yoshihiro Shimoda yoshihiro.shimoda...@renesas.com
Enable HS-USB device for the Lager board, defining the GPIO that the driver
should check when probing. Since this board doesn't have the OTG ID pin, we
assume that GP5_18 (USB0_PWEN) is an ID pin because it is 1 when the SW5 is
in position
On Wed, 8 Oct 2014, Mark Knibbs wrote:
Hi,
SCM-based USB-SCSI converters work with multi-LUN devices. I tested an MPL
MCDISK-D dual PCMCIA SCSI device in a Windows XP VM (with SCM driver
installed). Windows detected cards in both slots and added drive letters
for them.
With Linux
Apologies in advance if I'm posting to the wrong list. I began by
filing this as a bug on launchpad.net. Folks on that site indicated
that it should be filed at kernel.org as it is upstream but not until
after asking first on the mailling lists.
My issue touches many parts usb/graphics/etc so I
On Wed, 8 Oct 2014, Dennis Gesker wrote:
Apologies in advance if I'm posting to the wrong list. I began by
filing this as a bug on launchpad.net. Folks on that site indicated
that it should be filed at kernel.org as it is upstream but not until
after asking first on the mailling lists.
My
The commit '2e4c7553cd usb: gadget: f_fs: add aio support' broke the
quirk implemented to align buffer size to maxpacketsize on out endpoint.
As result, functionfs does not work on Intel platforms using dwc3 driver
(i.e. Bay Trail and Merrifield). This patch fixes the issue.
This code is based on
There is a typo (prove instead of probe) in the error message printed when
the platform initialization fails. Replace that word with more fitting init.
Signed-off-by: Sergei Shtylyov sergei.shtyl...@cogentembedded.com
---
drivers/usb/renesas_usbhs/common.c |2 +-
1 file changed, 1
Hi,
On Wed, Oct 08, 2014 at 12:57:07PM -0500, Felipe Balbi wrote:
[ snip ]
It seems to be a difficult-to-reproduce race though. On a second boot it
didn't die during boot, but died with my USB test case. Unfortunately,
the platform I'm using is pretty new and only goes as far back
On 10/09/2014 01:42 AM, Sergei Shtylyov wrote:
There is a typo (prove instead of probe) in the error message printed when
the platform initialization fails. Replace that word with more fitting init.
Signed-off-by: Sergei Shtylyov sergei.shtyl...@cogentembedded.com
Oops, forgot to
There might be 11 GPIOs in total.
Last three GPIOs (offsets 8-10, 0-based) are shared with FDX, LNKA, SPD
LEDs respectively. The LEDs are driven by chip by default at startup time.
Once the corresponding GPIO is requested, the chip LED drive logic is disabled.
The numbering scheme according to
On Wed, Oct 8, 2014 at 12:18 AM, Alexandre Courbot gnu...@gmail.com wrote:
On Wed, Oct 8, 2014 at 4:09 PM, Muthu Mani m...@cypress.com wrote:
-Original Message-
From: Alexandre Courbot [mailto:gnu...@gmail.com]
Sent: Tuesday, October 07, 2014 3:34 PM
To: Muthu Mani
Cc: Samuel Ortiz;
Issuing a modprobe -r g_serial command to the target
over the gadget serial communications line causes
modprobe to enter uninterruptable sleep, leaving the
system in an unstable state.
The associated tty_port.count won't drop to 0 because
the command is issued over the very line being removed.
Hi,
On Thu, Oct 09, 2014 at 11:23:59AM +1100, Andre Wolokita wrote:
Issuing a modprobe -r g_serial command to the target
over the gadget serial communications line causes
modprobe to enter uninterruptable sleep, leaving the
system in an unstable state.
does anybody know if this is a valid
Hello.
(2014/10/09 3:02), Sergei Shtylyov wrote:
From: Yoshihiro Shimoda yoshihiro.shimoda...@renesas.com
Enable HS-USB device for the Koelsch board, defining the GPIO that the driver
should check when probing (which is the ID output from MAX3355 OTG chip).
Note that there will be
On Thu, Oct 09, 2014 at 11:23:59AM +1100, Andre Wolokita wrote:
Issuing a modprobe -r g_serial command to the target
over the gadget serial communications line causes
modprobe to enter uninterruptable sleep, leaving the
system in an unstable state.
The associated tty_port.count won't drop
On 09/10/14 13:56, Greg KH wrote:
On Thu, Oct 09, 2014 at 11:23:59AM +1100, Andre Wolokita wrote:
Issuing a modprobe -r g_serial command to the target
over the gadget serial communications line causes
modprobe to enter uninterruptable sleep, leaving the
system in an unstable state.
The
On 2014-10-09 02:23, Adel Gadllah wrote:
Yet another device affected by this.
Tested-by: Kevin Fenzi ke...@scrye.com
Signed-off-by: Adel Gadllah adel.gadl...@gmail.com
---
drivers/usb/core/quirks.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/usb/core/quirks.c
On Thu, Oct 09, 2014 at 02:08:04PM +1100, Andre Wolokita wrote:
On 09/10/14 13:56, Greg KH wrote:
On Thu, Oct 09, 2014 at 11:23:59AM +1100, Andre Wolokita wrote:
Issuing a modprobe -r g_serial command to the target
over the gadget serial communications line causes
modprobe to enter
On 09/10/14 14:38, Greg KH wrote:
On Thu, Oct 09, 2014 at 02:08:04PM +1100, Andre Wolokita wrote:
On 09/10/14 13:56, Greg KH wrote:
On Thu, Oct 09, 2014 at 11:23:59AM +1100, Andre Wolokita wrote:
Issuing a modprobe -r g_serial command to the target
over the gadget serial communications line
This patch fixes an issue that suspend/resume cannot work correctly
on xhci-rcar because the xhci driver output the following log:
xhci-hcd ee00.usb: WARN: xHC CMD_RUN timeout
So, this patch adds to set the XHCI_SLOW_SUSPEND quirk if xhci-rcar.
Signed-off-by: Yoshihiro Shimoda
On 10/08/2014 11:59 PM, Sebastian Andrzej Siewior wrote:
So testing managed to configure musb in DMA mode but not load the
matching cppi41 driver for DMA. This results in
|musb-hdrc musb-hdrc.0.auto: Failed to request rx1.
|musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status
On Mon, Sep 29, 2014 at 11:28:57AM +0300, Heikki Krogerus wrote:
A question, the dwc3 controller is the PCI-E device in my platform,
but the class code of PCI header is 0x0c0330, the same with xHC.
That's because it need to meet the windows enviroment. The dwc3
controller acted as
93 matches
Mail list logo
