On Wed, May 27, 2015 at 11:39:33AM +0300, Heikki Krogerus wrote:
Hi Greg,
I can appreciate now that fixing the core problem like I2C did is
wrong, but I still feel that the driver core should provide something
like the helper for checking if the bus was registered already or not.
Otherwise
do not try to set cancel function in synchronous operations in
ffs_epfile_{read,write}_iter.
With, 70e60d917 gadget/function/f_fs.c: switch to -{read,write}_iter()
if CONFIG_AIO is disable there is no problem as kiocb_set_cancel_fn
is a nop, with this option enabled it will try to use ctx that is
From: Chunfeng Yun chunfeng@mediatek.com
Signed-off-by: Chunfeng Yun chunfeng@mediatek.com
---
drivers/usb/phy/Kconfig | 10 +
drivers/usb/phy/Makefile | 1 +
drivers/usb/phy/phy-mt65xx-usb3.c | 724 ++
3 files changed, 735
From: Chunfeng Yun chunfeng@mediatek.com
Signed-off-by: Chunfeng Yun chunfeng@mediatek.com
---
arch/arm64/boot/dts/mediatek/mt8173-evb.dts | 14 ++
arch/arm64/boot/dts/mediatek/mt8173.dtsi| 24
2 files changed, 38 insertions(+)
diff --git
From: Chunfeng Yun chunfeng@mediatek.com
find the phy driver before add primary usb_hcd to avoid acessing
xHCI register which may hangup the system when the phy is not loaded
yet and the related powers or clocks put in phy driver are not
enabled.
Signed-off-by: Chunfeng Yun
From: Chunfeng Yun chunfeng@mediatek.com
add a DT binding documentation of xHCI host controller for
the MT8173 SoC from Mediatek.
Signed-off-by: Chunfeng Yun chunfeng@mediatek.com
---
Documentation/devicetree/bindings/usb/mt8173-xhci.txt | 19 +++
1 file changed, 19
From: Macpaul Lin macp...@gmail.com
Copy usb_otg_descriptor from config's descriptor if host requests USB_DT_OTG.
Signed-off-by: Macpaul Lin macp...@gmail.com
Signed-off-by: Li Jun jun...@freescale.com
---
drivers/usb/gadget/composite.c | 18 ++
1 file changed, 18 insertions(+)
After introduce usb otg properties, update ci_otg_is_fsm_mode conditions to be
depending on both usb hardware properties and usb driver config, also resolve
a compile issue after this API change in debug.c.
Signed-off-by: Li Jun jun...@freescale.com
---
drivers/usb/chipidea/ci.h| 4 ++--
From: Macpaul Lin macp...@gmail.com
Add ADP, HNP and SRP feature options to gadget structure.
Signed-off-by: Macpaul Lin macp...@gmail.com
---
include/linux/usb/gadget.h | 9 +
1 file changed, 9 insertions(+)
diff --git a/include/linux/usb/gadget.h b/include/linux/usb/gadget.h
index
The patch supports MediaTek's xHCI controller.
There are some differences from xHCI spec:
1. The interval is specified in 250 * 8ns increments for Interrupt Moderation
Interval(IMODI) of the Interrupter Moderation(IMOD) register, it is 8 times as
much as that defined in xHCI spec.
2. For the
Hi Greg,
But couldn't we add a helper function to drivers/base/bus.c that the
bus drivers can use to at least check was the bus already loaded or
not? It looks like there are a couple of bus drivers that use the
struct bus member p to check that.
Greg, what do you think?
I think
[1.] Optiplex 9020 reboots rather than shutting down if USB3 enabled
[2.]
I have a large number of Dell Optiplex 9020 machines, and when they are
asked to shutdown with e.g. shutdown -h now, they shut down successfully
and then approximately four seconds later they start up again. This
On 26.05.2015 21:50, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
commit 2d148ea63fe50bf30071cb3e6c87fbd32c081cba
Author: Vladimir Serbinenko phco...@gmail.com
Date: Tue May 26 21:35:06 2015 +0200
Tested and works as expected in coreboot and GRUB. Booted Linux
recognizes
and it
Hi,
On 26/05/2015 at 09:51:18 -0500, Felipe Balbi wrote :
On Thu, May 14, 2015 at 04:36:33PM -0500, Bin Liu wrote:
Alexandre,
On Thu, May 14, 2015 at 4:26 PM, Alexandre Belloni
alexandre.bell...@free-electrons.com wrote:
On 14/05/2015 at 16:16:12 -0500, Bin Liu wrote :
I think I
From: Macpaul Lin macp...@gmail.com
Add USB_OTG_ADP definition for usb_otg_descriptor.bmAttributes.
Signed-off-by: Macpaul Lin macp...@gmail.com
Signed-off-by: Li Jun jun...@freescale.com
---
include/uapi/linux/usb/ch9.h | 1 +
1 file changed, 1 insertion(+)
diff --git
From: Macpaul Lin macp...@gmail.com
Update usb_otg_descriptor for ADP/SRP/HNP features if usb HW has any
configrations of them.
Signed-off-by: Macpaul Lin macp...@gmail.com
Signed-off-by: Li Jun jun...@freescale.com
---
drivers/usb/gadget/composite.c | 31 +++
1 file
From: Macpaul Lin macp...@gmail.com
Add CONFIG_USB_OTG_VERSION to identify the OTG and EH supplement release number
with which the OTG device is compliant, also update the usb_otg_descriptor for
OTG 2.0 and later release to include this OTG version number.
Signed-off-by: Macpaul Lin
Add srp, hnp and adp support for usb OTG port, then those OTG features don't
have to be decided by usb driver.
Signed-off-by: Li Jun jun...@freescale.com
---
Documentation/devicetree/bindings/usb/ci-hdrc-imx.txt | 6 ++
1 file changed, 6 insertions(+)
diff --git
Hi,
This is a follow-up of Macpaul Lin's previous patchset to resolve usb gadget
driver work with OTG 2.0, main changes:
1. keep one usb_otg_descriptor definition and introduce a kernel config to
identify the
OTG release version, if OTG 2.0 or later, add bcdOTG.
2. Override the
Check property of usb hardware to get if SRP, HNP and ADP is supported.
Signed-off-by: Li Jun jun...@freescale.com
---
drivers/usb/common/common.c | 45 +
include/linux/usb/of.h | 15 +++
2 files changed, 60 insertions(+)
diff --git
Set gadget's otg features according to controller's capability and usb property
in device tree.
Signed-off-by: Li Jun jun...@freescale.com
---
drivers/usb/chipidea/core.c | 12
drivers/usb/chipidea/udc.c | 19 ++-
include/linux/usb/chipidea.h | 3 +++
3 files
Hi alan:
2015-05-07 2:16 GMT+08:00 Alan Stern st...@rowland.harvard.edu:
On Thu, 7 May 2015, yoma sophian wrote:
Besides, the kernel already contains a thread that calls
sd_check_events periodically. Why do you need to write a new one?
I create the thread since some buggy devices needs to
On Wed, May 27, 2015 at 07:48:00PM +0800, chunfeng@mediatek.com wrote:
From: Chunfeng Yun chunfeng@mediatek.com
find the phy driver before add primary usb_hcd to avoid acessing
xHCI register which may hangup the system when the phy is not loaded
yet and the related powers or clocks
This function is used to call before 2.6.x version of linux kernel but since
then I haven't seen it's relative usage and it's not
being used any where right now after checking it through
linux.crossrefrence.So, IMHO it would be relevant to remove this obselete
function from kernel mainline.
From: Chunfeng Yun chunfeng@mediatek.com
add a DT binding documentation of usb3.0 phy for MT65xx
SoCs from Mediatek.
Signed-off-by: Chunfeng Yun chunfeng@mediatek.com
---
.../devicetree/bindings/usb/mt65xx-u3phy.txt | 37 ++
1 file changed, 37 insertions(+)
From: Chunfeng Yun chunfeng@mediatek.com
MTK xhci host controller defines some extra SW scheduling
parameters for HW to minimize the scheduling effort for
synchronous and interrupt endpoints. The parameters are
put into reseved DWs of slot context and endpoint context.
Signed-off-by:
Felipe,
On Tuesday 26 May 2015 09:08 PM, Felipe Balbi wrote:
On Sun, Mar 29, 2015 at 12:50:46PM +0200, Hans de Goede wrote:
The sunxi otg phy has a bug where it wrongly detects a high speed squelch
when reset on the root port gets de-asserted with a lo-speed device.
The workaround for this is
This function is used to call in early version of linux kernel in order
to find out the interface used by a usb device. But now it's use is
completely abolished. So,it would be relevant to remove this obselete
function from kernel mainline.
Signed-off-by: Abhishek Bist ishub...@gmail.com
---
On Wed, May 27, 2015 at 03:50:34PM -, Karl Palsson wrote:
Johan Hovold jo...@kernel.org wrote:
The usbmon traces seem to be a continual reporting of the 0x0160 shown
in the ftdi_get_modem_status lines. Is this actually _meant_ to be
happening? Can I turn it off? Any other
On Wed, 27 May 2015, Golmer Palmer wrote:
Hi Alan,
Thank you for the new patch!
However, a comment:
* At page 74 of the specifications,
section F.3 Boot Keyboard Requirements,
(http://www.usb.org/developers/hidpage/HID1_11.pdf)
is defined that:
The Boot Keyboard shall, upon reset,
Johan Hovold jo...@kernel.org wrote:
The usbmon traces seem to be a continual reporting of the 0x0160 shown
in the ftdi_get_modem_status lines. Is this actually _meant_ to be
happening? Can I turn it off? Any other suggestions?
This is the device reporting the modem and line status
On Wed, May 27, 2015 at 02:48:18PM -, Karl Palsson wrote:
Hi,
I've been using OpenWrt's usb activity led trigger to display
usb-serial traffic over a cp210x dongle quite successfully, but after
replacing the cp210x with a FT230x, I find that I get constant USB
traffic (every
On Wed, 2015-05-27 at 19:19 +0530, Abhishek Bist wrote:
This function is used to call before 2.6.x version of linux kernel but
since then I haven't seen it's relative usage and it's not
being used any where right now after checking it through
linux.crossrefrence.
This goes into detail way
Hi,
I've been using OpenWrt's usb activity led trigger to display
usb-serial traffic over a cp210x dongle quite successfully, but after
replacing the cp210x with a FT230x, I find that I get constant USB
traffic (every millisecond) as soon as the port is opened.
I've put a usbmon capture
On Wed, 27 May 2015, Heikki Krogerus wrote:
This problem is not ulpi specific. We have the same issue with every
single bus. With a bus like PCI it's just really unlikely to hit it
because PCI bus driver uses postcore_initcall. But if there was
a PCI driver that used postcore_initcall itself,
On Wed, May 27, 2015 at 07:19:15PM +0530, Abhishek Bist wrote:
This function is used to call before 2.6.x version of linux kernel but since
then I haven't seen it's relative usage and it's not
being used any where right now after checking it through
linux.crossrefrence.So, IMHO it would be
On Tue, 26 May 2015, Gary Dalmadge wrote:
Please see below. Please let me know if you need additional information.
Here's the problem, from right near the start of your trace:
8800cf87c000 2445467361 S Bo:1:004:2 -115 31 = 55534243 d200
0a35
On Wed, 27 May 2015, yoma sophian wrote:
After reading the kernel power document, freezing-of-tasks.txt , can I
get the below conclusion:
if I put my thread in freezable, it will get frozen automatically
whenever the system goes in to suspend or hibernate.
It's not entirely automatic. Your
On Wed, May 27, 2015 at 07:19:15PM +0530, Abhishek Bist wrote:
This function is used to call before 2.6.x version of linux kernel but since
then I haven't seen it's relative usage and it's not
being used any where right now after checking it through
linux.crossrefrence.So, IMHO it would be
On Wed, May 27, 2015 at 11:16:34AM -0400, Alan Stern wrote:
On Wed, 27 May 2015, Heikki Krogerus wrote:
This problem is not ulpi specific. We have the same issue with every
single bus. With a bus like PCI it's just really unlikely to hit it
because PCI bus driver uses postcore_initcall.
Hi Greg,
On Tue, May 26, 2015 at 07:41:18PM -0700, Greg KH wrote:
On Tue, May 26, 2015 at 10:54:01AM -0700, David Cohen wrote:
Hi,
On Mon, May 25, 2015 at 07:00:13PM +0200, Bjørn Mork wrote:
Greg KH gre...@linuxfoundation.org writes:
If there are other bus drivers that do this,
On Wed, May 27, 2015 at 04:28:50AM +, Kaukab, Yousaf wrote:
-Original Message-
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Wednesday, May 27, 2015 12:20 PM
To: Kaukab, Yousaf
Cc: ba...@ti.com; linux-usb@vger.kernel.org
Subject: Re: [PATCH 01/11] usb: phy: return error on
This patch fixes the following build warnings:
drivers/usb/gadget/udc/atmel_usba_udc.c:2207:12: warning:
‘usba_udc_suspend’ defined but not used [-Wunused-function] static int
usba_udc_suspend(struct device *dev)
drivers/usb/gadget/udc/atmel_usba_udc.c:2236:12: warning:
‘usba_udc_resume’ defined
Hi,
On Tue, May 26, 2015 at 07:37:02PM -0700, Greg Kroah-Hartman wrote:
On Wed, May 27, 2015 at 09:45:37AM +0800, Lu Baolu wrote:
Phy drivers and the ulpi interface providers depend on the
registration of the ulpi bus. Ulpi registers the bus in
module_init(). This could cause unnecessary
Greg KH gre...@linuxfoundation.org wrote:
If I'm not interested in modem status, can I disable this entirely? I
don't even have modem lines connected.
Is this data packet somehow causing a problem with your system? If so,
I suggest using a different type of usb to serial device, but
On Wed, May 27, 2015 at 03:50:34PM -, Karl Palsson wrote:
Johan Hovold jo...@kernel.org wrote:
The usbmon traces seem to be a continual reporting of the 0x0160 shown
in the ftdi_get_modem_status lines. Is this actually _meant_ to be
happening? Can I turn it off? Any other
This patch fixes the following build warnings:
drivers/usb/musb/ux500.c:346:12: warning: ‘ux500_suspend’ defined but
not used [-Wunused-function]
drivers/usb/musb/ux500.c:357:12: warning: ‘ux500_resume’ defined but not
used [-Wunused-function]
Signed-off-by: Felipe Balbi ba...@ti.com
---
This patch fixes the following build warnings:
drivers/usb/musb/am35x.c:573:12: warning: ‘am35x_suspend’ defined but
not used [-Wunused-function]
drivers/usb/musb/am35x.c:589:12: warning: ‘am35x_resume’ defined but not
used [-Wunused-function]
drivers/usb/musb/am35x.c:573:12: warning:
Hi Felipe,
On 05/26/2015 07:08 PM, Felipe Balbi wrote:
On Mon, May 04, 2015 at 02:55:10PM +0200, Robert Baldyga wrote:
Hi,
This patch set introduces two functions usb_gadget_deactivate() and
usb_gadget_activate(), designed to prevent udc-core from showing binded
gadget to host until it will
On Wed, May 27, 2015 at 07:50:04PM +0800, Li Jun wrote:
From: Macpaul Lin macp...@gmail.com
Update usb_otg_descriptor for ADP/SRP/HNP features if usb HW has any
configrations of them.
Signed-off-by: Macpaul Lin macp...@gmail.com
Signed-off-by: Li Jun jun...@freescale.com
---
On Wed, May 27, 2015 at 07:50:09PM +0800, Li Jun wrote:
After introduce usb otg properties, update ci_otg_is_fsm_mode conditions to be
depending on both usb hardware properties and usb driver config, also resolve
a compile issue after this API change in debug.c.
Signed-off-by: Li Jun
On Mon, May 25, 2015 at 9:53 AM, Tomeu Vizoso
tomeu.viz...@collabora.com wrote:
Hello,
I have a problem with the panel on my Tegra Chromebook taking longer than
expected to be ready during boot (Stéphane Marchesin reported what is
basically the same issue in [0]), and have looked into ordered
This patch adds function and usage of export to README and manuals.
The wording, 'server' and 'client' is changed also.
For existing attach command, the daemon runs device side machine and
attach command is executed in application side machine. Then 'server'
is used for device side and
Dear all,
This series of patches introduces WebSocket to USB/IP.
0. Version info
v4)
# Fixed regression of usbip list --remote
v3)
# Coding style for goto err labels are fixed.
# Defined magic numbers for open_hc_device() argument.
# Corrected include .../uapi/linux/usbip_ux.h as
USB/IP supports a function to import USB devices from application-side
machine by attach command.
The usage is as following.
dev:# (Physically attach your USB device.)
dev:# insmod usbip-core.ko and usbip-host.ko
dev:# usbipd -D
// Start usbip daemon.
dev:# usbip list -l
// List local USB devices
Originally, USB/IP transmits requests and response PDUs for preparation
to transfer URBs in user space, after completion of the preparation,
URBs are transmitted in kernel space.
To make easy to introduce application network protocols like WebSocket,
the driver, usbip_ux.ko, forwards URBs to
stub_shutdown_connection() : drivers/usb/usbip/stub_dev.c
stub_device_cleanup_urbs() : drivers/usb/usbip/stub_main.c
requests to kill pending URBs and clears priv lists.
stub_complete() : drivers/usb/usbip/stub_tx.c might be called with URBs
to have been requested to kill.
To avoid kernel
Originally, USB/IP transmits requests and response PDUs for preparation
to transfer URBs in user space, after the preparation, URBs are
transmitted in kernel space.
To make easy to introduce application network protocols like WebSocket
and so on, the driver, usbip_ux.ko, forwards URBs to
On Wed, May 27, 2015 at 07:50:03PM +0800, Li Jun wrote:
From: Macpaul Lin macp...@gmail.com
Add ADP, HNP and SRP feature options to gadget structure.
Signed-off-by: Macpaul Lin macp...@gmail.com
---
include/linux/usb/gadget.h | 9 +
1 file changed, 9 insertions(+)
diff --git
-next-20150527-dirty
ehci_hcd
[5.280280] usb usb1: SerialNumber: ci_hdrc.0
[5.286528] usb usb1: no of_node; not parsing pinctrl DT
[5.293375] hub 1-0:1.0: no of_node; not parsing pinctrl DT
[5.299273] hub 1-0:1.0: USB hub found
[5.303821] hub 1-0:1.0: 1 port detected
On 05/21/2015 08:13 PM, Marcel Holtmann wrote:
Hi Laura,
Then avoiding the failed firmware is no solution, indeed.
If it's a new probe, it should be never executed during resume.
Can you expand this comment? What's wrong with probing during resume?
The USB stack does carry out probes
On Wed, May 27, 2015 at 07:50:06PM +0800, Li Jun wrote:
Add srp, hnp and adp support for usb OTG port, then those OTG features don't
have to be decided by usb driver.
Please always cc to dt ML and maintainer about dt changes.
Signed-off-by: Li Jun jun...@freescale.com
---
On Thu, May 28, 2015 at 10:00:52AM +0800, Li Jun wrote:
On Thu, May 28, 2015 at 09:15:05AM +0800, Peter Chen wrote:
On Wed, May 27, 2015 at 07:50:01PM +0800, Li Jun wrote:
From: Macpaul Lin macp...@gmail.com
Add CONFIG_USB_OTG_VERSION to identify the OTG and EH supplement release
] usb usb1: Product: EHCI Host Controller
[5.272756] usb usb1: Manufacturer: Linux 4.1.0-rc5-next-20150527-dirty
ehci_hcd
[5.280280] usb usb1: SerialNumber: ci_hdrc.0
[5.286528] usb usb1: no of_node; not parsing pinctrl DT
[5.293375] hub 1-0:1.0: no of_node; not parsing pinctrl
On Wed, May 27, 2015 at 07:50:01PM +0800, Li Jun wrote:
From: Macpaul Lin macp...@gmail.com
Add CONFIG_USB_OTG_VERSION to identify the OTG and EH supplement release
number
with which the OTG device is compliant, also update the usb_otg_descriptor for
OTG 2.0 and later release to include
On Wed, May 27, 2015 at 07:50:02PM +0800, Li Jun wrote:
From: Macpaul Lin macp...@gmail.com
Add USB_OTG_ADP definition for usb_otg_descriptor.bmAttributes.
Signed-off-by: Macpaul Lin macp...@gmail.com
Signed-off-by: Li Jun jun...@freescale.com
---
include/uapi/linux/usb/ch9.h | 1 +
1
On Thu, May 28, 2015 at 09:15:05AM +0800, Peter Chen wrote:
On Wed, May 27, 2015 at 07:50:01PM +0800, Li Jun wrote:
From: Macpaul Lin macp...@gmail.com
Add CONFIG_USB_OTG_VERSION to identify the OTG and EH supplement release
number
with which the OTG device is compliant, also update
, Product=2,
SerialNumber=1
[5.267748] usb usb1: Product: EHCI Host Controller
[5.272756] usb usb1: Manufacturer: Linux 4.1.0-rc5-next-20150527-dirty
ehci_hcd
[5.280280] usb usb1: SerialNumber: ci_hdrc.0
[5.286528] usb usb1: no of_node; not parsing pinctrl DT
[5.293375] hub 1-0:1.0
On Wed, May 27, 2015 at 07:50:08PM +0800, Li Jun wrote:
Set gadget's otg features according to controller's capability and usb
property
in device tree.
Signed-off-by: Li Jun jun...@freescale.com
---
drivers/usb/chipidea/core.c | 12
drivers/usb/chipidea/udc.c | 19
-next-20150527-dirty
ehci_hcd
[5.280280] usb usb1: SerialNumber: ci_hdrc.0
[5.286528] usb usb1: no of_node; not parsing pinctrl DT
[5.293375] hub 1-0:1.0: no of_node; not parsing pinctrl DT
[5.299273] hub 1-0:1.0: USB hub found
[5.303821] hub 1-0:1.0: 1 port detected
On Thursday, May 28, 2015 12:41 PM, Chris Ruehl wrote:
More majordomo info at http://vger.kernel.org/majordomo-info.html
Seams to me the driver specific bus_resume call is broken.
ChipIdea?
(gdb) list *(hcd_bus_resume+0x58)
0x2cc0 is in hcd_bus_resume (drivers/usb/core/hcd.c:).
2217
On 05/28/2015 12:53 AM, David Cohen wrote:
Hi,
On Tue, May 26, 2015 at 07:37:02PM -0700, Greg Kroah-Hartman wrote:
On Wed, May 27, 2015 at 09:45:37AM +0800, Lu Baolu wrote:
Phy drivers and the ulpi interface providers depend on the
registration of the ulpi bus. Ulpi registers the bus in
On Wed, May 27, 2015 at 07:50:05PM +0800, Li Jun wrote:
From: Macpaul Lin macp...@gmail.com
Copy usb_otg_descriptor from config's descriptor if host requests USB_DT_OTG.
Signed-off-by: Macpaul Lin macp...@gmail.com
Signed-off-by: Li Jun jun...@freescale.com
---
: Product: EHCI Host Controller
[5.272756] usb usb1: Manufacturer: Linux 4.1.0-rc5-next-20150527-dirty
ehci_hcd
[5.280280] usb usb1: SerialNumber: ci_hdrc.0
[5.286528] usb usb1: no of_node; not parsing pinctrl DT
[5.293375] hub 1-0:1.0: no of_node; not parsing pinctrl DT
On Thu, May 28, 2015 at 09:37:47AM +0800, Peter Chen wrote:
On Wed, May 27, 2015 at 07:50:09PM +0800, Li Jun wrote:
After introduce usb otg properties, update ci_otg_is_fsm_mode conditions to
be
depending on both usb hardware properties and usb driver config, also
resolve
a compile
On Wed, May 27, 2015 at 07:50:06PM +0800, Li Jun wrote:
Add srp, hnp and adp support for usb OTG port, then those OTG features don't
have to be decided by usb driver.
Add this change to: Documentation/devicetree/bindings/usb/generic.txt
Signed-off-by: Li Jun jun...@freescale.com
---
On Wed, May 27, 2015 at 07:50:07PM +0800, Li Jun wrote:
Check property of usb hardware to get if SRP, HNP and ADP is supported.
Signed-off-by: Li Jun jun...@freescale.com
---
drivers/usb/common/common.c | 45
+
include/linux/usb/of.h | 15
[5.272756] usb usb1: Manufacturer: Linux 4.1.0-rc5-next-20150527-dirty
ehci_hcd
[5.280280] usb usb1: SerialNumber: ci_hdrc.0
[5.286528] usb usb1: no of_node; not parsing pinctrl DT
[5.293375] hub 1-0:1.0: no of_node; not parsing pinctrl DT
[5.299273] hub 1-0:1.0: USB hub found
More majordomo info at http://vger.kernel.org/majordomo-info.html
Seams to me the driver specific bus_resume call is broken.
ChipIdea?
(gdb) list *(hcd_bus_resume+0x58)
0x2cc0 is in hcd_bus_resume (drivers/usb/core/hcd.c:).
2217return -ENOENT;
2218if
On Wed, May 27, 2015 at 08:21:16AM -0700, Greg KH wrote:
On Wed, May 27, 2015 at 11:16:34AM -0400, Alan Stern wrote:
On Wed, 27 May 2015, Heikki Krogerus wrote:
Maybe we need to test for this in the driver core, not allowing drivers
for busses that are not registered, that might solve the
On Thu, May 28, 2015 at 11:09:38AM +0530, Sudip Mukherjee wrote:
On Wed, May 27, 2015 at 08:21:16AM -0700, Greg KH wrote:
On Wed, May 27, 2015 at 11:16:34AM -0400, Alan Stern wrote:
On Wed, 27 May 2015, Heikki Krogerus wrote:
Maybe we need to test for this in the driver core, not
Alan Stern stern@... writes:
On Tue, 26 May 2015, Golmer Palmer wrote:
Alan Stern stern at ... writes:
So please, can you add also some minimal support inside
Set_Protocol()
to change from mode 0 to mode 1 (and viceversa) assuming that
both
modes are equal?
Okay, a revised
82 matches
Mail list logo
