Hi Oliver!
>
> FYI: My laptop never crashed during these tests :-)
>
Good news:
Gerd also tested "plug off" and his system never crashed.
Seems to be a bug specific to my system.
regards,
Bernd
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to m
Add device driver for USB2CAN interface from "8 devices"
(http://www.8devices.com).
changes since v10:
* small cleanups
changes since v9:
* fixed syslog messages
* fixed crc error number
* increased MAX_RX_URBS and MAX_TX_URBS
changes since v8:
* remove all sysfs files
changes since v7:
* add
Yes. It's compiled directly into the kernel.
On Fri, Jan 18, 2013 at 8:35 PM, Greg KH wrote:
> On Fri, Jan 18, 2013 at 08:23:52PM +, Robert Dvoracek wrote:
>> When I plug something in to a USB3 port, nothing appears in the system
>> messages. The kernel is just not seeing the USB controller
tree: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-next
head: 6e30d7cba992d626c9d16b3873a7b90c700d0e95
commit: 6e30d7cba992d626c9d16b3873a7b90c700d0e95 [26/26] usb: Add
driver/usb/core/(port.c,hub.h) files
config: make ARCH=arm at91_dt_defconfig
All error/warnings:
dri
On Fri, Jan 18, 2013 at 11:28:43PM +0100, Arkadiusz Miskiewicz wrote:
> Hi.
>
> Using 3.7.3 kernel and connecting two rs232 usb adapters, CP2102 and FT232RL,
> one after disconnecting another.
>
> After few cycles of reconnecting and using socat (below) I'm getting problems
> accessing ttyUSB0:
Hi,
On Sat, Jan 19, 2013 at 9:11 AM, Gregory CLEMENT
wrote:
> On 01/19/2013 01:07 AM, Nobuhiro Iwamatsu wrote:
>> Hi,
>>
>> Thomas, Thank you for the detailed explanation.
>>
>> Ezequiel, I checked your patch on OpenBlocks AX3, work fine.
>>
>> But I have a question. your patch "arm: mvebu: Add s
On 01/19/2013 01:07 AM, Nobuhiro Iwamatsu wrote:
> Hi,
>
> Thomas, Thank you for the detailed explanation.
>
> Ezequiel, I checked your patch on OpenBlocks AX3, work fine.
>
> But I have a question. your patch "arm: mvebu: Add support for USB
> host controllers in Armada 370/XP"
> was set USB co
Hi,
Thomas, Thank you for the detailed explanation.
Ezequiel, I checked your patch on OpenBlocks AX3, work fine.
But I have a question. your patch "arm: mvebu: Add support for USB
host controllers in Armada 370/XP"
was set USB controller of 0xd005 to IRQ 45. I think this is 47,
and 0xd005200
On Fri, Jan 11, 2013 at 08:10:39PM +0800, Lan Tianyu wrote:
> ACPI provide "_PLD" and "_UPC" aml methods to describe usb port
> visibility and connectability. This patch is to add
> usb_hub_adjust_DeviceRemovable()
> to adjust usb hub port's DeviceRemovable according ACPI information and
> invoke
On Fri, Jan 11, 2013 at 08:10:37PM +0800, Lan Tianyu wrote:
> The dev_pm_qos_flags() will be used in the usb core which could be
> compiled as a module. This patch is to export it.
>
> Signed-off-by: Lan Tianyu
> ---
> drivers/base/power/qos.c |1 +
> 1 file changed, 1 insertion(+)
>
> diff
On Mon, Jan 14, 2013 at 10:55:48AM +0800, fangxiaozhi 00110321 wrote:
>
> From: fangxiaozhi
>
> 1. Optimize the matching rules with new macro for Huawei USB storage
>devices, to avoid to load USB storage driver for the modem interface
>with Huawei devices.
> 2. Add to support new switch
On Mon, Jan 14, 2013 at 10:55:48AM +0800, fangxiaozhi 00110321 wrote:
>
> From: fangxiaozhi
>
> 1. Optimize the matching rules with new macro for Huawei USB storage
>devices, to avoid to load USB storage driver for the modem interface
>with Huawei devices.
> 2. Add to support new switch
On Sat, Jan 19, 2013 at 12:10:07AM +0800, Lan Tianyu wrote:
> Usb3.0 device defines function remote wakeup which is only for interface
> recipient rather than device recipient. This is different with usb2.0 device's
> remote wakeup feature which is defined for device recipient. According usb3.0
> s
On Sat, Jan 12, 2013 at 11:18:03PM +0800, Chen Gang wrote:
>
> for function uhci_sprint_schedule:
> the buffer len is MAX_OUTPUT: 64 * 1024, which may not be enough:
> may loop UHCI_NUMFRAMES times (UHCI_NUMFRAMES is 1024)
> each time of loop may get more than 64 bytes
> so n
On 19-01-2013 2:16, Sergei Shtylyov wrote:
Serialize usb-storage operations with usbfs and 'cat /proc/bus/usb/devices',
so that they cannot disturb storage by seemingly harmless control reads.
This patch was adapted from 2.4 patches by Pete Zaitcev. The initial
patch of
the series dates back
Hello.
On 19-01-2013 2:12, Sergei Shtylyov wrote:
Serialize usb-storage operations with usbfs and 'cat /proc/bus/usb/devices',
so that they cannot disturb storage by seemingly harmless control reads.
This patch was adapted from 2.4 patches by Pete Zaitcev. The initial patch of
the series da
> On 18.01.2013 15:24, Bernd Krumboeck wrote:
>
>> Add device driver for USB2CAN interface from "8 devices"
>> (http://www.8devices.com).
>
>>
>
>> Signed-off-by: Bernd Krumboeck
>> Acked-by: Wolfgang Grandegger
>
>
>
> You can add my
>
> Tested-by: Oliver Hartkopp
>
> in the v11 post :-)
>
> I
Hello.
On 19-01-2013 0:22, Alan Stern wrote:
Serialize usb-storage operations with usbfs and 'cat /proc/bus/usb/devices',
so that they cannot disturb storage by seemingly harmless control reads.
This patch was adapted from 2.4 patches by Pete Zaitcev. The initial patch of
the series dates b
>From 4983f3b51e18d008956dd113e0ea2f252774cefc Mon Sep 17 00:00:00 2001
From: Tejun Heo
Date: Fri, 18 Jan 2013 14:05:57 -0800
Synchronous requet_module() from an async worker can lead to deadlock
because module init path may invoke async_synchronize_full(). The
async worker waits for request_mod
>From 84b233adcca3cacd5cfa8013a5feda7a3db4a9af Mon Sep 17 00:00:00 2001
From: Tejun Heo
Date: Fri, 18 Jan 2013 14:05:56 -0800
This function queries whether %current is an async worker executing an
async item. This will be used to implement warning on synchronous
request_module() from async worke
>From 2eaebdb33e1911c0cf3d44fd3596c42c6f502fab Mon Sep 17 00:00:00 2001
From: Tejun Heo
Date: Fri, 18 Jan 2013 14:05:55 -0800
This will be used to implement an inline function to query whether
%current is a workqueue worker and, if so, allow determining which
work item it's executing.
Signed-off
On Fri, 18 Jan 2013, Piergiorgio Sartor wrote:
> I tried the patch below with kernel 3.7, I updated
> my local git copy to that version.
>
> I'm sorry to say it does not seem to fix the issue.
>
> Some explanation, I made three trials, with reboot
> inbetween, of course.
> The first one got the
>From ea138446e51f7bfe55cdeffa3f1dd9cafc786bd8 Mon Sep 17 00:00:00 2001
From: Tejun Heo
Date: Fri, 18 Jan 2013 14:05:55 -0800
Workqueue wants to expose more interface internal to kernel/. Instead
of adding a new header file, repurpose kernel/workqueue_sched.h.
Rename it to workqueue_internal.h a
>From 111c225a5f8d872bc9327ada18d13b75edaa34be Mon Sep 17 00:00:00 2001
From: Tejun Heo
Date: Thu, 17 Jan 2013 17:16:24 -0800
PF_WQ_WORKER is used to tell scheduler that the task is a workqueue
worker and needs wq_worker_sleeping/waking_up() invoked on it for
concurrency management. As rescuers
Hi,
On Fri, Jan 18, 2013 at 03:56:12PM -0500, Shane Whalen wrote:
> I am having problems with the 3.6 musb kernel driver. I am running
> testusb.c and test.sh to try and diagnose where the problem may live.
> Here are the outputs from the 'unlink' and 'control' tests.
>
> Host setup: 3.6.5-rt14-d
Oliver Neukum writes:
> On Friday 18 January 2013 15:25:47 Bjørn Mork wrote:
>> Adding support for the MBIM mode in some Sierra Wireless devices.
>>
>> Some Sierra Wireless firmwares support CDC MBIM but have no CDC
>> Union funtional descriptor. This violates the MBIM specification,
>> but we ca
On Fri, Jan 18, 2013 at 03:56:12PM -0500, Shane Whalen wrote:
> Hi,
>
> I am having problems with the 3.6 musb kernel driver. I am running testusb.c
> and test.sh to try and diagnose where the problem may live. Here are the
> outputs from the 'unlink' and 'control' tests.
3.6 is end-of-life, how
On Fri, 18 Jan 2013, Sarah Sharp wrote:
> On Fri, Jan 18, 2013 at 02:09:26PM -0500, Alan Stern wrote:
> > On Fri, 18 Jan 2013, Sarah Sharp wrote:
> >
> > > Hi Alan,
> > >
> > > What's the current state of USB mass storage suspend? I know there was
> > > some purposed changes to the SCSI or bloc
Hi,
I am having problems with the 3.6 musb kernel driver. I am running testusb.c
and test.sh to try and diagnose where the problem may live. Here are the
outputs from the 'unlink' and 'control' tests.
Host setup: 3.6.5-rt14-deka #1 PREEMPT RT Tue Nov 27 14:23:32 EST 2012 armv7l
armv7l armv7l GNU
Hi Alan,
On Wed, Jan 16, 2013 at 10:55:50AM -0500, Alan Stern wrote:
[...]
> I changed my mind -- it turns out that adding the fix is somewhat
> easier than unlinking one QH at a time.
>
> So now we're ready for some serious testing. The patch below is based
> on the 3.7 kernel, and it doesn't
On Fri, Jan 18, 2013 at 11:23:08AM -0800, Greg KH wrote:
> On Fri, Jan 18, 2013 at 10:24:39AM +0200, Felipe Balbi wrote:
> > regset is a generic implementation of regdump
> > utility through debugfs.
> >
> > Signed-off-by: Felipe Balbi
> > ---
> >
> > Hi Greg, would you take the patch below to d
On Fri, 18 Jan 2013, Oliver Neukum wrote:
> On Friday 18 January 2013 14:09:26 Alan Stern wrote:
>
> > The autosuspend delay at the USB level probably should be set to 0;
> > then the autosuspend delay at the SCSI disk level will control the
> > actual power changes.
>
> What about things like
On Fri, Jan 18, 2013 at 08:23:52PM +, Robert Dvoracek wrote:
> When I plug something in to a USB3 port, nothing appears in the system
> messages. The kernel is just not seeing the USB controller,
> apparently. I'll attach a dmesg.
Do you have the xhci-hcd driver build for this system? Is it
On Friday 18 January 2013 11:58:28 Sarah Sharp wrote:
> Isn't there a sysfs file to control the polling rate for removable
> media? I don't remember where is it though. (I seem to ask about mass
/sys/block/$DEVICE/events_poll_msecs
HTH
Oliver
--
To unsubscribe from thi
On Fri, 18 Jan 2013, David Miller wrote:
> > + ret = fn(dev, cmd, USB_DIR_IN | USB_TYPE_VENDOR |
> > + USB_RECIP_DEVICE, value, index, data, size);
>
> This is not indented properly. When a function call takes up
> multiple lines, the text on the second and subsequent lines m
Hi Roger,
On Fri, 18 Jan 2013, Roger Quadros wrote:
> We don't need multiple aliases for the OMAP USB host clocks and neither
> the dummy clocks so remove them.
>
> CC: Paul Walmsley
> CC: Rajendra Nayak
> CC: Benoit Cousson
> CC: Mike Turquette
>
> Signed-off-by: Roger Quadros
> Reviewed-
Hello.
On 01/18/2013 11:17 PM, Pete Zaitcev wrote:
>>>Don't forget that the same code is working in 2.4 for several years.
>> In mainline? Or some random vendor-specific kernel branch where we have
>> no visiblity into? :)
> Yes, it's in mainline since 2006. However, I am in full agreemen
When I plug something in to a USB3 port, nothing appears in the system
messages. The kernel is just not seeing the USB controller,
apparently. I'll attach a dmesg.
dmesg
Description: Binary data
On Fri, 18 Jan 2013, Sergei Shtylyov wrote:
> Serialize usb-storage operations with usbfs and 'cat /proc/bus/usb/devices',
> so that they cannot disturb storage by seemingly harmless control reads.
>
> This patch was adapted from 2.4 patches by Pete Zaitcev. The initial patch of
> the series dat
On 18.01.2013 15:24, Bernd Krumboeck wrote:
> Add device driver for USB2CAN interface from "8 devices"
> (http://www.8devices.com).
>
> Signed-off-by: Bernd Krumboeck
> Acked-by: Wolfgang Grandegger
You can add my
Tested-by: Oliver Hartkopp
in the v11 post :-)
I have only one small cos
On Fri, 18 Jan 2013 11:59:45 -0800
Greg KH wrote:
> >Don't forget that the same code is working in 2.4 for several years.
>
> In mainline? Or some random vendor-specific kernel branch where we have
> no visiblity into? :)
Yes, it's in mainline since 2006. However, I am in full agreement w
Hello.
On 01/18/2013 10:59 PM, Greg KH wrote:
Serialize usb-storage operations with usbfs and 'cat
/proc/bus/usb/devices',
so that they cannot disturb storage by seemingly harmless control reads.
This patch was adapted from 2.4 patches by Pete Zaitcev. The initial
pat
Best Regards
Tianyu Lan
-Original Message-
From: Alan Stern [mailto:st...@rowland.harvard.edu]
Sent: Saturday, January 19, 2013 2:50 AM
To: Lan, Tianyu
Cc: r...@sisk.pl; gre...@linuxfoundation.org; sarah.a.sh...@linux.intel.com;
oneu...@suse.de; linux-usb@vger.kernel.org
Subject: RE:
Hello.
On 01/18/2013 10:51 PM, Greg KH wrote:
>> +/*
>> + * This is our custom open-coded lock, similar to r/w locks in concept.
>> + * It prevents usb-storage, usbfs, and /proc from simultaneous access.
>> + */
>> +wait_queue_head_t excl_wait;
>> +spinlock_t excl_lock;
>>
On Fri, Jan 18, 2013 at 11:52:53PM +0300, Sergei Shtylyov wrote:
> Hello.
>
> On 01/18/2013 10:48 PM, Greg KH wrote:
>
> >> Serialize usb-storage operations with usbfs and 'cat
> >> /proc/bus/usb/devices',
> >> so that they cannot disturb storage by seemingly harmless control reads.
>
> >> This
On Fri, Jan 18, 2013 at 02:09:26PM -0500, Alan Stern wrote:
> On Fri, 18 Jan 2013, Sarah Sharp wrote:
>
> > Hi Alan,
> >
> > What's the current state of USB mass storage suspend? I know there was
> > some purposed changes to the SCSI or block layer that would have
> > effected suspend, and I won
On 17.01.2013 22:16, Oliver Hartkopp wrote:
>
> I forgot to check the other USB CAN adapters for comparison.
> Will do tomorrow.
>
Here are the results when un-plugging PEAK USB at CAN load:
(..)
[ 862.607999] peak_usb 2-1.2:1.0 can2: Rx urb aborted (-32)
[ 862.828276] usb 2-1.2: USB disco
Hello.
On 01/18/2013 10:48 PM, Greg KH wrote:
>> Serialize usb-storage operations with usbfs and 'cat /proc/bus/usb/devices',
>> so that they cannot disturb storage by seemingly harmless control reads.
>> This patch was adapted from 2.4 patches by Pete Zaitcev. The initial patch
>> of
>> the s
The following changes since commit 8cf65dc386f3634a43312f436cc7a935476a40c4:
usb: ftdi_sio: Crucible Technologies COMET Caller ID - pid added (2013-01-13
13:44:23 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/ tags/usb-3.8-rc4
f
On Friday 18 January 2013 14:09:26 Alan Stern wrote:
> The autosuspend delay at the USB level probably should be set to 0;
> then the autosuspend delay at the SCSI disk level will control the
> actual power changes.
What about things like lsusb? Should we better not go down quite
to zero?
> No
On Fri, Jan 18, 2013 at 11:35:49PM +0300, Sergei Shtylyov wrote:
> + /*
> + * This is our custom open-coded lock, similar to r/w locks in concept.
> + * It prevents usb-storage, usbfs, and /proc from simultaneous access.
> + */
> + wait_queue_head_t excl_wait;
> + spinloc
On Fri, Jan 18, 2013 at 11:35:49PM +0300, Sergei Shtylyov wrote:
> Serialize usb-storage operations with usbfs and 'cat /proc/bus/usb/devices',
> so that they cannot disturb storage by seemingly harmless control reads.
>
> This patch was adapted from 2.4 patches by Pete Zaitcev. The initial patch
On 18.01.2013 15:31, "Bernd Krumböck" wrote:
>> [ 5941.577933] peak_usb 2-1.4:1.0 can3: Rx urb aborted (-32)
>> [ 5941.743693] usb 2-1.2: USB disconnect, device number 11
>> [ 5941.744096] usb_8dev 2-1.2:1.0 can2: device disconnected
>> [ 5941.744121] usb_8dev 2-1.2:1.0 can2: sending command mess
On Fri, Jan 18, 2013 at 07:36:38PM +, Robert Dvoracek wrote:
> Hello. Is there any chance a future version of the kernel will
> support the Renesis USB3 on the DX79TO? Everything else is working
> great though, so I still love you.
Specifics as to exactly what is not working would be appreci
Serialize usb-storage operations with usbfs and 'cat /proc/bus/usb/devices',
so that they cannot disturb storage by seemingly harmless control reads.
This patch was adapted from 2.4 patches by Pete Zaitcev. The initial patch of
the series dates back to 2004 and it unfortunately wasn't applied to
On 01/17/2013 11:15 PM, Venu Byravarasu wrote:
> As Tegra PHY driver needs to access one of the Host registers,
> added few APIs.
I have applied patches 1-3 (v1) and patch 4 (v3) to Tegra's for-3.9/usb
branch.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a
Serialize usb-storage operations with usbfs and 'cat /proc/bus/usb/devices',
so that they cannot disturb storage by seemingly harmless control reads.
This patch was adapted from 2.4 patches by Pete Zaitcev. The initial patch of
the series dates back to 2004 and it unfortunately wasn't applied to
From: Freddy Xin
Date: Thu, 17 Jan 2013 17:32:54 +0800
> +struct ax88179_rx_pkt_header {
> +
> + u8 l4_csum_err:1,
Get rid of such extraneous empty lines. They do not add clarity,
rather they just take up space.
> + ret = fn(dev, cmd, USB_DIR_IN | USB_TYPE_VENDOR |
> +
On Fri, Jan 18, 2013 at 10:24:39AM +0200, Felipe Balbi wrote:
> regset is a generic implementation of regdump
> utility through debugfs.
>
> Signed-off-by: Felipe Balbi
> ---
>
> Hi Greg, would you take the patch below to debugfs ? I don't think debugfs
> should ever change whatever's passed thr
From: Lucas Stach
Date: Wed, 16 Jan 2013 15:24:06 +0100
> The device comes up with a MAC address of all zeros. We need to read the
> initial device MAC from EEPROM so it can be set properly later.
>
> Signed-off-by: Lucas Stach
Applied.
--
To unsubscribe from this list: send the line "unsubscr
From: Lucas Stach
Date: Wed, 16 Jan 2013 15:24:07 +0100
> ASIX AX88772B started to pack data even more tightly. Packets and the ASIX
> packet
> header may now cross URB boundaries. To handle this we have to introduce
> some state between individual calls to asix_rx_fixup().
>
> Signed-off-by: L
On Friday 18 January 2013 15:25:47 Bjørn Mork wrote:
> Adding support for the MBIM mode in some Sierra Wireless devices.
>
> Some Sierra Wireless firmwares support CDC MBIM but have no CDC
> Union funtional descriptor. This violates the MBIM specification,
> but we can easily work around the bug b
On Fri, 18 Jan 2013, Sarah Sharp wrote:
> Hi Alan,
>
> What's the current state of USB mass storage suspend? I know there was
> some purposed changes to the SCSI or block layer that would have
> effected suspend, and I wondered if those made it in.
The block-layer autosuspend patches are in pre
Hi,
On Sun, Dec 02, 2012 at 05:33:36PM +0200, Dmitry Lifshitz wrote:
> Hi,
>
> We are running kernel v3.5.7 on am3517 based hardware (CM-T3517 module).
> Recently we faced with the following issue: am35x MUSB module fails
> when trying to reinsert it.
> It fails with the message "musb-hdrc.0: fai
On Fri, 18 Jan 2013, Lan, Tianyu wrote:
> HI Alan:
> I just find Rafael's patch has resolved this issue. In this
> patch, enable runtime PM
> right after executing subsystem/driver .resume_early() callbacks. When do
> resume(),
> the device's runtime pm has been enabled. This patch
Hi,
On Thu, Jan 17, 2013 at 04:23:48PM +0530, Bhupesh Sharma wrote:
> This patchset tries to enhance the UVC webcam gadget driver and
> is based on Laurent's git tree available here (head uvc-gadget):
> git://linuxtv.org/pinchartl/uvcvideo.git
>
> Note that to ease review and integration of these
Hi,
On Fri, Jan 18, 2013 at 02:30:21PM +0530, Praveen Paneri wrote:
> Changes from v8:
> Resending this patch series after rebasing to the latest usb-next branch.
> Rewording inline comments for better readability.
> Removed IS_ENABLED(CONFIG_OF) as pdev->dev.of_node is enough to check for dt
> s
Hi Alan,
What's the current state of USB mass storage suspend? I know there was
some purposed changes to the SCSI or block layer that would have
effected suspend, and I wondered if those made it in.
I'm specifically looking for when we can expect a USB storage device to
go into auto-suspend. If
On Fri, 18 Jan 2013, Roger Quadros wrote:
> Thanks. I used the below code (also attached) and could reproduce
> corruption on the first byte at ehci->priv. This is from the the kernel log.
>
> > [ 30.381774] ehci-omap ehci-omap.0: ehci_hcd_omap_probe a 0x1234abcd, b
> > 0x5679efba
>
> > [ 12
On Wed, Jan 16, 2013 at 07:00:21PM +0530, Venu Byravarasu wrote:
> Tegra20 USB has 3 PHY instances:
> Instance 1 and 3 are UTMI. Instance 2 is ULPI.
>
> As instance number was used to differentiate ULPI from UTMI,
> used DT param to get this info and processed accordingly.
>
> Signed-off-by: Venu
On Wed, Jan 16, 2013 at 07:00:20PM +0530, Venu Byravarasu wrote:
> Tegra20 USB has 3 PHY instances. Instance 0 is based on
> legacy PHY interface and other two are standard interfaces.
>
> As instance number was used to differentiate legacy from
> standard interfaces, used DT param to get this inf
HI Alan:
I just find Rafael's patch has resolved this issue. In this
patch, enable runtime PM
right after executing subsystem/driver .resume_early() callbacks. When do
resume(),
the device's runtime pm has been enabled. This patch now is already in the
v3.8-rc4.
So this patchset
On 01/18/2013 10:58 AM, Felipe Balbi wrote:
> On Fri, Jan 18, 2013 at 10:28:38AM -0700, Stephen Warren wrote:
>> On 01/18/2013 08:30 AM, Alan Stern wrote:
>>> On Fri, 18 Jan 2013, Venu Byravarasu wrote:
>>>
As Tegra PHY driver needs to access one of the Host
registers, added few APIs.
>>
On Fri, Jan 18, 2013 at 10:28:38AM -0700, Stephen Warren wrote:
> On 01/18/2013 08:30 AM, Alan Stern wrote:
> > On Fri, 18 Jan 2013, Venu Byravarasu wrote:
> >
> >> As Tegra PHY driver needs to access one of the Host registers,
> >> added few APIs.
> >>
> >> Signed-off-by: Venu Byravarasu
> >> --
On Mon, 14 Jan 2013 12:23:05 -0800
Greg KH wrote:
> >Forgot to mention the side effect of the patch: one can't submit read and
> > write URB simultaneously via USBDEVFS_BULK ioctl(). That has been dealt in
> > 2.4
> > by later patch by Pete, which I can try to port if needed.
>
> That's not
On Thu, 2013-01-17 at 14:44 +0800, Wei Shuai wrote:
> OK, I will follow up. after add FLAG_NOARP, how should I handle
> IFF_NOARP? will I do it in cdc_ncm.c or usb_net.c?
usbnet.c
Dan
> 2013/1/17 Dan Williams :
> > On Sat, 2013-01-12 at 19:34 +0800, Wei Shuai wrote:
> >> Infineon(now Intel) HSPA
On 01/18/2013 08:30 AM, Alan Stern wrote:
> On Fri, 18 Jan 2013, Venu Byravarasu wrote:
>
>> As Tegra PHY driver needs to access one of the Host registers,
>> added few APIs.
>>
>> Signed-off-by: Venu Byravarasu
>> ---
>> delta from v2:
>> Renamed USB_PORTSC1 to TEGRA_USB_PORTSC1.
>> Removed tegr
On 01/18/2013 10:04 AM, Stephen Warren wrote:
> On 01/16/2013 06:30 AM, Venu Byravarasu wrote:
>> Tegra20 USB has 3 PHY instances:
>> Instance 1 and 3 are UTMI. Instance 2 is ULPI.
>>
>> As instance number was used to differentiate ULPI from UTMI,
>> used DT param to get this info and processed acc
Hi Greg,
Here are my latest fixes for this -rc cycle. Unless something
extremely important shows up, we should be ready for a final
v3.8 ;-)
Hopefully no surprises will come.
ps: You will notice a few changes on arch/arm/mach-imx/ but they're needed to
make fsl build and work again. We _do_ have
On 01/16/2013 06:30 AM, Venu Byravarasu wrote:
> Tegra20 USB has 3 PHY instances:
> Instance 1 and 3 are UTMI. Instance 2 is ULPI.
>
> As instance number was used to differentiate ULPI from UTMI,
> used DT param to get this info and processed accordingly.
> diff --git a/include/linux/usb/tegra_us
This patch is to bind xhci root hub usb port with its acpi node.
The port num in the acpi table matches with the sequence in the xhci
extended capabilities table. So call usb_hcd_find_raw_port_number() to
transfer hub port num into raw port number which associates with
the sequence in the xhci exte
This patch is to optimize xhci_find_realport_number(). Call
xhci_find_raw_port_number() to get real index in the HW port
status registers instead of scanning through the xHCI roothub
port array.
Signed-off-by: Lan Tianyu
---
drivers/usb/host/xhci-mem.c | 36
xhci driver divides the root hub into two logical hubs which work
respectively for usb 2.0 and usb 3.0 devices. They are independent
devices in the usb core. But in the ACPI table, it's one device node
and all usb2.0 and usb3.0 ports are under it. Binding usb port with
its acpi node needs the raw p
Alan Stern wrote:
> > >> > Should we just drop those warnings?
> > >>
> > >> No opinion.
> > >
> > > I think they should stay.
> >
> > OK, but how about demoting them to debug messages instead of warnings?
>
> If you want to make that change, I don't mind.
I prefer that they stay visible by def
On Thu, 17 Jan 2013, Bjørn Mork wrote:
> Peter Stuge writes:
> > Alan Stern wrote:
> >> > Is this useful to anyone?
> >>
> >> In theory it would be useful to somebody developing firmware for a USB
> >> device. If only such people would test their firmwares under Linux...
> >
> > Some do. Maybe
On Fri, 18 Jan 2013, Lan Tianyu wrote:
> > By the way, have you checked whether the auto-power-off mechanism works
> > correctly when you do a system suspend?
> >
> Thanks for reminder. I test this today and find an issue. If usb device
> was powered off during runtime, pm_runtime_get_sync() in
Usb3.0 device defines function remote wakeup which is only for interface
recipient rather than device recipient. This is different with usb2.0 device's
remote wakeup feature which is defined for device recipient. According usb3.0
spec 9.4.5, the function remote wakeup can be modified by the SetFeat
On Fri, 18 Jan 2013, Vivek Gautam wrote:
> Hi Alan,
>
>
> On Fri, Jan 18, 2013 at 6:46 PM, Felipe Balbi wrote:
> > On Fri, Jan 11, 2013 at 08:32:29PM +0530, Vivek Gautam wrote:
> >> Adding the phy driver to ehci-s5p. Keeping the platform data
> >> for continuing the smooth operation for boards
On Fri, 11 Jan 2013, Vivek Gautam wrote:
> Adding the phy-driver to ohci-exynos. Keeping the platform data
> for continuing the smooth operation for boards which still uses it
>
> Signed-off-by: Vivek Gautam
> Acked-by: Jingoo Han
Acked-by: Alan Stern
--
To unsubscribe from this list: send t
On Fri, 11 Jan 2013, Vivek Gautam wrote:
> Adding the phy driver to ehci-s5p. Keeping the platform data
> for continuing the smooth operation for boards which still uses it
>
> Signed-off-by: Vivek Gautam
> Acked-by: Jingoo Han
Acked-by: Alan Stern
--
To unsubscribe from this list: send the
On Fri, 18 Jan 2013, Venu Byravarasu wrote:
> As Tegra PHY driver needs to access one of the Host registers,
> added few APIs.
>
> Signed-off-by: Venu Byravarasu
> ---
> delta from v2:
> Renamed USB_PORTSC1 to TEGRA_USB_PORTSC1.
> Removed tegra_ehci_set_wakeon_events() and its references.
> Used
On 01/18/2013 05:02 PM, Russell King - ARM Linux wrote:
> On Fri, Jan 18, 2013 at 02:17:09PM +0200, Roger Quadros wrote:
>> +/* only PHY and UNUSED modes don't need TLL */
>> +#define omap_usb_mode_needs_tll(x) ((x != OMAP_USBHS_PORT_MODE_UNUSED) &&\
>> + (x !=
On Fri, Jan 18, 2013 at 07:59:52PM +0530, Vivek Gautam wrote:
> HI Balbi,
>
>
> On Fri, Jan 18, 2013 at 7:52 PM, Felipe Balbi wrote:
> > On Fri, Jan 18, 2013 at 07:51:08PM +0530, Vivek Gautam wrote:
> >> Hi Felipe,
> >>
> >>
> >> On Fri, Jan 18, 2013 at 6:46 PM, Felipe Balbi wrote:
> >> > Hi,
>
On 01/18/2013 04:59 PM, Russell King - ARM Linux wrote:
> On Fri, Jan 18, 2013 at 02:17:08PM +0200, Roger Quadros wrote:
>> +tll->ch_clk = devm_kzalloc(dev, sizeof(struct clk * [tll->nch]),
>> +GFP_KERNEL);
>> +if (!tll->ch_clk) {
>> +
On Fri, Jan 18, 2013 at 02:17:09PM +0200, Roger Quadros wrote:
> +/* only PHY and UNUSED modes don't need TLL */
> +#define omap_usb_mode_needs_tll(x) ((x != OMAP_USBHS_PORT_MODE_UNUSED) &&\
> + (x != OMAP_EHCI_PORT_MODE_PHY))
Growl.
These parens do not make
On Fri, Jan 18, 2013 at 02:17:08PM +0200, Roger Quadros wrote:
> + tll->ch_clk = devm_kzalloc(dev, sizeof(struct clk * [tll->nch]),
> + GFP_KERNEL);
> + if (!tll->ch_clk) {
> + ret = -ENOMEM;
> + dev_err(dev, "Couldn't allo
> On 16.01.2013 09:07, "Bernd Krumböck" wrote:
>
>> Hi Oliver!
>>
>>> When detaching the device from the CAN bus when sending/receiving CAN
traffic
>>> i got these dmesg infos:
>>>
>>> [ 960.047130] usb_8dev 2-1.4:1.0 can2: Unknown status/error message (0)
>>> [ 976.544343] usb_8dev 2-1.4:1.0 can
Hi Alan,
On Fri, Jan 18, 2013 at 6:46 PM, Felipe Balbi wrote:
> On Fri, Jan 11, 2013 at 08:32:29PM +0530, Vivek Gautam wrote:
>> Adding the phy driver to ehci-s5p. Keeping the platform data
>> for continuing the smooth operation for boards which still uses it
>>
>> Signed-off-by: Vivek Gautam
>
HI Balbi,
On Fri, Jan 18, 2013 at 7:52 PM, Felipe Balbi wrote:
> On Fri, Jan 18, 2013 at 07:51:08PM +0530, Vivek Gautam wrote:
>> Hi Felipe,
>>
>>
>> On Fri, Jan 18, 2013 at 6:46 PM, Felipe Balbi wrote:
>> > Hi,
>> >
>> > On Mon, Jan 14, 2013 at 05:52:15PM +0530, Vivek Gautam wrote:
>> >> This
The driver description files gives these names to the vendor specific
functions on this modem:
Diag VID_19D2&PID_0265&MI_00
NMEA VID_19D2&PID_0265&MI_01
AT cmd VID_19D2&PID_0265&MI_02
Modem VID_19D2&PID_0265&MI_03
NetVID_19D2&PID_0265&MI_04
Signed-off-by: Bjørn Mork
---
drivers/ne
1 - 100 of 176 matches
Mail list logo
