smatch reports the following warnings:
drivers/net/can/usb/esd_usb2.c:640 esd_usb2_start() error: doing dma on the
stack (msg)
drivers/net/can/usb/esd_usb2.c:846 esd_usb2_close() error: doing dma on the
stack (msg)
drivers/net/can/usb/esd_usb2.c:855 esd_usb2_close() error: doing dma on the
Dan == Dan Carpenter dan.carpen...@oracle.com writes:
Dan The callers expect this function to return zero on success or -EIO if it
Dan times out. The type should be int instead of unsigned short.
Dan Signed-off-by: Dan Carpenter dan.carpen...@oracle.com
Acked-by: Peter Korsgaard
Adding the transceiver to hsotg driver. Keeping the platform data
for continuing the smooth operation for boards which still uses it
Signed-off-by: Praveen Paneri p.pan...@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/s3c-hsotg.c | 37
The code in the driver is based on the specs from ADMTek (later,
Infineon). Since i never suspend my machines this feature has not been
tested by me.
However, if the proposed patch is the right thing to do i'd be happy to
see it applied.
cheers,
Petko
On Fri, 18 Jan 2013, Ming Lei
Added a new driver for the usb part of control module. This has an API
to power on the USB2 phy and an API to write to the mailbox depending on
whether MUSB has to act in host mode or in device mode.
Writing to control module registers for doing the above task which was
previously done in omap
Added a new driver for the usb part of control module. This has an API
to power on the USB2 phy and an API to write to the mailbox depending on
whether MUSB has to act in host mode or in device mode.
Writing to control module registers for doing the above task which was
previously done in omap
Start using the control module driver for powering on the PHY and for
writing to the mailbox instead of writing to the control module
registers on their own.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
Documentation/devicetree/bindings/usb/omap-usb.txt |4 ++
Added has_mailbox to the musb platform data to specify that omap uses
an external mailbox (in control module) to communicate with the musb
core during device connect and disconnect.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/mach-omap2/usb-musb.c |3 +++
A seperate driver has been added to handle the usb part of control
module. A device for the above driver is created here, using the register
address information to be used by the driver for powering on the PHY and
for writing to the mailbox.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
On 01/17/2013 06:59 PM, Tony Lindgren wrote:
* Alan Stern st...@rowland.harvard.edu [130117 07:19]:
On Thu, 17 Jan 2013, Roger Quadros wrote:
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,
This patch series adds dt data to get MUSB working in omap4 and omap3.
Long time back a patch series with the same title was sent but only
a part of it got merged. The rest of it wasn't merged because of
adding omap control usb data to glue and usb phy.
Now there exists a separate driver for
Add omap control usb data in omap4 device tree file. This will have the
register address of registers to power on the PHY and to write to
mailbox.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/omap4.dtsi |8
1 file changed, 8 insertions(+)
diff --git
On Fri, Jan 18, 2013 at 5:57 AM, Andrew Morton
a...@linux-foundation.org wrote:
Fair enough, thanks.
I grabbed the patches for 3.9-rc1. It is good that the page
allocator's newly-added test of current-flags is not on the fastpath.
Andrew, great thanks, :-)
Also thank Alan, Oliver,
Hi,
On Friday 18 January 2013 03:25 AM, Richard Genoud wrote:
Hi,
I've got an usb3.0 HDD dock ( http://www.icydock.com/goods.php?id=130
) wich uses JMicron JMS539 chipset and an USB3.0 board based on VIA
VL800 B3 ( http://www.ldlc.com/fiche/PB00130847.html )
When I plug the dock in an UBS3.0
Hi Chao,
You latest patches caused another breakage for x86. Please fix it asap
or I will have to drop all your changes from my pull request.
ERROR: mv_usb2_unregister_notifier [drivers/usb/gadget/mv_udc.ko] undefined!
ERROR: mv_usb2_register_notifier [drivers/usb/gadget/mv_udc.ko] undefined!
On 2013年01月16日 23:45, Alan Stern wrote:
On Tue, 15 Jan 2013, Lan Tianyu wrote:
Hi GregAlan:
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 st...@rowland.harvard.edu
By the way,
drivers/usb/gadget/u_serial.c:1291:5: sparse: symbol \
'userial_init' was not declared. Should it be static?
drivers/usb/gadget/zero.c:66:25: sparse: symbol \
'gzero_options' was not declared. Should it be static?
Reported-by: Fengguang Wu fengguang...@intel.com
Signed-off-by:
dwc3_gadget_set_ep_config expects maxburst as incremented by 1. So, by
default initialize ep-maxburst to 1 for ep0.
Signed-off-by: Pratyush Anand pratyush.an...@st.com
---
drivers/usb/dwc3/gadget.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/dwc3/gadget.c
Hi,
On Tue, Jan 15, 2013 at 02:12:51PM +0530, Kishon Vijay Abraham I wrote:
Added a new driver for the usb part of control module. This has an API
to power on the USB2 phy and an API to write to the mailbox depending on
whether MUSB has to act in host mode or in device mode.
Writing to
On Thu, Jan 17, 2013 at 04:44:52PM +0530, kishon wrote:
@@ -171,6 +188,11 @@ static inline void devm_usb_put_phy(struct device
*dev, struct usb_phy *x)
{
}
+static inline struct usb_phy_bind *usb_bind_phy(const char *dev_name, u8
index,
+ const char
On Wed, Jan 16, 2013 at 08:30:56PM +0530, Kishon Vijay Abraham I wrote:
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
tree: git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git gadget
head: 7620f5f22e9317ab26c0fdbdd15c5e9ed972ef89
commit: 84b140524c107fb4f4fe618509bc067245c9d878 [19/61] usb: phy: mv_usb2: add
PHY driver for marvell usb2 controller
config: make ARCH=x86_64 allmodconfig
All
On Friday 18 January 2013 05:18 PM, Felipe Balbi wrote:
On Wed, Jan 16, 2013 at 08:30:56PM +0530, Kishon Vijay Abraham I wrote:
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
Hi,
On Fri, Jan 18, 2013 at 03:10:42PM +0530, Kishon Vijay Abraham I wrote:
Added a new driver for the usb part of control module. This has an API
to power on the USB2 phy and an API to write to the mailbox depending on
whether MUSB has to act in host mode or in device mode.
Writing to
Hi,
On Fri, Jan 18, 2013 at 03:10:45PM +0530, Kishon Vijay Abraham I wrote:
Start using the control module driver for powering on the PHY and for
writing to the mailbox instead of writing to the control module
registers on their own.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
On Fri, Jan 18, 2013 at 07:48:14PM +0800, kbuild test robot wrote:
tree: git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git gadget
head: 7620f5f22e9317ab26c0fdbdd15c5e9ed972ef89
commit: 84b140524c107fb4f4fe618509bc067245c9d878 [19/61] usb: phy: mv_usb2:
add PHY driver for marvell
tree: git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git gadget
head: 7620f5f22e9317ab26c0fdbdd15c5e9ed972ef89
commit: 2f06f18d080955b07c05cb2792708250f1f522e4 [43/61] usb: gadget: add some
infracture to register/unregister functions
config: make ARCH=x86_64 allmodconfig
Note: the
On Friday 18 January 2013 16:36:29 kishon wrote:
Bus 001 Device 004: ID 152d:2509 JMicron Technology Corp. / JMicron
USA Technology Corp. JMS539 SuperSpeed SATA II 3.0G Bridge
Device Descriptor:
You are connecting to the wrong port.
Try connecting to bus2 which seems to have usb3.
Bus
Hi,
On Friday 18 January 2013 05:29 PM, Felipe Balbi wrote:
Hi,
On Fri, Jan 18, 2013 at 03:10:42PM +0530, Kishon Vijay Abraham I wrote:
Added a new driver for the usb part of control module. This has an API
to power on the USB2 phy and an API to write to the mailbox depending on
whether MUSB
On Fri, Jan 18, 2013 at 10:50:28AM +0800, Peter Chen wrote:
+#ifdef CONFIG_PM
+static int ci13xxx_imx_suspend(struct device *dev)
+{
+ struct ci13xxx_imx_data *data =
+ platform_get_drvdata(to_platform_device(dev));
Is there a reason not to use dev_get_drvdata() here?
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
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 rog...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
---
We don't need multiple aliases for the OMAP USB host clocks and neither
the dummy clocks so remove them.
CC: Paul Walmsley p...@pwsan.com
CC: Rajendra Nayak rna...@ti.com
CC: Benoit Cousson b-cous...@ti.com
CC: Mike Turquette mturque...@linaro.com
Signed-off-by: Roger Quadros rog...@ti.com
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 rog...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
---
drivers/mfd/omap-usb-host.c | 16
1 files changed, 0 insertions(+), 16 deletions(-)
diff
Enable the optional HSIC clocks (60MHz and 480MHz) for the ports
that are configured in HSIC mode.
Signed-off-by: Roger Quadros rog...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
---
drivers/mfd/omap-usb-host.c | 97 --
1 files changed, 83
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 rog...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
---
drivers/mfd/omap-usb-tll.c | 15 +--
1 files changed, 5 insertions(+),
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 rog...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
---
drivers/mfd/omap-usb-host.c | 10 --
1 files changed, 0
Use devm_ variants of kzalloc and ioremap. Also clean up error path.
Signed-off-by: Roger Quadros rog...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
---
drivers/mfd/omap-usb-host.c | 38 +++---
1 files changed, 11 insertions(+), 27 deletions(-)
diff --git
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 rog...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
---
drivers/mfd/omap-usb-tll.c | 14 ++
1 files changed, 14 insertions(+), 0 deletions(-)
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.
Without this patch, EHCI will break on repeated insmod/rmmod
of ehci_hcd for all OMAP2+ platforms that use EHCI and
set 'phy_reset = true' in
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.
CC:
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 rog...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
---
drivers/mfd/omap-usb-tll.c | 53
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 rog...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
---
drivers/mfd/omap-usb-tll.c | 20
1 files changed, 12
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
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
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 rog...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
---
drivers/mfd/omap-usb-tll.c | 20
Use devm_ variants of kzalloc() and ioremap(). Simplify the error path.
Signed-off-by: Roger Quadros rog...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
---
drivers/mfd/omap-usb-tll.c | 38 --
1 files changed, 12 insertions(+), 26 deletions(-)
diff --git
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
On 01/18/2013 02:17 PM, Roger Quadros wrote:
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.
Without this patch, EHCI will break on repeated insmod/rmmod
of ehci_hcd for all OMAP2+ platforms that use
On Fri, Jan 18, 2013 at 4:53 PM, Petko Manolov pet...@nucleusys.com wrote:
The code in the driver is based on the specs from ADMTek (later, Infineon).
Since i never suspend my machines this feature has not been tested by me.
However, if the proposed patch is the right thing to do i'd be happy
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 gautam.vi...@samsung.com
Acked-by: Jingoo Han jg1@samsung.com
Missing
Hi,
On Mon, Jan 14, 2013 at 05:52:15PM +0530, Vivek Gautam wrote:
This patch adds host phy support to samsung-usbphy driver and
further adds support for samsung's exynos5250 usb-phy.
Signed-off-by: Praveen Paneri p.pan...@samsung.com
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
On 01/17/2013 06:10 PM, Alan Stern wrote:
On Thu, 17 Jan 2013, Roger Quadros wrote:
Alan,
What tree is your patch based off?
Roughly speaking, 3.7 plus Greg KH's usb-next branch as of the 3.7
release. This should be pretty much the same as 3.8-rc1 as far as the
USB stack is concerned.
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 ba...@ti.com wrote:
Hi,
On Mon, Jan 14, 2013 at 05:52:15PM +0530, Vivek Gautam wrote:
This patch adds host phy support to samsung-usbphy driver and
further adds
Add device driver for USB2CAN interface from 8 devices
(http://www.8devices.com).
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 sysfs documentation
* fix minor
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 by looking at the Interface
Association Descriptor instead.
HI Balbi,
On Fri, Jan 18, 2013 at 7:52 PM, Felipe Balbi ba...@ti.com 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 ba...@ti.com wrote:
Hi,
On Mon, Jan 14, 2013 at 05:52:15PM +0530, Vivek Gautam wrote:
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 can2: Unknown
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 allocate
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 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) {
+ret =
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 ba...@ti.com 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 ba...@ti.com wrote:
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, 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 vbyravar...@nvidia.com
---
delta from v2:
Renamed USB_PORTSC1 to TEGRA_USB_PORTSC1.
Removed tegra_ehci_set_wakeon_events() and its
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 gautam.vi...@samsung.com
Acked-by: Jingoo Han jg1@samsung.com
Acked-by: Alan Stern
On Fri, 18 Jan 2013, Vivek Gautam wrote:
Hi Alan,
On Fri, Jan 18, 2013 at 6:46 PM, Felipe Balbi ba...@ti.com 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
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
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 the
On Thu, 17 Jan 2013, Bjørn Mork wrote:
Peter Stuge pe...@stuge.se 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 it's
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 default, because it
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
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
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 tianyu@intel.com
---
drivers/usb/host/xhci-mem.c | 36
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
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 vbyravar...@nvidia.com
---
delta from v2:
Renamed USB_PORTSC1 to TEGRA_USB_PORTSC1.
Removed
On Mon, 14 Jan 2013 12:23:05 -0800
Greg KH gre...@linuxfoundation.org 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
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.
Signed-off-by:
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 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 info
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 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
[ 122.523468]
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.
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 now
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 by
From: Lucas Stach d...@lynxeye.de
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 d...@lynxeye.de
Applied.
--
To unsubscribe from this
From: Lucas Stach d...@lynxeye.de
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().
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 ba...@ti.com
---
Hi Greg, would you take the patch below to debugfs ? I don't think debugfs
should ever change whatever's
From: Freddy Xin fre...@asix.com.tw
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 |
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
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
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 message
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 of
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?
Note
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
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 series
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 wondered if
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 agreement with
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 must
1 - 100 of 132 matches
Mail list logo
