On Wed, 2015-07-29 at 02:06 +, Hayes Wang wrote:
> Oliver Neukum [mailto:oneu...@suse.com]
> > Sent: Tuesday, July 28, 2015 8:59 PM
> [...]
> > > > > static void rtl8152_tx_timeout(struct net_device *netdev) {
> > > > > struct r8152 *tp = netdev_priv(netdev);
> > > > > - int i;
The attribute authorized shows the authorization state for an interface.
Signed-off-by: Stefan Koch
---
include/linux/usb.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/usb.h b/include/linux/usb.h
index 447fe29..3deccab 100644
--- a/include/linux/usb.h
+++ b/include/linux/us
This introduces an attribute for each interface to
authorize (1) or deauthorize (0) it:
/sys/bus/usb/devices/INTERFACE/authorized
Signed-off-by: Stefan Koch
---
drivers/usb/core/sysfs.c | 43 +--
1 file changed, 41 insertions(+), 2 deletions(-)
diff --git
The kernel supports the device authorization because of wireless USB.
These is usable for wired USB devices, too.
These new interface authorization allows to enable or disable
individual interfaces instead a whole device.
If a deauthorized interface will be authorized so the driver probing must
be
This patch introduces an interface authorization for USB devices.
The kernel supports a device authorization because of wireless USB.
But the new interface authorization allows to authorize or deauthorize
individual interfaces instead authorization or deauthorize a whole device.
Therefore the aut
Interfaces are allowed per default.
This can disabled or enabled (again) by writing 0 or 1 to
/sys/bus/usb/devices/usbX/interface_authorized_default
Signed-off-by: Stefan Koch
---
drivers/usb/core/hcd.c | 47 ++
drivers/usb/core/message.c | 1 +
i
Driver probings and interface claims get rejected
if an interface is not authorized.
Signed-off-by: Stefan Koch
---
drivers/usb/core/driver.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/usb/core/driver.c b/drivers/usb/core/driver.c
index 818369a..d542d43 100644
--- a/driv
This part adds the documentation for the interface authorization.
Signed-off-by: Stefan Koch
---
Documentation/ABI/testing/sysfs-bus-usb | 22 +
Documentation/usb/authorization.txt | 34 +
2 files changed, 56 insertions(+)
diff --git a/Doc
With this patch a flag instead of a variable
is used for the default device authorization.
Signed-off-by: Stefan Koch
---
drivers/usb/core/hcd.c | 31 +--
drivers/usb/core/usb.c | 2 +-
include/linux/usb/hcd.h | 6 --
3 files changed, 26 insertions(+), 13 dele
Hi,
> With this setting and AHBBRST at SBUSCFG as "Incremental burst of
> unspecified length", each unburst size can be taken as one single transfer.
> It is benefit for unburst size transfer.
>
What is an 'unburst'?
Lothar Waßmann
--
___
On Wed, Jul 29, 2015 at 10:30:22AM +0200, Lothar Waßmann wrote:
> Hi,
>
> > With this setting and AHBBRST at SBUSCFG as "Incremental burst of
> > unspecified length", each unburst size can be taken as one single transfer.
> > It is benefit for unburst size transfer.
> >
> What is an 'unburst'?
>
Hi,
> On Wed, Jul 29, 2015 at 10:30:22AM +0200, Lothar Waßmann wrote:
> > Hi,
> >
> > > With this setting and AHBBRST at SBUSCFG as "Incremental burst of
> > > unspecified length", each unburst size can be taken as one single
> > > transfer.
> > > It is benefit for unburst size transfer.
> > >
Hello.
On 7/29/2015 11:16 AM, Stefan Koch wrote:
This patch introduces an interface authorization for USB devices.
The kernel supports a device authorization because of wireless USB.
But the new interface authorization allows to authorize or deauthorize
individual interfaces instead authoriz
Oliver Neukum [mailto:oneu...@suse.com]
> Sent: Wednesday, July 29, 2015 3:22 PM
[...]
> Now, I think I got the reason for the confusion.
>
> You are using cancel_delayed_work(&tp->schedule); after you queue a reset.
> Therefore the order in which the work and the reset will be executed is
> unde
> -Original Message-
> From: Felipe Balbi [mailto:ba...@ti.com]
> Sent: Monday, July 27, 2015 8:38 PM
> To: Badola Nikhil-B46172
> Cc: ba...@ti.com; linux-ker...@vger.kernel.org; linux-usb@vger.kernel.org;
> linux-o...@vger.kernel.org; gre...@linuxfoundation.org
> Subject: Re: [PATCH 2/3] d
Am Mittwoch, den 29.07.2015, 13:40 +0300 schrieb Sergei Shtylyov:
> Hello.
>
> On 7/29/2015 11:16 AM, Stefan Koch wrote:
>
> > This patch introduces an interface authorization for USB devices.
> > The kernel supports a device authorization because of wireless USB.
>
> > But the new interface aut
Hello.
On 7/29/2015 11:16 AM, Stefan Koch wrote:
Interfaces are allowed per default.
This can disabled or enabled (again) by writing 0 or 1 to
/sys/bus/usb/devices/usbX/interface_authorized_default
Signed-off-by: Stefan Koch
---
drivers/usb/core/hcd.c | 47
On 7/29/2015 3:12 PM, Stefan Koch wrote:
On 7/29/2015 11:16 AM, Stefan Koch wrote:
This patch introduces an interface authorization for USB devices.
The kernel supports a device authorization because of wireless USB.
But the new interface authorization allows to authorize or deauthorize
in
The device reset is necessary if the hw becomes abnormal and stops
transmitting packets.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/r8152.c
index e1b6d6d..ad8cbc6 10064
v3:
For patch #2, remove cancel_delayed_work().
v2:
For patch #1, remove usb_autopm_get_interface(), usb_autopm_put_interface(), and
the checking of intf->condition.
For patch #2, replace the original method with usb_queue_reset_device() to reset
the device.
v1:
Although the driver works normal
Add rtl8152_pre_reset() and rtl8152_post_reset() which are used when
calling usb_reset_device(). The two functions could reduce the time
of reset when calling usb_reset_device() after probe().
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 54
This part adds the documentation for the interface authorization.
Signed-off-by: Stefan Koch
---
Documentation/ABI/testing/sysfs-bus-usb | 22 +
Documentation/usb/authorization.txt | 34 +
2 files changed, 56 insertions(+)
diff --git a/Doc
The kernel supports the device authorization because of wireless USB.
These is usable for wired USB devices, too.
These new interface authorization allows to enable or disable
individual interfaces instead a whole device.
If a deauthorized interface will be authorized so the driver probing must
be
This introduces an attribute for each interface to
authorize (1) or deauthorize (0) it:
/sys/bus/usb/devices/INTERFACE/authorized
Signed-off-by: Stefan Koch
---
drivers/usb/core/sysfs.c | 39 +--
1 file changed, 37 insertions(+), 2 deletions(-)
diff --git a/d
Interfaces are allowed per default.
This can disabled or enabled (again) by writing 0 or 1 to
/sys/bus/usb/devices/usbX/interface_authorized_default
Signed-off-by: Stefan Koch
---
drivers/usb/core/hcd.c | 47 ++
drivers/usb/core/message.c | 1 +
i
This patch introduces an interface authorization for USB devices.
The kernel supports a device authorization because of wireless USB.
But the new interface authorization allows to authorize or deauthorize
individual interfaces instead authorization or deauthorize a whole device.
Therefore the aut
The attribute authorized shows the authorization state for an interface.
Signed-off-by: Stefan Koch
---
include/linux/usb.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/usb.h b/include/linux/usb.h
index 447fe29..3deccab 100644
--- a/include/linux/usb.h
+++ b/include/linux/us
With this patch a flag instead of a variable
is used for the default device authorization.
Signed-off-by: Stefan Koch
---
drivers/usb/core/hcd.c | 31 +--
drivers/usb/core/usb.c | 2 +-
include/linux/usb/hcd.h | 6 --
3 files changed, 26 insertions(+), 13 dele
Driver probings and interface claims get rejected
if an interface is not authorized.
Signed-off-by: Stefan Koch
---
drivers/usb/core/driver.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/usb/core/driver.c b/drivers/usb/core/driver.c
index 818369a..d542d43 100644
--- a/driv
On Wed, 29 Jul 2015, Stefan Koch wrote:
> This introduces an attribute for each interface to
> authorize (1) or deauthorize (0) it:
> /sys/bus/usb/devices/INTERFACE/authorized
>
> Signed-off-by: Stefan Koch
> ---
> drivers/usb/core/sysfs.c | 39 +--
> 1 file
Hi,
On Wed, Jul 29, 2015 at 11:19:01AM +, Badola Nikhil wrote:
> > > > yet another problem is that this register doesn't exist in *all*
> > > > versions of DWC3. It was introduced in version 2.50a so the branch I
> > > > typed above needs one extra check, and since it's getting so large,
> > >
On Tue, 28 Jul 2015, Laura Abbott wrote:
> Hi,
>
> While debugging an issue with another driver, I've hit some corruption in
> xHCI.
> I'm not sure if the corruption is directly caused by the first warning or if
> the warning is exposing an issue with the driver. The issue I was actually
> tryin
On Mon, Jul 27, 2015 at 03:21:59PM +0800, Peter Chen wrote:
> On Thu, Jul 23, 2015 at 11:37:24AM +0800, Li Jun wrote:
> > Change for v8:
> > - Add Peter's ACk for chipidea driver; and Roger's Reviewed-by for patch
> > 07, 21~23.
> > - Add ci->is_otg condition before enable ci->gadget.is_otg for c
On Mon, Jul 27, 2015 at 11:16:14AM +0200, Robert Baldyga wrote:
> Convert endpoint configuration to new capabilities model.
>
> Fixed typo in "epc-nulk" to "epc-bulk".
>
> Signed-off-by: Robert Baldyga
> ---
> drivers/staging/emxx_udc/emxx_udc.c | 60
> ++---
>
On Mon, Jul 27, 2015 at 11:44:08AM +0530, Vaishali Thakkar wrote:
> On Sat, Jun 6, 2015 at 7:02 AM, Vaishali Thakkar
> wrote:
> > In big endian cases, macro cpu_to_le16 unfolds to __swab16 which
> > provides special case for constants. In little endian cases,
> > __constant_cpu_to_le16 and cpu_to
On 07/28/2015 07:54 PM, Rob Herring wrote:
> On Tue, Jul 28, 2015 at 8:06 PM, Tim Bird wrote:
>> Antoine and Rob,
>>
>> I was just doing some testing with USB on a Qualcomm SoC.
>>
>> I followed the instructions in the binding document:
>> Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt
>
Am Mittwoch, den 29.07.2015, 10:12 -0400 schrieb Alan Stern:
> On Wed, 29 Jul 2015, Stefan Koch wrote:
>
> > This introduces an attribute for each interface to
> > authorize (1) or deauthorize (0) it:
> > /sys/bus/usb/devices/INTERFACE/authorized
> >
> > Signed-off-by: Stefan Koch
> > ---
> > d
On Tue, Jun 2, 2015 at 6:14 AM, Ivan T. Ivanov wrote:
> On recent Qualcomm platforms VBUS and ID lines are not routed to
> USB PHY LINK controller. Use extcon framework to receive connect
> and disconnect ID and VBUS notification.
>
> Signed-off-by: Ivan T. Ivanov
> ---
> Changes sice v2 [1].
>
>
On Wed, Jul 29, 2015 at 12:29 PM, Tim Bird wrote:
>
>
> On 07/28/2015 07:54 PM, Rob Herring wrote:
>> On Tue, Jul 28, 2015 at 8:06 PM, Tim Bird wrote:
>>> Antoine and Rob,
>>>
>>> I was just doing some testing with USB on a Qualcomm SoC.
>>>
>>> I followed the instructions in the binding document
The xpad driver has several races with respect to URB submission which
make it easy to end up with submission while active:
[ cut here ]
WARNING: CPU: 3 PID: 3563 at drivers/usb/core/urb.c:339
usb_submit_urb+0x2ad/0x5a0()
URB 8804078ac240 submitted while active
Modules
We handle the "if (!req->req.length)" condition at the start of the
function and return. We can delete this dead code.
Signed-off-by: Dan Carpenter
---
This code doesn't change the current behavior but it's also possible
that the current code is buggy. Perhaps we should delete the earlier
check
There is an "&&" vs "||" typo here so this loops 3000 times or if we get
unlucky it could loop forever.
Fixes: ceaa0a6eeadf ('usb: gadget: m66592-udc: add support for TEST_MODE')
Signed-off-by: Dan Carpenter
diff --git a/drivers/usb/gadget/udc/m66592-udc.c
b/drivers/usb/gadget/udc/m66592-udc.c
On Wed, Jul 29, 2015 at 10:04:27AM -0500, Felipe Balbi wrote:
> On Mon, Jul 27, 2015 at 03:21:59PM +0800, Peter Chen wrote:
> > On Thu, Jul 23, 2015 at 11:37:24AM +0800, Li Jun wrote:
> > > Change for v8:
> > > - Add Peter's ACk for chipidea driver; and Roger's Reviewed-by for patch
> > > 07, 21~
Hi Mathias,
>> The xhci platform driver needs to work on systems that either only
>> support 64-bit DMA or only support 32-bit DMA. Attempt to set a
>> coherent dma mask for 64-bit DMA, and attempt again with 32-bit
>> DMA if that fails.
>>
>> Signed-off-by: Mark Langsdorf
>> Tested-by: Mark Salt
On Wed, Jul 29, 2015 at 06:11:06PM -0700, Loc Ho wrote:
> Hi Mathias,
>
> >> The xhci platform driver needs to work on systems that either only
> >> support 64-bit DMA or only support 32-bit DMA. Attempt to set a
> >> coherent dma mask for 64-bit DMA, and attempt again with 32-bit
> >> DMA if that
On Thu, Jul 30, 2015 at 07:24:03AM +0800, Li Jun wrote:
> On Wed, Jul 29, 2015 at 10:04:27AM -0500, Felipe Balbi wrote:
> > On Mon, Jul 27, 2015 at 03:21:59PM +0800, Peter Chen wrote:
> > > On Thu, Jul 23, 2015 at 11:37:24AM +0800, Li Jun wrote:
> > > > Change for v8:
> > > > - Add Peter's ACk for
> > On Wed, Jul 29, 2015 at 10:30:22AM +0200, Lothar Waßmann wrote:
> > > Hi,
> > >
> > > > With this setting and AHBBRST at SBUSCFG as "Incremental burst of
> > > > unspecified length", each unburst size can be taken as one single
> > > > transfer.
> > > > It is benefit for unburst size transfe
On Wed, Jul 29, 2015 at 09:11:41PM -0500, Felipe Balbi wrote:
> On Thu, Jul 30, 2015 at 07:24:03AM +0800, Li Jun wrote:
> > On Wed, Jul 29, 2015 at 10:04:27AM -0500, Felipe Balbi wrote:
> > > On Mon, Jul 27, 2015 at 03:21:59PM +0800, Peter Chen wrote:
> > > > On Thu, Jul 23, 2015 at 11:37:24AM +080
Hi,
>> >> The xhci platform driver needs to work on systems that either only
>> >> support 64-bit DMA or only support 32-bit DMA. Attempt to set a
>> >> coherent dma mask for 64-bit DMA, and attempt again with 32-bit
>> >> DMA if that fails.
>> >>
>> >> Signed-off-by: Mark Langsdorf
>> >> Tested-
This patch introduces an interface authorization for USB devices.
The kernel supports a device authorization because of wireless USB.
But the new interface authorization allows to authorize or deauthorize
individual interfaces instead authorization or deauthorize a whole device.
Therefore the aut
This part adds the documentation for the interface authorization.
Signed-off-by: Stefan Koch
---
Documentation/ABI/testing/sysfs-bus-usb | 22 +
Documentation/usb/authorization.txt | 34 +
2 files changed, 56 insertions(+)
diff --git a/Doc
The attribute authorized shows the authorization state for an interface.
Signed-off-by: Stefan Koch
---
include/linux/usb.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/usb.h b/include/linux/usb.h
index 447fe29..3deccab 100644
--- a/include/linux/usb.h
+++ b/include/linux/us
With this patch a flag instead of a variable
is used for the default device authorization.
Signed-off-by: Stefan Koch
---
drivers/usb/core/hcd.c | 31 +--
drivers/usb/core/usb.c | 2 +-
include/linux/usb/hcd.h | 6 --
3 files changed, 26 insertions(+), 13 dele
This introduces an attribute for each interface to
authorize (1) or deauthorize (0) it:
/sys/bus/usb/devices/INTERFACE/authorized
Signed-off-by: Stefan Koch
---
drivers/usb/core/sysfs.c | 36
1 file changed, 36 insertions(+)
diff --git a/drivers/usb/core/sys
Interfaces are allowed per default.
This can disabled or enabled (again) by writing 0 or 1 to
/sys/bus/usb/devices/usbX/interface_authorized_default
Signed-off-by: Stefan Koch
---
drivers/usb/core/hcd.c | 47 ++
drivers/usb/core/message.c | 1 +
i
Driver probings and interface claims get rejected
if an interface is not authorized.
Signed-off-by: Stefan Koch
---
drivers/usb/core/driver.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/usb/core/driver.c b/drivers/usb/core/driver.c
index 818369a..d542d43 100644
--- a/driv
The kernel supports the device authorization because of wireless USB.
These is usable for wired USB devices, too.
These new interface authorization allows to enable or disable
individual interfaces instead a whole device.
If a deauthorized interface will be authorized so the driver probing must
be
According to USB Audio Device 2.0 Spec, Ch4.10.1.1:
wMaxPacketSize is defined as follows:
Maximum packet size this endpoint is capable of sending or receiving
when this configuration is selected.
This is determined by the audio bandwidth constraints of the endpoint.
In current code, the wMaxPacket
Hi Laura,
On Wed, Jul 29, 2015 at 02:27:23PM -0700, Laura Abbott wrote:
@@ -791,6 +796,9 @@ static int xpad_play_effect(struct input_dev *dev, void
*data, struct ff_effect
> {
> struct usb_xpad *xpad = input_get_drvdata(dev);
>
> + if (test_and_set_bit(OUT_IRQ_SUBMITTED, &xpad->odata
On Wed, 2015-07-29 at 12:10 -0700, Tim Bird wrote:
> On Tue, Jun 2, 2015 at 6:14 AM, Ivan T. Ivanov iva...@linaro.org> wrote:
> > On recent Qualcomm platforms VBUS and ID lines are not routed to
> > USB PHY LINK controller. Use extcon framework to receive connect
> > and disconnect ID and VBUS not
60 matches
Mail list logo
