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 can2: Unknown status/error message (0)
>
Sorry, I can't do this
On Tuesday 15 January 2013 23:26:20 Woody Suwalski wrote:
> The modules are insmoded in a fixed order:
> usb-common, usbcore, xhci-hcd, ehci-hcd, uhci-hcd, ohci-hcd, usbhid,
> usb_storage,...
>
> If all USB is built as modules - I get read errors from USB drives when
> accessing squash image, b
This mxs usbphy is only needs to be on after system boots
up, and software never needs to control it anymore.
Meanwhile, usbphy's parent needs to be notified if usb
is suspend or not. So we design below mxs usbphy usage:
- usbphy1_gate and usbphy2_gate:
Their parents are dummy clock, we only needs
It needs to call set_suspend during USB suspend/resume
Signed-off-by: Peter Chen
---
drivers/usb/otg/mxs-phy.c | 20
1 files changed, 20 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/otg/mxs-phy.c b/drivers/usb/otg/mxs-phy.c
index 7630272..5158332 100644
--- a/dr
During the system suspend/resume procedure, the USB also
needs to go suspend/resume procedure, this patch adds
related APIs. It is tested at i.mx6q sabrelite. Meanwhile,
it fixes the bug that the USB will out of work after
system suspend/resume.
Signed-off-by: Peter Chen
---
drivers/usb/chipidea
On Wed, 16 Jan 2013, Fernando Luis Vazquez Cao wrote:
> I noticed that the patch was tagged "for-3.9". Does this mean
> that it is too late to get it merged during the current release
> cycle?
I currently don't have anything queued for 3.8, and this particular patch
doesn't justify a separate pu
On 01/04/2013 02:20 PM, Gary Thomas wrote:
>
>
> On Thursday, January 3, 2013 9:21:19 AM UTC-7, Felipe Balbi wrote:
>
> Hi,
>
> On Wednesday, January 2, 2013 10:44:50 PM UTC+2, Gary Thomas wrote:
>
> I have a video adapter attached to my EHCI port which runs full
> spee
On Wed, Jan 16, 2013 at 3:52 AM, Tejun Heo wrote:
> This avoids the described deadlock because iosched module doesn't use
> async and thus wouldn't invoke async_synchronize_full(). This is
> hacky and incomplete. It will deadlock if async module loading nests;
> however, this works around the kn
As part of registering tegra USB PHY as platform driver, prepared
patches to add separate DT nodes describing Tegra USB PHY properties.
Modified instance number based processing to make use of the added
DT properties. As PHY will be registered as separate driver, removed
ehci register access from P
As Tegra PHY driver needs to access one of the Host registers,
added few APIs.
Signed-off-by: Venu Byravarasu
---
drivers/usb/host/ehci-tegra.c | 71 -
drivers/usb/phy/tegra_usb_phy.c | 51 +++
include/linux/usb/tegra_usb_phy.
Add DT nodes for Tegra USB PHY along with related documentation.
Also added a phandle property to controller DT node, for referring
to connected PHY instance.
Signed-off-by: Venu Byravarasu
---
.../bindings/usb/nvidia,tegra20-ehci.txt |1 +
.../bindings/usb/nvidia,tegra20-usb-phy.t
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 info and
processed accordingly.
Signed-off-by: Venu Byravarasu
---
drivers/
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 Byravarasu
---
drivers/usb/phy/tegra_usb_phy.c | 23 +---
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
---
A similar fix was added into U-Boot:
http://patchwork.ozlabs.org/patch/179409/
v2: pass flag in the data field instead of clobbe
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: Lucas Stach
---
I've running this patch for some weeks already now and
This is a handy macro to check if the port requires the
USB TLL module or not. Use it to Enable the TLL module and manage
the clocks.
Signed-off-by: Roger Quadros
---
drivers/mfd/omap-usb-tll.c | 20
1 files changed, 12 insertions(+), 8 deletions(-)
diff --git a/drivers/m
Fixes the below build warning when driver is built-in.
drivers/mfd/omap-usb-host.c:750:12: warning:
‘usbhs_omap_remove’ defined but not used [-Wunused-function]
Signed-off-by: Roger Quadros
---
drivers/mfd/omap-usb-host.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a
We don't need multiple aliases for the OMAP USB host clocks so remove them.
CC: Paul Walmsley
CC: Rajendra Nayak
CC: Benoit Cousson
CC: Mike Turquette
Signed-off-by: Roger Quadros
Acked-by: Paul Walmsley
---
arch/arm/mach-omap2/cclock44xx_data.c |7 ---
1 files changed, 0 insertion
All ports have similarly named port clocks so we can
bunch them into a port data structure and use for loop
to enable/disable the clocks.
Dynamically allocate and get clocks based on number of ports
available on the platform
Signed-off-by: Roger Quadros
---
drivers/mfd/omap-usb-host.c | 180 ++
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
Acked-by: Paul Walmsley
---
arch/arm/mach-omap2/cclock3xxx_data.c | 11
This driver does not request any gpios so don't free them.
Fixes L3 bus error on multiple modprobe/rmmod of ehci_hcd
with ehci-omap in use.
Signed-off-by: Roger Quadros
---
drivers/usb/host/ehci-omap.c |8
1 files changed, 0 insertions(+), 8 deletions(-)
diff --git a/drivers/usb/ho
clk_set_parent is expected to fail on OMAP3 platforms. We don't
consider that as fatal so don't spam console.
Signed-off-by: Roger Quadros
---
drivers/mfd/omap-usb-host.c | 18 +-
1 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/mfd/omap-usb-host.c b/drive
We split initializing revision 1 and revision 2 into different
functions. Initialization is now done dynamically so that only
the number of ports available on the system are initialized.
Signed-off-by: Roger Quadros
---
drivers/mfd/omap-usb-host.c | 122 +
Enable the optional HSIC clocks (60MHz and 480MHz) for the ports
that are configured in HSIC mode.
Signed-off-by: Roger Quadros
---
drivers/mfd/omap-usb-host.c | 77 +++---
1 files changed, 71 insertions(+), 6 deletions(-)
diff --git a/drivers/mfd/omap-usb-
The driver does not have an interrupt handler and
we don't really need a spinlock, so get rid of it.
Signed-off-by: Roger Quadros
---
drivers/mfd/omap-usb-host.c | 16
1 files changed, 0 insertions(+), 16 deletions(-)
diff --git a/drivers/mfd/omap-usb-host.c b/drivers/mfd/oma
Get rid of the unnecessary spin_lock_irqsave/restore() as there is
no interrupt handler for this driver. Instead we serialize access
to tll_dev using a global spinlock.
Signed-off-by: Roger Quadros
---
drivers/mfd/omap-usb-tll.c | 53 ++-
1 files changed
The TLL module on OMAP5 has 3 channels.
HSIC mode requires the TLL channel to be in Transparent UTMI mode.
Signed-off-by: Roger Quadros
---
drivers/mfd/omap-usb-tll.c | 14 ++
1 files changed, 14 insertions(+), 0 deletions(-)
diff --git a/drivers/mfd/omap-usb-tll.c b/drivers/mfd/o
The revision register should tell us how many ports are present.
Signed-off-by: Roger Quadros
---
drivers/mfd/omap-usb-host.c | 33 -
1 files changed, 28 insertions(+), 5 deletions(-)
diff --git a/drivers/mfd/omap-usb-host.c b/drivers/mfd/omap-usb-host.c
index
Use devm_ variants of kzalloc and ioremap. Also clean up error path.
Signed-off-by: Roger Quadros
---
drivers/mfd/omap-usb-host.c | 38 +++---
1 files changed, 11 insertions(+), 27 deletions(-)
diff --git a/drivers/mfd/omap-usb-host.c b/drivers/mfd/omap-usb-hos
Both OMAP4 and 5 exhibit the same revision ID in the REVISION register
but they have different number of ports i.e. 2 and 3 respectively.
So we can't rely on REVISION register for number of ports on OMAP5
and depend on platform data (or device tree) instead.
Signed-off-by: Roger Quadros
---
driv
Get rid of the unnecessary missing platform data checks
in runtime_suspend/resume. We are already checking for missing
platform data in probe.
Signed-off-by: Roger Quadros
---
drivers/mfd/omap-usb-host.c | 10 --
1 files changed, 0 insertions(+), 10 deletions(-)
diff --git a/drivers/m
No need to check for missing platform data in runtime_suspend/resume
as it makes more sense to do it in the probe function.
Signed-off-by: Roger Quadros
---
drivers/mfd/omap-usb-tll.c | 15 +--
1 files changed, 5 insertions(+), 10 deletions(-)
diff --git a/drivers/mfd/omap-usb-tll
omap_enable/disable_tll() can fail if TLL device is not
initialized. It could be due to multiple reasons and not only
due to missing platform data.
Also make local variables static and use 'struct device *'
instead of 'struct platform_device *' for global reference.
Signed-off-by: Roger Quadros
Hi,
This patchset addresses the following
- Consolidate USB Host platform data.
- Avoid addressing clocks one by one by name and use a for loop + bunch
of cleanups.
- Get number of channels/ports dynamically either from revision register
or from platform data. Avoids getting clocks that are n
Use devm_ variants of kzalloc() and ioremap(). Simplify the error path.
Signed-off-by: Roger Quadros
---
drivers/mfd/omap-usb-tll.c | 36 +++-
1 files changed, 11 insertions(+), 25 deletions(-)
diff --git a/drivers/mfd/omap-usb-tll.c b/drivers/mfd/omap-usb-tll.
Every channel has a functional clock that is similarly named.
It makes sense to use a for loop to manage these clocks as OMAPs
can come with up to 3 channels.
Dynamically allocate and get channel clocks depending on the
number of clocks avaiable on the platform.
Signed-off-by: Roger Quadros
---
Let's have a single platform data structure for the OMAP's High-Speed
USB host subsystem instead of having 3 separate ones i.e. one for
board data, one for USB Host (UHH) module and one for USB-TLL module.
This makes the code much simpler and avoids creating multiple copies of
platform data.
Sign
Fix channel count detecion for REV2. Also, don't give up
if we don't recognize the IP Revision. We assume the default
number of channels (i.e. 3) for unrecognized IPs.
Signed-off-by: Roger Quadros
---
drivers/mfd/omap-usb-tll.c | 20 +++-
1 files changed, 11 insertions(+), 9 de
On Wed, Jan 16, 2013 at 04:43:35PM +0200, Roger Quadros wrote:
> + spin_lock_irqsave(&tll->lock, flags);
> +
> + for (i = 0; i < tll->nch; i++) {
> + char clkname[] = "usb_tll_hs_usb_chx_clk";
> + struct clk *fck;
> +
> + snprintf(clkname, sizeof(clkname)
On Tue, 15 Jan 2013, Woody Suwalski wrote:
> > Another important change is that the EHCI driver is now split into two
> > modules. That can slow down loading and affect the timing.
> >
> > Alan Stern
> >
> My testcase is a live initramfs + squash root.
> The boot logic is as stable as can be - un
Added a phandle in the dt node for usb_otg to bind the PHY with the USB
controller and also updated the documentation with the binding information.
Signed-off-by: Kishon Vijay Abraham I
---
I'll add this patch in this series "usb: musb: add driver for control module"
which contains the dt data to
This is in preparation for the changes in PHY library to support adding
and getting multiple PHYs of the same type. In the new design, the
binding information between the PHY and the USB controller should be
specified in the platform specific initialization code. So it's been
done for OMAP platform
In order to add support for multipe PHY's of the same type, the API's
for adding PHY and getting PHY has been changed. Now the binding
information of the PHY and controller should be done in platform file
using usb_bind_phy API. And for getting a PHY, the device pointer of the
USB controller and an
Added an API devm_usb_get_phy_by_phandle(), to get usb phy by passing a
device node phandle value. This function will return a pointer to
the phy on success, -EPROBE_DEFER if there is a device_node for the phandle,
but the phy has not been added, or a ERR_PTR() otherwise.
Cc: Marc Kleine-Budde
Si
New platforms are added which has multiple PHY's (of same type) and
which has multiple USB controllers. The binding information has to be
present in the PHY library (otg.c) in order for it to return the
appropriate PHY whenever the USB controller request for the PHY. So
added a new API to pass the
New platforms are being added which has multiple PHY's (of same type) and
which has multiple USB controllers. The binding information has to be
present in the PHY library (otg.c) in order for it to return the
appropriate PHY whenever the USB controller request for the PHY. So
added a new API to pas
The OMAP glue has been modified to get PHY by phandle for dt boot.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/usb/musb/omap2430.c |7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/musb/omap2430.c b/drivers/usb/musb/omap2430.c
index 3628a50..08709cf 1
Hi Tomasz,
On Wed, Jan 16, 2013 at 1:19 PM, Tomasz Figa wrote:
> Hi Vivek,
>
> Don't you need also some clkdev lookup entry to make the clock available
> in the driver?
>
This clock source we added with a motive of completion, however it's
not being used as of now.
As far as i could see the loo
On 01/16/2013 04:55 PM, Russell King - ARM Linux wrote:
> On Wed, Jan 16, 2013 at 04:43:35PM +0200, Roger Quadros wrote:
>> +spin_lock_irqsave(&tll->lock, flags);
>> +
>> +for (i = 0; i < tll->nch; i++) {
>> +char clkname[] = "usb_tll_hs_usb_chx_clk";
>> +struct clk
On Wed, 16 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
> --- a/drivers/usb/host/ehci-tegra.c
> +++ b/drivers/usb/host/ehci-tegra.c
> @@ -605,6 +619,50 @@ static const struct dev_pm_ops te
Hi Tomasz,
On Wed, Jan 16, 2013 at 1:14 PM, Tomasz Figa wrote:
> Hi Vivek,
>
> On Tuesday 15 of January 2013 19:08:30 Vivek Gautam wrote:
>> Adding OHCI device tree node for Exynos5250 along with
>> the device base address.
>>
>> Signed-off-by: Vivek Gautam
>> Acked-by: Jingoo Han
>> Acked-by:
On Tue, 15 Jan 2013, Lan Tianyu wrote:
> Hi Greg&Alan:
> Do you have some more comments about this patchset? Thanks.
I don't have any more comments at this point. It looks okay to me.
Acked-by: Alan Stern
By the way, have you checked whether the auto-power-off mechanism works
correctly
On Mon, 14 Jan 2013, Piergiorgio Sartor wrote:
> > Okay, I figured out what the problem is. It really is a bug in
> > ehci-hcd; the driver doesn't do what the spec requires when unlinking
> > more than one QH at a time.
>
> Well, I'm happy to read this. Good that you find it!
>
> It puzzles m
Hello, Alan.
On Tue, Jan 15, 2013 at 11:01:15PM -0500, Alan Stern wrote:
> > The current domain implementation is somewhere inbetween. It's not
> > completely simplistic system and at the same time not developed enough
> > to do properly stacked flushing.
>
> I like your idea of chronological sy
But no, it's not just some trivial one-liner. Especially the question
about "when to try to load the module that is given on the kernel
command line" is not trivial. Do we require that the module is in the
initrd and loadable basically immediate at boot? Do we try again after
switching the root
Hey,
On Tue, Jan 15, 2013 at 07:37:42PM -0800, Linus Torvalds wrote:
> I do want the same user-visible semantics, so it's not some one-liner.
>
> The compiled-in elevator would be easy enough to handle in the Kconfig
> file (maybe we do already, I didn't even bother to check). The real
> problem
On Wed, 16 Jan 2013, Tejun Heo wrote:
> Hello, Alan.
>
> On Tue, Jan 15, 2013 at 11:01:15PM -0500, Alan Stern wrote:
> > > The current domain implementation is somewhere inbetween. It's not
> > > completely simplistic system and at the same time not developed enough
> > > to do properly stacked
As Arjan suggested, trying to load the default modules right after the
initial rootfs mount could be an acceptable compromise and it would be
really nice (for both code sanity and avoiding future problems) to be
able to declare module loading nested inside async unspported.
we can even try twi
On Wed, Jan 16, 2013 at 9:03 AM, Arjan van de Ven wrote:
>
> we can even try twice
>
> the first time right after we mount the initramfs
> the second time when the initramfs code exits, and before we exec init
> (the initramfs supposedly mounted the real root fs at this point)
Yes. This, together
On 01/16/2013 12:12 AM, Felipe Balbi wrote:
> Hi,
>
> On Tue, Jan 15, 2013 at 11:04:51AM -0700, Stephen Warren wrote:
>> On 01/15/2013 03:19 AM, Venu Byravarasu wrote:
>>> As tegra_usb_phy_clk_disable/enable() are not being used,
>>> removing them.
>>
>> Greg, Felipe,
>>
>> Again if I may, I'll
083b804c4d3e1e3d0eace56bdbc0f674946d2847 ("async: use workqueue for
worker pool") made it possible that async jobs are moved from pending
to running out-of-order. While pending async jobs will be queued and
dispatched for execution in the same order, nothing guarantees they'll
enter "1) move self
On Wed, 16 Jan 2013, Martin Mokrejs wrote:
> A corresponding diff of dmesg output is attached. Note that the first
> kmemleak in there
> happened just without any prior fiddling with a USB drive. For about two days
> I haven't
> connected a drive. However, usb-storage might be in a wrong shape s
Hello, Alan.
On Wed, Jan 16, 2013 at 12:01:53PM -0500, Alan Stern wrote:
> > The problem here is that "flush everything which comes before me" is
> > used to order async jobs. e.g. after async jobs probe the hardware
> > they order themselves by flushing before registering them, so unless
>
> I
On Wed, 16 Jan 2013, Tejun Heo wrote:
> Hello, Alan.
>
> On Wed, Jan 16, 2013 at 12:01:53PM -0500, Alan Stern wrote:
> > > The problem here is that "flush everything which comes before me" is
> > > used to order async jobs. e.g. after async jobs probe the hardware
> > > they order themselves by
Hello.
On 01/16/2013 05:43 PM, Roger Quadros wrote:
> Use devm_ variants of kzalloc and ioremap. Also clean up error path.
> Signed-off-by: Roger Quadros
[...]
> diff --git a/drivers/mfd/omap-usb-host.c b/drivers/mfd/omap-usb-host.c
> index 061366d..0f190b6 100644
> --- a/drivers/mfd/omap-usb-
Hello.
On 01/16/2013 05:43 PM, Roger Quadros wrote:
> Use devm_ variants of kzalloc() and ioremap(). Simplify the error path.
> Signed-off-by: Roger Quadros
> ---
> drivers/mfd/omap-usb-tll.c | 36 +++-
> 1 files changed, 11 insertions(+), 25 deletions(-)
> d
Hi Nobuhiro,
On Tue, Jan 15, 2013 at 9:01 PM, Nobuhiro Iwamatsu wrote:
> Hi,
>
>
>
> On Tue, Jan 15, 2013 at 6:54 PM, Ezequiel Garcia
> wrote:
>> Cc: Lior Amsalem
>> Cc: Thomas Petazzoni
>> Cc: Gregory CLEMENT
>> Signed-off-by: Ezequiel Garcia
>> ---
>> arch/arm/boot/dts/armada-xp-openblock
Dear Ezequiel Garcia,
On Wed, 16 Jan 2013 16:16:59 -0300, Ezequiel Garcia wrote:
> >> + usb@d005 {
> >> + status = "okay";
> >> + };
> >> + usb@d0051000 {
> >> + status = "okay";
> >> + };
> >>
Hello.
On 01/14/2013 11:23 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.28 patch by Pete Zaitcev -- which I even
>>> had to
>>>
On Wed, Jan 16, 2013 at 12:22:59PM -0500, Alan Stern wrote:
> On Wed, 16 Jan 2013, Martin Mokrejs wrote:
>
> > A corresponding diff of dmesg output is attached. Note that the first
> > kmemleak in there
> > happened just without any prior fiddling with a USB drive. For about two
> > days I haven
From: Tushar Behera
Date: Tue, 15 Jan 2013 11:09:01 +0530
> commit 24b1042c4eb2 ("usbnet: dm9601: apply introduced usb command
> APIs") removes the distiction between DM_WRITE_REG and DM_WRITE_REGS
> command. The distiction is reintroduced to the driver so that the
> functionality of the driver r
From: Bjørn Mork
Date: Tue, 15 Jan 2013 10:19:50 +0100
> The driver description files gives these names to the vendor specific
> functions on this modem:
>
> Diagnostics VID_2357&PID_0201&MI_00
> NMEAVID_2357&PID_0201&MI_01
> Modem VID_2357&PID_0201&MI_03
> Networkcard VID_2357
From: Bjørn Mork
Date: Tue, 15 Jan 2013 09:34:07 +0100
> The main problem is that these devices don't support ethernet. They
> support IP (v4 and _maybe_ v6) with an ethernet header. Many of them
> will do ARP (and IPv6 ND) as well to complete the picture, but some of
> them don't and that's wh
On Wed, 16 Jan 2013, Sarah Sharp wrote:
> > Sarah, I looked through the xhci-hcd driver. There does appear to be a
> > leak in xhci-ring.c:handle_tx_event().
>
> Thanks for catching that.
>
> > The routine looks like this:
> >
> > /* Leave the TD around for the reset endpoi
This patch adds default module loading and uses it to load the default
block elevator. During boot, it's called right after initramfs or
initrd is made available and right before control is passed to
userland. This ensures that as long as the modules are available in
the usual places in initramfs
Block layer allows selecting an elevator which is built as a module to
be selected as system default via kernel param "elevator=". This is
achieved by automatically invoking request_module() whenever a new
block device is initialized and the elevator is not available.
This led to an interesting d
On Sat, 2013-01-12 at 19:34 +0800, Wei Shuai wrote:
> Infineon(now Intel) HSPA Modem platform NCM cannot support ARP. so I
> introduce a flag CDC_NCM_DRIVER_DATA_NOARP which is defined in
> driver_info:data. so later on, if more such buggy devices are found, they
> could use same flag to handle.
On 01/16/2013 06:30 AM, Venu Byravarasu wrote:
> Add DT nodes for Tegra USB PHY along with related documentation.
> Also added a phandle property to controller DT node, for referring
> to connected PHY instance.
Just a quick reminder to Greg, Felipe, Alan: Once this series passes
review, I'll need
On 01/16/2013 08:08 AM, Alan Stern wrote:
> On Wed, 16 Jan 2013, Venu Byravarasu wrote:
>
>> As Tegra PHY driver needs to access one of the Host registers,
>> added few APIs.
>> --- a/drivers/usb/host/ehci-tegra.c
>> +++ b/drivers/usb/host/ehci-tegra.c
>> +void tegra_ehci_set_wakeon_events(struc
Sarah Sharp wrote:
> On Wed, Jan 16, 2013 at 12:22:59PM -0500, Alan Stern wrote:
>> On Wed, 16 Jan 2013, Martin Mokrejs wrote:
>>
>>> A corresponding diff of dmesg output is attached. Note that the first
>>> kmemleak in there
>>> happened just without any prior fiddling with a USB drive. For abo
On Wed, 16 Jan 2013, Stephen Warren wrote:
> On 01/16/2013 08:08 AM, Alan Stern wrote:
> > On Wed, 16 Jan 2013, Venu Byravarasu wrote:
> >
> >> As Tegra PHY driver needs to access one of the Host registers,
> >> added few APIs.
>
> >> --- a/drivers/usb/host/ehci-tegra.c
> >> +++ b/drivers/usb/ho
On Sat, 5 Jan 2013 10:25:38 +0800
Ming Lei wrote:
> This patchset try to solve one deadlock problem which might be caused
> by memory allocation with block I/O during runtime PM and block device
> error handling path. Traditionly, the problem is addressed by passing
> GFP_NOIO statically to mm,
The tty is NULL when the port is hanging up.
chase_port() needs to check for this.
This patch is intended for stable series.
The behavior was observed and tested in Linux 3.2 and 3.7.1.
Johan Hovold submitted a more elaborate patch for the mainline kernel.
[ 56.277883] usb 1-1: edge_bulk_in_c
On 14/01/13 16:37, Johan Hovold wrote:
> I've prepared a patch series which removes the custom chase_port
> function and replaces it with the corresponding generic implementations
> instead (which does not suffer from the problem you found).
>
> However, I think your solution is probably the best o
An isochronous TD is comprised of one isochronous TRB chained to zero or
more normal TRBs. Only the isoc TRB has the TBC and TLBPC fields. The
normal TRBs must set those fields to zeroes. The code was setting the
TBC and TLBPC fields for both isoc and normal TRBs. Fix this.
This should be back
To calculate the TD size for a particular TRB in an isoc TD, we need
know the endpoint's max packet size. Isochronous endpoints also encode
the number of additional service opportunities in their wMaxPacketSize
field. The TD size calculation did not mask off those bits before using
the field. Th
On Wed, Jan 16, 2013 at 08:30:59PM +0530, Kishon Vijay Abraham I wrote:
> In order to add support for multipe PHY's of the same type, the API's
> for adding PHY and getting PHY has been changed. Now the binding
> information of the PHY and controller should be done in platform file
> using usb_bind
Hi Nickolai,
Thanks for catching this. Don't worry about sending a new patch with
the short description for the commit, I'll fix that when I send it off.
Sarah Sharp
On Mon, Jan 07, 2013 at 10:39:31PM -0500, Nickolai Zeldovich wrote:
> Fix incorrect bit test that originally showed up in
> 4ee82
On Thu, Jan 17, 2013 at 7:37 AM, Andrew Morton
wrote:
> On Sat, 5 Jan 2013 10:25:38 +0800
> Ming Lei wrote:
>
>> This patchset try to solve one deadlock problem which might be caused
>> by memory allocation with block I/O during runtime PM and block device
>> error handling path. Traditionly, th
On Wed, Jan 16, 2013 at 04:59:03PM +0800, Peter Chen wrote:
> This mxs usbphy is only needs to be on after system boots
> up, and software never needs to control it anymore.
> Meanwhile, usbphy's parent needs to be notified if usb
> is suspend or not. So we design below mxs usbphy usage:
>
> - usb
Alan Stern wrote:
On Tue, 15 Jan 2013, Woody Suwalski wrote:
Another important change is that the EHCI driver is now split into two
modules. That can slow down loading and affect the timing.
Alan Stern
My testcase is a live initramfs + squash root.
The boot logic is as stable as can be - un
Fixed coding style issue with single line braces.
Signed-off-by: Jake Champlin
---
drivers/staging/usbip/usbip_common.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/staging/usbip/usbip_common.c
b/drivers/staging/usbip/usbip_common.c
index 75189fe..75aa5bf 100644
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?
2013/1/17 Dan Williams :
> On Sat, 2013-01-12 at 19:34 +0800, Wei Shuai wrote:
>> Infineon(now Intel) HSPA Modem platform NCM cannot support ARP. so I
>> introduce a flag CDC_NCM_DRI
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
94 matches
Mail list logo
