On Mon, Aug 05, 2013 at 09:36:23AM -0500, Dan Williams wrote:
On Mon, 2013-08-05 at 19:41 +0800, Greg Kroah-Hartman wrote:
+/* All of the above structures mushed into two lists */
+static struct usb_serial_driver * const serial_drivers[] = {
+ zio_device,
+ funsoft_device,
+
At former design, both ci_hdrc_imx and usbmisc_imx are individual
module, ci_hdrc_imx is glue layer for imx usb driver. usbmisc_imx
handles non-core registers which has different register layout
for imx SoC serials, it usually supplies interface for wakeup
setting, PHY setting, etc.
usbmisc_imx
Hi Aaro,
On 06.08.2013 19:06, Aaro Koskinen wrote:
Peripheral-only mode got broken in v3.11-rc1 because of unknown reasons.
Given that you have a board that is affected, could you investigate a
little maybe? I would have done it a long time ago, but I don't have
access to such hardware
On Wed, Aug 7, 2013 at 1:41 PM, Christoffer Dall
christoffer.d...@linaro.org wrote:
Hi all,
I've found that booting a recent kernel (and as far back as 3.9 at
least) I get a kernel bug during boot with VM debugging enabled. I
haven't had time to dig further into it, but wanted to check if
On Wed, Aug 07, 2013 at 01:34:37PM +0800, Peter Chen wrote:
At former design, both ci_hdrc_imx and usbmisc_imx are individual
module, ci_hdrc_imx is glue layer for imx usb driver. usbmisc_imx
handles non-core registers which has different register layout
for imx SoC serials, it usually
On Wed, Aug 07, 2013 at 10:15:22AM +0200, Sascha Hauer wrote:
On Wed, Aug 07, 2013 at 01:34:37PM +0800, Peter Chen wrote:
At former design, both ci_hdrc_imx and usbmisc_imx are individual
module, ci_hdrc_imx is glue layer for imx usb driver. usbmisc_imx
handles non-core registers which has
On Wed, Aug 07, 2013 at 03:00:05PM +0800, Peter Chen wrote:
On Wed, Aug 07, 2013 at 10:15:22AM +0200, Sascha Hauer wrote:
On Wed, Aug 07, 2013 at 01:34:37PM +0800, Peter Chen wrote:
At former design, both ci_hdrc_imx and usbmisc_imx are individual
module, ci_hdrc_imx is glue layer for imx
On Wed, Aug 07, 2013 at 01:34:37PM +0800, Peter Chen wrote:
-
- reg = usbmisc-base + MX25_USB_PHY_CTRL_OFFSET;
-
- if (usbdev-evdo) {
- spin_lock_irqsave(usbmisc-lock, flags);
- val = readl(reg);
- writel(val | MX25_BM_EXTERNAL_VBUS_DIVIDER, reg);
On Tue, Aug 06, 2013 at 10:35:52PM -0300, Fabio Estevam wrote:
On Tue, Aug 6, 2013 at 12:49 PM, Mark Brown broo...@kernel.org wrote:
From: Andy Green andy.gr...@linaro.org
You might have CONFIG_PM, but you might not have CONFIG_SUSPEND, in which
case these are unused.
Signed-off-by:
Just in case,
i tested ar5523 based adapter on two different xhci controllers. No
visible problems.
Am 07.08.2013 05:39, schrieb Sarah Sharp:
Please recompile your kernel with CONFIG_USB_DEBUG and
CONFIG_USB_XHCI_HCD_DEBUGGING turned on, and email dmesg from when you
first plug in the
On Wed, Aug 07, 2013 at 11:08:45AM +0200, Sascha Hauer wrote:
- Convert imx-usb-misc from a driver into something which is called
directly
- add aliases
- change devicetree bindings (which causes pain and it's not explained why
this is necessary at all)
Yes, I need to
On Wed, Aug 07, 2013 at 11:11:10AM +0200, Sascha Hauer wrote:
On Wed, Aug 07, 2013 at 01:34:37PM +0800, Peter Chen wrote:
-
- reg = usbmisc-base + MX25_USB_PHY_CTRL_OFFSET;
-
- if (usbdev-evdo) {
- spin_lock_irqsave(usbmisc-lock, flags);
- val = readl(reg);
-
On 7 August 2013 17:34, Mark Brown broo...@kernel.org wrote:
On Tue, Aug 06, 2013 at 10:35:52PM -0300, Fabio Estevam wrote:
On Tue, Aug 6, 2013 at 12:49 PM, Mark Brown broo...@kernel.org wrote:
From: Andy Green andy.gr...@linaro.org
You might have CONFIG_PM, but you might not have
On Wed, Aug 07, 2013 at 03:54:06PM +0800, Peter Chen wrote:
On Wed, Aug 07, 2013 at 11:08:45AM +0200, Sascha Hauer wrote:
- Convert imx-usb-misc from a driver into something which is called
directly
- add aliases
- change devicetree bindings (which causes pain and it's not
On Wed, Aug 07, 2013 at 01:34:37PM +0800, Peter Chen wrote:
diff --git a/Documentation/devicetree/bindings/usb/ci13xxx-imx.txt
b/Documentation/devicetree/bindings/usb/ci13xxx-imx.txt
index b4b5b79..13720a2 100644
--- a/Documentation/devicetree/bindings/usb/ci13xxx-imx.txt
+++
Hi Alan,
Thank you very much for quick response and the patch. The patch fixed the mic
on both cameras.
I have also added the following patch (see
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=36691e1be6ec551eef4a5225f126a281f8c051c2)
for avoiding the kernel
On Wed, Aug 07, 2013 at 12:05:07PM +0200, Sascha Hauer wrote:
We need to know controller number, like pdev-id in the past.
The registers at non core register is messy, the specific bit
is for specific controller.
The controller number is present in the old binding:
fsl,usbmisc =
On Wed, Aug 07, 2013 at 12:06:42PM +0200, Sascha Hauer wrote:
On Wed, Aug 07, 2013 at 01:34:37PM +0800, Peter Chen wrote:
diff --git a/Documentation/devicetree/bindings/usb/ci13xxx-imx.txt
b/Documentation/devicetree/bindings/usb/ci13xxx-imx.txt
index b4b5b79..13720a2 100644
---
From: Fabio Estevam fabio.este...@freescale.com
Using SIMPLE_DEV_PM_OPS can make the code simpler and cleaner.
Signed-off-by: Fabio Estevam fabio.este...@freescale.com
---
drivers/usb/dwc3/dwc3-pci.c | 15 +--
1 file changed, 5 insertions(+), 10 deletions(-)
diff --git
On Wed, Aug 07, 2013 at 05:24:45PM +0800, Peter Chen wrote:
On Wed, Aug 07, 2013 at 12:05:07PM +0200, Sascha Hauer wrote:
We need to know controller number, like pdev-id in the past.
The registers at non core register is messy, the specific bit
is for specific controller.
The
Hi Peter,
On Wed, Aug 07, 2013 at 05:24:45PM +0800, Peter Chen wrote:
On Wed, Aug 07, 2013 at 12:05:07PM +0200, Sascha Hauer wrote:
We need to know controller number, like pdev-id in the past.
The registers at non core register is messy, the specific bit
is for specific controller.
On Wed, Aug 07, 2013 at 02:28:20PM +0200, Michael Grzeschik wrote:
Hi Peter,
On Wed, Aug 07, 2013 at 05:24:45PM +0800, Peter Chen wrote:
On Wed, Aug 07, 2013 at 12:05:07PM +0200, Sascha Hauer wrote:
We need to know controller number, like pdev-id in the past.
The registers at
At Tue, 06 Aug 2013 14:53:24 +0300,
Jussi Kivilinna wrote:
Patch fixes 6fire not to use stack as URB transfer_buffer. URB buffers need to
be DMA-able, which stack is not. Furthermore, transfer_buffer should not be
allocated as part of larger device structure because DMA coherency issues and
**_usb_get_phy_**() APIs should generate equivalent
error codes in case of failure in getting phy. There's no
need of returning NULL pointer, like in devm_usb_get_phy()
or devm_usb_get_phy_dev(), since it's nowhere handled.
Earlier series of patches starting:
9ee1c7f usb: host: ohci-exynos: fix
URB setup packet must not be allocated as part of larger structure
because DMA coherence issues.
Patch changes catc to allocate ctrl_dr member as separate buffer.
Patch is only compile tested.
Cc: sta...@vger.kernel.org
Signed-off-by: Jussi Kivilinna jussi.kivili...@iki.fi
---
URB transfer_buffer must not be allocated as part of larger structure
because DMA coherence issues.
Patch changes catc to allocate tx_buf, rx_buf, irq_buf and ctrl_buf members
as separate buffers.
Patch is only compile tested.
Cc: sta...@vger.kernel.org
Signed-off-by: Jussi Kivilinna
URB transfer_buffers must not be allocated as part of larger structure because
DMA coherence issues.
Patch changes hso to allocate serial_state_notification member of
'struct hso_tiocmget' as separate buffer.
Patch is only compile tested.
Cc: sta...@vger.kernel.org
Signed-off-by: Jussi
URB setup packets must not be allocated as part of larger structure because
DMA coherence issues.
Patch changes hso to allocate ctrl_req_[tr]x members of 'struct hso_serial'
as separate buffers.
Patch is only compile tested.
Cc: sta...@vger.kernel.org
Signed-off-by: Jussi Kivilinna
URB transfer_buffers must not be allocated as part of larger structure
because DMA coherence issues.
Patch changes pegasus to allocate intr_buff and tx_buff members of
'struct pegasus' as separate buffers.
Patch is only compile tested.
Cc: sta...@vger.kernel.org
Signed-off-by: Jussi Kivilinna
Currently pegasus passes stack memory (which must not be used for DMA
transfers) as URB buffers with get_registers(), set_registers() and
set_register(). Apply fix inside these functions instead of changing every
call site.
Stack usage was introduced by recent commit 323b34963d11 drivers: net:
rtl8150 allocates URB transfer_buffer and setup_packet as part of same
structure 'struct async_req'. This can cause same cacheline to be DMA-mapped
twice with same URB. This can lead to memory corruption on some systems.
Patch make allocation of these buffers separate.
Use of 'struct async_req'
At Wed, 7 Aug 2013 15:59:07 +0200,
Torsten Schenk wrote:
On Wed, 07 Aug 2013 14:43:43 +0200
Takashi Iwai ti...@suse.de wrote:
At Tue, 06 Aug 2013 14:53:24 +0300,
Jussi Kivilinna wrote:
Patch fixes 6fire not to use stack as URB transfer_buffer. URB
buffers need to be DMA-able,
On Wed, 07 Aug 2013 14:43:43 +0200
Takashi Iwai ti...@suse.de wrote:
At Tue, 06 Aug 2013 14:53:24 +0300,
Jussi Kivilinna wrote:
Patch fixes 6fire not to use stack as URB transfer_buffer. URB
buffers need to be DMA-able, which stack is not. Furthermore,
transfer_buffer should not be
On 07.08.2013 16:59, Torsten Schenk wrote:
On Wed, 07 Aug 2013 14:43:43 +0200
Takashi Iwai ti...@suse.de wrote:
At Tue, 06 Aug 2013 14:53:24 +0300,
Jussi Kivilinna wrote:
Patch fixes 6fire not to use stack as URB transfer_buffer. URB
buffers need to be DMA-able, which stack is not.
Since commits 4005ad4390bf (EHCI: implement new semantics for
URB_ISO_ASAP) and c75c5ab575af (ALSA: USB: adjust for changed 3.8 USB
API) became widely distributed, people have been experiencing problems
with audio transfers. The slightest underrun causes complete failure,
requiring the audio
On Wed, 2013-08-07 at 16:29 +0300, Jussi Kivilinna wrote:
URB setup packets must not be allocated as part of larger structure because
DMA coherence issues.
Patch changes hso to allocate ctrl_req_[tr]x members of 'struct hso_serial'
as separate buffers.
Patch is only compile tested.
On Wed, 2013-08-07 at 16:29 +0300, Jussi Kivilinna wrote:
URB transfer_buffers must not be allocated as part of larger structure because
DMA coherence issues.
Patch changes hso to allocate serial_state_notification member of
'struct hso_tiocmget' as separate buffer.
Patch is only compile
Hi Felipe,
This patch brings up an interesting point: will a dwc3 PCI host use the
xhci platform driver instead of the xhci PCI driver?
If so, that seems less than ideal. Won't it not use the standard xHCI
PCI suspend and resume functions if it's registered as a platform
device? Also, it seems
On Tue, Aug 06, 2013 at 07:00:17PM +0100, Julius Werner wrote:
This patch simplifies the way the phy-samsung-usb code finds the correct
power management register to enable PHY clock gating. Previously, the
code would calculate the register address from a device tree supplied
base address and
[Cc'ed to linux-usb ML]
At Wed, 7 Aug 2013 16:51:49 +0200,
Torsten Schenk wrote:
Patch fixes URB transfer buffer allocation for midi output to be DMA-able.
Is this really needed?
That is, can't a transfer buffer be at middle of kmalloc'ed space, but
must be always the head of the kmalloc'ed
On Wed, 7 August 2013 08:50:53 +0300, Jussi Kivilinna wrote:
On 06.08.2013 19:49, Jörn Engel wrote:
On Tue, 6 August 2013 15:03:29 +0300, Jussi Kivilinna wrote:
Patch fixes alauda not to use stack as URB transfer_buffer. URB buffers
need to
be DMA-able, which stack is not.
Patch is
This breaks compatibility, both for an old kernel and a new dt and a new
kernel with an old dt. Is anyone using these bindings?
They only affect Samsung SoCs and have only been upstream for half a
year, so I doubt it's heavily used.
Why are we describing fewer registers now? Are they
On Wed, Aug 07, 2013 at 11:35:35AM +0200, Oleksij Rempel wrote:
Just in case,
i tested ar5523 based adapter on two different xhci controllers. No
visible problems.
Ah, ok, I had missed the fact that Yannik was using the device under
EHCI. I'm not sure why he emailed me instead of Alan
On Wed, 7 Aug 2013, Takashi Iwai wrote:
[Cc'ed to linux-usb ML]
At Wed, 7 Aug 2013 16:51:49 +0200,
Torsten Schenk wrote:
Patch fixes URB transfer buffer allocation for midi output to be DMA-able.
Is this really needed?
That is, can't a transfer buffer be at middle of kmalloc'ed
@@ -94,11 +94,11 @@ static int devm_usb_phy_match(struct device *dev, void
*res, void *match_data)
*/
struct usb_phy *devm_usb_get_phy(struct device *dev, enum usb_phy_type type)
{
- struct usb_phy **ptr, *phy;
+ struct usb_phy *phy = ERR_PTR(-ENOMEM), **ptr;
This looks a
On 08/07/2013 07:06 PM, Julius Werner wrote:
This breaks compatibility, both for an old kernel and a new dt and a new
kernel with an old dt. Is anyone using these bindings?
They only affect Samsung SoCs and have only been upstream for half a
year, so I doubt it's heavily used.
It probably
This patch adds USB2-LPM-Errata for USB2.0 Binary Object Store
Descriptor that support Best Effort Latency Tolerance (BELT),
with the Baseline BESL value, and Deep BESL values. Additionally, it
identifies if a Binary Object Store Descriptor is pre-errata HIRD
Link Power Management.
Signed-off-by:
*** BLURB HERE ***
Alexandra Yates (2):
lsusb: Reports if USB2.0 port is on L1 state
lsusb: Reports devices that support BESL on USB2.0
lsusb.c | 14 --
1 file changed, 12 insertions(+), 2 deletions(-)
--
1.7.9.5
--
To unsubscribe from this list: send the line unsubscribe
From: Alexandra Yates alexandra.ya...@linux.intel.com
This patch reports the low power state L1 for ports with attahced USB2
devices. The output will be part of the roothub port status as follows:
ayates@magd:~$ sudo lsusb -v -s 001:001
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0
On Wed, Aug 07, 2013 at 12:12:26PM -0700, Alexandra Yates wrote:
*** BLURB HERE ***
What is supposed to go here?
--
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
From: Mark Brown broo...@linaro.org
The intn and connect GPIO properties are swapped in the code which will
cause failures at runtime if these are connected, fix the code.
There are currently no in-tree users of this device to check or update.
Signed-off-by: Mark Brown broo...@linaro.org
---
From: Maksim Boyko maksim.a.bo...@gmail.com
Add the volume control quirk for avoiding the kernel warning for Logitech HD
Webcam C525.
The similar patch was previously reported for Logitech HD Webcam C310 (see
36691e1be6ec551eef4a5225f126a281f8c051c2).
--- linux-3.10.5-orig/sound/usb/mixer.c
On Wed, Aug 07, 2013 at 11:24:46PM +0400, Бойко Максим wrote:
From: Maksim Boyko maksim.a.bo...@gmail.com
Add the volume control quirk for avoiding the kernel warning for Logitech HD
Webcam C525.
The similar patch was previously reported for Logitech HD Webcam C310 (see
Hello.
On 08/07/2013 11:24 PM, Бойко Максим wrote:
From: Maksim Boyko maksim.a.bo...@gmail.com
Add the volume control quirk for avoiding the kernel warning for Logitech HD
Webcam C525.
The similar patch was previously reported for Logitech HD Webcam C310 (see
On Wed, Aug 07, 2013 at 03:50:42PM +0800, Ming Lei wrote:
On Wed, Aug 7, 2013 at 1:41 PM, Christoffer Dall
christoffer.d...@linaro.org wrote:
Hi all,
I've found that booting a recent kernel (and as far back as 3.9 at
least) I get a kernel bug during boot with VM debugging enabled. I
ATTENTION.
Let me use the liberty of this medium to inform you that my principal is
interested in investing his bond as a silent business partner in your company.
He would like to invest in private sector projects with an established company
in any project(s) which are already in the
From: Mark Brown broo...@linaro.org
Saves us a bit of code.
Signed-off-by: Mark Brown broo...@linaro.org
---
This depends on my previous patch usb: misc: Fix swapped properties in
usb3503 DT parsing.
drivers/usb/misc/usb3503.c | 42 +++---
1 file changed, 7
From: Mark Brown broo...@linaro.org
If someone provided meaningful error codes from reset() we should tell the
user what they were.
Signed-off-by: Mark Brown broo...@linaro.org
---
drivers/usb/core/hcd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/core/hcd.c
Sorry about that.
Here is the blurb:
The two patches enable lsusb with LPM for USB2.0 Errata. They present the user
with link status, BESL and DBESL values.
Thank you,
Alexandra.
-Original Message-
From: Greg KH [mailto:gre...@linuxfoundation.org]
Sent: Wednesday, August
The two patches enable lsusb with LPM for USB2.0 Errata.
They present the user with link status, BESL, and DBESL values.
Alexandra Yates (2):
lsusb: Reports if USB2.0 port is on L1 state
lsusb: Reports devices that support BESL on USB2.0
COPYING | 41 +++---
NEWS | 39
This patch adds USB2-LPM-Errata for USB2.0 Binary Object Store
Descriptor that support Best Effort Latency Tolerance (BELT),
with the Baseline BESL value, and Deep BESL values. Additionally, it
identifies if a Binary Object Store Descriptor is pre-errata HIRD
Link Power Management.
Signed-off-by:
From: Alexandra Yates alexandra.ya...@linux.intel.com
This patch reports the low power state L1 for ports with attahced USB2
devices. The output will be part of the roothub port status as follows:
ayates@magd:~$ sudo lsusb -v -s 001:001
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0
Hi,
I am going to test my udc driver with gadget gmidi.
And I haven't used it before so I googled how to use it,
unfortunately,there seems nothing talk about it.
Has anyone else used it or know any info that makes it work?
Thanks.
Best regards
Tong Li
--
To unsubscribe from this list: send
Hi Felipe,
This patch brings up an interesting point: will a dwc3 PCI host use the xhci
platform driver instead of the xhci PCI driver?
If so, that seems less than ideal. Won't it not use the standard xHCI PCI
suspend and resume functions if it's registered as a platform device? Also,
64 matches
Mail list logo
