If the glue layer is removed first (core layer later),
it deletes the phy device first, then the core device.
But at core's removal, it still uses PHY's resources, it may
cause kernel's oops. It is much like the problem
Paul Zimmerman reported at:
http://marc.info/?l=linux-usbm=136547502011472w=2.
If the glue layer is removed first (core layer later),
it deletes the phy device first, then the core device.
But at core's removal, it still uses PHY's resources, it may
cause kernel's oops. It is much like the problem
Paul Zimmerman reported at:
http://marc.info/?l=linux-usbm=136547502011472w=2.
If the glue layer is removed first (core layer later),
it deletes the phy device first, then the core device.
But at core's removal, it still uses PHY's resources, it may
cause kernel's oops. It is much like the problem
Paul Zimmerman reported at:
http://marc.info/?l=linux-usbm=136547502011472w=2.
If the glue layer is removed first (core layer later),
it deletes the phy device first, then the core device.
But at core's removal, it still uses PHY's resources, it may
cause kernel's oops. It is much like the problem
Paul Zimmerman reported at:
http://marc.info/?l=linux-usbm=136547502011472w=2.
On Thu, May 23, 2013 at 08:31:18AM -0700, Greg Kroah-Hartman wrote:
On Thu, May 23, 2013 at 03:07:09PM +0200, Philippe De Muyter wrote:
Hi all,
I have a lot of linux computers equipped with a GlobalSat Br-353 GPS
receiver,
which is connected via USB (an integrated PL2303). The GPS
In order to convert to configfs the usb functions need to be converted
to a new interface and compiled as modules. This patch creates an rndis
module which will be used by the new functions. After all users of
f_rndis are converted to the new interface, this module can be
merged with f_rndis
Increase the current arbitrary limit for isocronous packet size to a
value large enough to account for USB 3.0 super bandwidth streams,
bMaxBurst (0~15 allowed, 1~16 packets)
bmAttributes (bit 1:0, mult 0~2, 1~3 packets)
so the size max for one USB 3 isocronous transfer is
1024 byte * 16 * 3 =
The Option GTM681W uses a qualcomm chip and can be
served by the qcserial device driver.
Signed-off-by: Richard Weinberger rich...@nod.at
---
drivers/usb/serial/qcserial.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/serial/qcserial.c b/drivers/usb/serial/qcserial.c
index
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/u_ether.c | 11 +++
drivers/usb/gadget/u_ether.h | 10 ++
2 files changed, 21 insertions(+), 0 deletions(-)
diff --git
Here I present the conversion of everything that is required to provide
the equivalent of g_ether.ko with configfs.
A branch will be available here (from 24th May 2013, afternoon UTC):
git://git.infradead.org/users/kmpark/linux-samsung usb-gadget-configfs
This series requires the following
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
Documentation/ABI/testing/configfs-usb-gadget-eem | 14 ++
drivers/usb/gadget/Kconfig| 15 ++
drivers/usb/gadget/f_eem.c
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/f_eem.c | 17 ++---
1 files changed, 6 insertions(+), 11 deletions(-)
diff --git a/drivers/usb/gadget/f_eem.c b/drivers/usb/gadget/f_eem.c
index
Converting rndis to the new function interface requires converting
the USB rndis' function code and its users.
This patch converts the f_rndis.c to the new function interface.
The file is now compiled into a separate usb_f_rndis.ko module.
The old function interface is provided by means of a
There are no old function interface users left, so the old interface
can be removed.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/f_eem.c | 59 --
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
.../ABI/testing/configfs-usb-gadget-rndis | 14 ++
drivers/usb/gadget/Kconfig | 16 ++
drivers/usb/gadget/f_rndis.c
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/f_rndis.c | 22 --
1 files changed, 8 insertions(+), 14 deletions(-)
diff --git a/drivers/usb/gadget/f_rndis.c
This is required in preparation for using usb_gstrings_attach.
The rndis initialization so far has been performed on the first
occurence of rndis_bind(), but the condition to check it (first
or not first) was borrowed from strings handling.
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/ether.c | 54 +--
2 files changed, 32 insertions(+), 23 deletions(-)
diff --git
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
.../ABI/testing/configfs-usb-gadget-subset | 14 ++
drivers/usb/gadget/Kconfig | 10
drivers/usb/gadget/f_subset.c
Converting ecm subset to the new function interface requires converting
the USB subset's function code and its users.
This patch converts the f_subset.c to the new function interface.
The file is now compiled into a separate usb_f_subset.ko module.
The old function interface is provided by means
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/multi.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/drivers/usb/gadget/multi.c b/drivers/usb/gadget/multi.c
index f9e07c0..66f756f
Converting eem to the new function interface requires converting
the USB eem's function code and its users.
This patch converts the f_eem.c to the new function interface.
The file is now compiled into a separate usb_f_eem.ko module.
The old function interface is provided by means of a preprocessor
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/ether.c | 104
2 files changed, 58 insertions(+), 47 deletions(-)
diff --git
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/Kconfig |1 +
drivers/usb/gadget/ether.c | 73
2 files changed, 61 insertions(+), 13 deletions(-)
diff --git
Is noone interested in taking this up with me?
Martin
On Mon, May 13, 2013 at 1:20 PM, Martin van Es mrva...@gmail.com wrote:
Hi,
I have exactly the same problem as described by Harald Judt in this mail:
http://www.spinics.net/lists/linux-usb/msg58841.html
The thread ends here, in mid
On Fri, May 24, 2013 at 09:27:17AM +0200, Philippe De Muyter wrote:
On Thu, May 23, 2013 at 08:31:18AM -0700, Greg Kroah-Hartman wrote:
On Thu, May 23, 2013 at 03:07:09PM +0200, Philippe De Muyter wrote:
Hi all,
I have a lot of linux computers equipped with a GlobalSat Br-353 GPS
Richard Weinberger rich...@nod.at writes:
The Option GTM681W uses a qualcomm chip and can be
served by the qcserial device driver.
Should it also be added to the qmi_wwan driver?
Bjørn
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message to
On Fri, 24 May 2013, Philippe De Muyter wrote:
On Thu, May 23, 2013 at 08:31:18AM -0700, Greg Kroah-Hartman wrote:
On Thu, May 23, 2013 at 03:07:09PM +0200, Philippe De Muyter wrote:
Hi all,
I have a lot of linux computers equipped with a GlobalSat Br-353 GPS
receiver,
which
On Fri, 24 May 2013, Federico Manzan wrote:
Increase the current arbitrary limit for isocronous packet size to a
value large enough to account for USB 3.0 super bandwidth streams,
bMaxBurst (0~15 allowed, 1~16 packets)
bmAttributes (bit 1:0, mult 0~2, 1~3 packets)
so the size max for one USB
On Fri, 24 May 2013, Jingoo Han wrote:
From: Thomas Abraham thomas...@samsung.com
Exynos5440 does not require any explict USB phy configuration. So skip
the USB phy configuration for Exynos5440 based platforms.
Signed-off-by: Thomas Abraham thomas...@samsung.com
Signed-off-by: Jingoo Han
From: Graeme Gregory g...@slimlogic.co.uk
This is the driver for the USB comparator built into the palmas chip. It
handles the various USB OTG events that can be generated by cable
insertion/removal.
Signed-off-by: Graeme Gregory g...@slimlogic.co.uk
Signed-off-by: Moiz Sonasath
From: Graeme Gregory g...@slimlogic.co.uk
Added an API to set/clear the switch bit on SMPS10 which can be used by
palmas usb. The switch bit should be set in order for palmas to
supply VBUS and is needed when OMAP is acting as USB HOST.
Signed-off-by: Graeme Gregory g...@slimlogic.co.uk
Modified dwc3-omap to receive connect and disconnect notification using
extcon framework. Also did the necessary cleanups required after
adapting to extcon framework.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/dwc3/dwc3-omap.c | 80
Hello.
On 24-05-2013 9:34, B, Ravi wrote:
removed unused nop xceiv (un_)register API's from all musb platform
drivers
Since when are they unused?
Please refer to commit id 662dca54 : usb: otg: support for multiple
transceivers by a single controller.
Usb_get_phy() is used to get
Conversion to new interface is required to move to configfs.
This patch edition fixes compilation error if RNDIS is not selected in Kconfig.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/Kconfig |1 +
Hello.
On 24-05-2013 12:47, Federico Manzan wrote:
Increase the current arbitrary limit for isocronous packet size to a
value large enough to account for USB 3.0 super bandwidth streams,
bMaxBurst (0~15 allowed, 1~16 packets)
bmAttributes (bit 1:0, mult 0~2, 1~3 packets)
so the size max for
Hi list,
I'm experiencing problems while booting on a Freescale P1013 based board. It
hangs on USB initialization:
[3.763584] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[3.770519] ehci-pci: EHCI PCI platform driver
[3.775116] ohci_hcd: USB 1.1 'Open' Host Controller
Hello.
On 24-05-2013 16:17, Andrzej Pietrasiewicz wrote:
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/u_ether.c | 11 +++
drivers/usb/gadget/u_ether.h | 10 ++
2 files changed,
Hello.
On 24-05-2013 18:31, Kishon Vijay Abraham I wrote:
From: Graeme Gregory g...@slimlogic.co.uk
Added an API to set/clear the switch bit on SMPS10 which can be used by
palmas usb. The switch bit should be set in order for palmas to
supply VBUS and is needed when OMAP is acting as USB
Am 24.05.2013 15:18, schrieb Bjørn Mork:
Richard Weinberger rich...@nod.at writes:
The Option GTM681W uses a qualcomm chip and can be
served by the qcserial device driver.
Should it also be added to the qmi_wwan driver?
Don't know. But I can happily test it. :)
Can you please explain me
At this point the port switchover quirk is getting unwieldy. I know of
at least two more platforms that will need the switchover quirk, and
it's silly to keep adding them to the list.
Heikki, can you change the code to always try to switchover the ports
from EHCI to xHCI if an Intel xHCI host is
On Tue, May 21, 2013 at 04:26:43PM +0400, Sergei Shtylyov wrote:
Hello.
On 21-05-2013 10:08, Heikki Krogerus wrote:
From: Chew, Chiau Ee chiau.ee.c...@intel.com
Like the xHCI controller on Intel Panther Point and Lynx Point
chipsets, the xHCI controller on Intel BayTrail has also ports
On Fri, 24 May 2013 14:42:46 +
Thumshirn, Johannes Tobias johannes.thumsh...@men.de wrote:
Hi list,
I'm experiencing problems while booting on a Freescale P1013 based board. It
hangs on USB initialization:
[3.763584] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[
Do we have support for the new extensions for USB communication devices
that use the Mobile Broadband Interface Model (MBIM) spec?
http://www.usb.org/developers/devclass_docs/MBIM10Errata1.zip
The spec was released pretty recently, which is why I'm asking on the
mailing lists, rather than
The context entries field of the slot context must be set to one more
than the highest endpoint index currently active. The previous logic
only included the set of endpoints currently being added, meaning that
if an endpoint where dropped then the field would be reset to 1,
deactivating all
Martin:
The patch below should implement the new behavior of the URB_ISO_ASAP
flag (as described in the kerneldoc for usb_submit_urb) for the
imx21-hcd driver. I can't test it -- I haven't even tried to
cross-compile it.
Does it look okay to you?
Alan Stern
Index:
Hello.
On 05/24/2013 08:56 PM, Sarah Sharp wrote:
From: Chew, Chiau Ee chiau.ee.c...@intel.com
Like the xHCI controller on Intel Panther Point and Lynx Point
chipsets, the xHCI controller on Intel BayTrail has also ports that
can be switched between the EHCI host controller.
s/between/to/
Ccing Dan Williams, since Johannes Berg mentioned on IRC that Dan might
know the status of MBIM support.
On Fri, May 24, 2013 at 10:09:15AM -0700, Sarah Sharp wrote:
Do we have support for the new extensions for USB communication devices
that use the Mobile Broadband Interface Model (MBIM)
Richard Weinberger rich...@nod.at writes:
Am 24.05.2013 15:18, schrieb Bjørn Mork:
Richard Weinberger rich...@nod.at writes:
The Option GTM681W uses a qualcomm chip and can be
served by the qcserial device driver.
Should it also be added to the qmi_wwan driver?
Don't know. But I can
[resending due to an unreliable smtp smarthost - apologies if you
receive any duplicates]
Sarah Sharp sarah.a.sh...@linux.intel.com writes:
Do we have support for the new extensions for USB communication devices
that use the Mobile Broadband Interface Model (MBIM) spec?
We do. See
Sarah Sharp sarah.a.sh...@linux.intel.com writes:
Do we have support for the new extensions for USB communication devices
that use the Mobile Broadband Interface Model (MBIM) spec?
We do. See drivers/net/usb/cdc_mbim.c. It's a usbnet minidriver based on
reusing parts of cdc_ncm. It should be
Bjørn Mork bj...@mork.no writes:
http://www.usb.org/developers/devclass_docs/MBIM10Errata1.zip
Thanks for that pointer. I haven't seen the errata before. Will study
it, but fortunately we are protected against anything involving
management protocol updates.
Yuck. When did the USB-IF start
From: Fabio Estevam fabio.este...@freescale.com
Fix the following sparse warnings:
drivers/usb/chipidea/usbmisc_imx.c:246:5: warning: symbol
'usbmisc_imx_drv_init' was not declared. Should it be static?
drivers/usb/chipidea/usbmisc_imx.c:252:6: warning: symbol
'usbmisc_imx_drv_exit' was not
(apologies if this is duplicate; I've tried posting several times over the
past few days, but it seems to be getting silently dropped)
This problem occurs in 3.9.0 and 3.9.3, but not in 3.6.11. Stock
kernel, not tainted, most things (including USB drivers) compiled as
modules.
modprobing
From: Paul Zimmerman
Sent: Monday, May 13, 2013 11:58 AM
From: Matthijs Kooijman [mailto:matth...@stdin.nl]
Sent: Wednesday, May 08, 2013 2:02 PM
I'm running into an issue with the dwc2 driver. When I power on my board
with an usb device (mass storage in this case) connected, the
On Fri, May 24, 2013 at 11:12:57AM -0700, Shawn Nematbakhsh wrote:
If a USB controller with XHCI_RESET_ON_RESUME goes to runtime suspend,
a reset will be performed upon runtime resume. Any previously suspended
devices attached to the controller will be re-enumerated at this time.
This will
On Fri, May 24, 2013 at 10:05:01PM +0400, Sergei Shtylyov wrote:
Hello.
On 05/24/2013 08:56 PM, Sarah Sharp wrote:
From: Chew, Chiau Ee chiau.ee.c...@intel.com
Like the xHCI controller on Intel Panther Point and Lynx Point
chipsets, the xHCI controller on Intel BayTrail has also ports
On Fri, 2013-05-24 at 20:25 +0200, Bjørn Mork wrote:
Richard Weinberger rich...@nod.at writes:
Am 24.05.2013 15:18, schrieb Bjørn Mork:
Richard Weinberger rich...@nod.at writes:
The Option GTM681W uses a qualcomm chip and can be
served by the qcserial device driver.
Should it also
Hello.
On 05/25/2013 01:54 AM, Sarah Sharp wrote:
From: Chew, Chiau Ee chiau.ee.c...@intel.com
Like the xHCI controller on Intel Panther Point and Lynx Point
chipsets, the xHCI controller on Intel BayTrail has also ports that
can be switched between the EHCI host controller.
s/between/to/
The following changes since commit 2a0ebf80aa95cc758d4725f74a7016e992606a39:
USB: cxacru: potential underflow in cxacru_cm_get_array() (2013-05-20
11:35:47 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/sarah/xhci.git
for-usb-linus-2013-05-24
From: Vladimir Murzin murzi...@gmail.com
If for whatever reason we fall into fail path in xhci_mem_init()
before bw table gets initialized we may access the uninitialized lists
in xhci_mem_cleanup().
Check for bw table before traversing lists in cleanup routine.
This patch should be backported
Some xHCI hosts contain a redriver from TI that silently drops port
status connect changes if the port slips into Compliance Mode. If the
port slips into compliance mode while the host is in D0, there will not
be a port status change event. If the port slips into compliance mode
while the host
From: Tony Camuso tcam...@redhat.com
Commit 71c731a2 (usb: host: xhci: Fix Compliance Mode on SN65LVPE502CP
Hardware) was a workaround for systems using the SN65LVPE502CP,
controller, but it introduced a bug in resume from hibernate.
The fix created a timer, comp_mode_recovery_timer, which is
From: Sergio Aguirre sergio.a.aguirre.rodrig...@intel.com
It is possible that we fail on xhci_mem_init, just before doing
the INIT_LIST_HEAD, and calling xhci_mem_cleanup.
Problem is that, the list_for_each_entry_safe macro, assumes
list heads are initialized (not NULL), and dereferences their
Passing the value DMA_BIT_MASK(31) to dma_set_mask() causes the
dwc2-pci driver to sometimes fail (cannot enumerate the connected
device). Change it to DMA_BIT_MASK(32) instead, which is a more
sensible value anyway.
Signed-off-by: Paul Zimmerman pa...@synopsys.com
---
This should be sent to
Change some dev_dbg() messages in dwc2_hcd_hub_control() to
dev_vdbg(), to prevent massive spew to the dmesg log when a device
is disconnected.
Signed-off-by: Paul Zimmerman pa...@synopsys.com
---
drivers/staging/dwc2/hcd.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff
On Fri, 2013-05-24 at 11:10 -0700, Sarah Sharp wrote:
Ccing Dan Williams, since Johannes Berg mentioned on IRC that Dan might
know the status of MBIM support.
As Bjorn mentioned, libmbim just got a 1.0 release, and ModemManager
0.7.x (git master, basically) has support for MBIM devices via
This patchset address some (but not all) of the security issues found
with the Klockwork static analysis tool. I have not reviewed these in
detail to see if these could be used by attackers, so someone with more
security experience may want to look these over.
Sarah Sharp
The following changes
It's horrible coding style to panic the kernel when someone passes you
an argument value you didn't expect.
This patch should be backported to kernels as old as 2.6.31, that
contain the commit d115b04818e57bdbc7ccde4d0660b15e33013dc8 USB: xhci:
Support for 64-byte contexts.
Signed-off-by: Sarah
From: Mathias Nyman mathias.ny...@linux.intel.com
If the endpoint type is unknown, set it to 0 and fail gracefully
instead of causing a kernel panic.
This patch should be backported to kernels as old as 2.6.31, that
contain the commit f94e0186312b0fc39f41eed4e21836ed74b7efe1 USB: xhci:
Bandwidth
From: Mathias Nyman mathias.ny...@linux.intel.com
usb_hub_to_struct_hub() can return NULL in the unlikely cases a hub
without active configuration, or a hub without ports is found.
Even if unlikely we need to handle those cases properly.
[Note from Sarah: I'm not sure which stable kernels need
From: Mathias Nyman mathias.ny...@linux.intel.com
Fail and free the container context in case dma_pool_alloc() can't allocate
the raw context data part of it
This patch should be backported to kernels as old as 2.6.31, that
contain the commit d115b04818e57bdbc7ccde4d0660b15e33013dc8 USB: xhci:
From: Mathias Nyman mathias.ny...@linux.intel.com
We may have more speed types in the future, so fail gracefully, rather
than causing the kernel to panic.
BUG() was called if the device speed was unknown when setting max packet
size. Set the max packet size at the same time as the slot speed
Fail gracefully, instead of causing the kernel to panic, if the input
control context doesn't have the right type (XHCI_CTX_TYPE_INPUT). Push
finding the pointer to the input control context up into functions that
can fail.
This patch should be backported to kernels as old as 2.6.31, that
The current XHCI code treats a command completion event with the
COMP_CMD_STOP code as a slightly different version of COMP_CMD_ABORT. In
particular, it puts the pointed-to command TRB through the normal
command completion handlers. This is not how this event works.
As XHCI spec 4.6.1.1
The XHCI stack usually uses wait_for_completion_interruptible_timeout()
to wait for the completion of an XHCI command, and treats both timeouts
and interruptions as errors. This is a bad idea, since these commands
are often essential for the correct operation of the USB stack, and
their failure
On OMAP4 platforms, EHCI HCD needs the physical layer signalling
activated, along with the NOP USB Transceiver driver. Otherwise, the
kernel boots without registering any USB device.
This patch applies to Linux 3.10-rc2.
Signed-off-by: Adrien Vergé adrienve...@gmail.com
---
diff --git
77 matches
Mail list logo
