On 2012年12月13日 04:28, Frank Schäfer wrote:
Am 12.12.2012 09:23, schrieb Lan Tianyu:
On 2012年12月12日 05:59, Frank Schäfer wrote:
Am 11.12.2012 17:48, schrieb Alan Stern:
[snip]
We really need to know which component is bad: the host controller or
the device.
It happens with all USB 1.1
On 12/12/2012 07:34 PM, Alan Stern wrote:
Okay. Then how about this: Unplug both the power connector and the
slave connector. After the N7 goes into deep sleep, plug the power
connector back in but leave the slave unplugged. Then a few seconds
later, plug in the slave.
This always fails
On 12/11/2012 06:57 PM, Bernd Krumboeck wrote:
Add device driver for USB2CAN interface from 8 devices
(http://www.8devices.com).
changes since v5:
* unlock mutex on error
changes since v4:
* removed FSF address
* renamed struct usb_8dev
* removed unused variable free_slots
* replaced
Hi,
On Wed, Dec 12, 2012 at 10:13:27PM +0100, Linus Walleij wrote:
On Tue, Nov 27, 2012 at 3:11 PM, Linus Walleij linus.wall...@linaro.org
wrote:
On Wed, Nov 21, 2012 at 3:33 PM, Linus Walleij linus.wall...@linaro.org
wrote:
On Wed, Nov 14, 2012 at 3:40 PM, Linus Walleij
Hi Samuel Felipe,
How can we proceed with this patchset?
You can use the below pull request.
The following changes since commit 47f46768d3a3866bff7164649dab499bf5d8ed81:
Merge branch 'next/soc' into for-next (2012-12-07 16:35:14 -0800)
are available in the git repository at:
Hi,
On Thu, Dec 13, 2012 at 12:44:22PM +0200, Roger Quadros wrote:
Hi Samuel Felipe,
How can we proceed with this patchset?
You can use the below pull request.
there are patches under arch/arm/ which need Tony's Acked-by, if we get
those, then sure, go ahead ;-)
--
balbi
On Wed, Dec 05, 2012 at 04:13:46PM +0200, Roger Quadros wrote:
On 12/05/2012 03:42 PM, Sergei Shtylyov wrote:
Hello.
On 04-12-2012 18:31, Roger Quadros wrote:
clk_set_parent is expected to fail on OMAP3 platforms. We don't
consider that as fatal so don't spam console.
On 5 December 2012 19:43, Roger Quadros rog...@ti.com wrote:
On 12/05/2012 03:42 PM, Sergei Shtylyov wrote:
Hello.
On 04-12-2012 18:31, Roger Quadros wrote:
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
we have an extra 'ret' variable shadowing a previous
definition. Remove it.
Signed-off-by: Felipe Balbi ba...@ti.com
---
alredy in my branch, will be sent for v3.9 merge window.
drivers/usb/dwc3/gadget.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/usb/dwc3/gadget.c
In the IN case, since the USB request is allocated only when
the source/sink function is started and never freed, the USB ept
buffer needs to be inited only at the beginning. This change
results into a more performant g_zero module, especially when
'pattern=1' is selected.
Signed-off-by: Armando
Using chip specific compatible string as it should be.
So fixing this for ehci-s5p, ohci-exynos and dwc3-exynos
which till now used a generic 'exynos' in their compatible strings.
This goes as per the discussion happened in the thread for
[PATCH v2] ARM: Exynos5250: Enabling dwc3-exynos driver
Using specific chip in compatible strings. Newer SOCs can claim
device by using older string in the compatible list.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
drivers/usb/host/ehci-s5p.c|2 +-
drivers/usb/host/ohci-exynos.c |2 +-
2 files changed, 2 insertions(+), 2
Using specific chip in compatible strings. Newer SOCs can claim
device by using older string in the compatible list.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
drivers/usb/dwc3/dwc3-exynos.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
On Thu, 13 Dec 2012, Timur wrote:
On 12/12/2012 07:34 PM, Alan Stern wrote:
Okay. Then how about this: Unplug both the power connector and the
slave connector. After the N7 goes into deep sleep, plug the power
connector back in but leave the slave unplugged. Then a few seconds
Hi Greg,
Here's my first set of fixes for this -rc cycle. Let me
know if you want any changes to this pull request.
I'm basing it off of Linus' current master as there are no
tags yet. If you want to wait until -rc1 is tagged, I can easily
rebase.
cheers
The following changes since commit
Am 13.12.2012 09:45, schrieb Lan Tianyu:
[snip]
I am curious about whether disabling usb device's wakeup rather than usb
hc's would make suspend work. Can you do a test?
Go to /sys/bus/usb/devices/ and enter the usb 1,1 device
directory(normally it will be something like1-1.1.)
run echo
On Thu, 13 Dec 2012, Frank Schäfer wrote:
I write a quirk patch. Can you test?
Yes, that makes it work !
I just find one MCP51 and two MCP79 OHCI id. Can you provide more buggy
hcd id via lspci -nnvvv?
Thanks.
I have the MCP61 (rev. A2) with id 10de:03f1.
Further NVIDIA OHCI
CC: LKML
On Thu, Dec 13, 2012 at 8:22 PM, Vivek Gautam gautam.vi...@samsung.com wrote:
Using chip specific compatible string as it should be.
So fixing this for ehci-s5p, ohci-exynos and dwc3-exynos
which till now used a generic 'exynos' in their compatible strings.
This goes as per the
On Thu, Dec 13, 2012 at 8:22 PM, Vivek Gautam gautam.vi...@samsung.com wrote:
Using specific chip in compatible strings. Newer SOCs can claim
device by using older string in the compatible list.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
drivers/usb/host/ehci-s5p.c|2
Changes from v2:
- Changed the compatible string to chip specific(samsung,exynos4210),
since ehci-s5p and ohci-exynos are being used from exynso4210 onwards.
- Based on changes for drivers available at:
http://www.mail-archive.com/devicetree-discuss@lists.ozlabs.org/msg23218.html
Changes
Adding EHCI device tree node for Exynos5250 along with
the device base adress and gpio line for vbus.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Acked-by: Jingoo Han jg1@samsung.com
---
.../devicetree/bindings/usb/exynos-usb.txt | 25
Adding OHCI device tree node for Exynos5250 along with
the device base address.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Acked-by: Jingoo Han jg1@samsung.com
---
.../devicetree/bindings/usb/exynos-usb.txt | 15 +++
arch/arm/boot/dts/exynos5250.dtsi
Adding DWC3 device tree node for Exynos5250 along with the
device address and clock support needed for the controller.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
Changes from v2:
- Changed the compatible string to chip specific(samsung,exynos5250),
since dwc3-exynos is being
On Wed, Dec 12, 2012 at 9:11 PM, Alan Stern st...@rowland.harvard.edu wrote:
That's the error code returned by the USB stack when a request is
cancelled synchronously. But it is intended for internal kernel use
only; it should not appear at the userspace level. Without knowing the
details of
On Wed, Dec 12, 2012 at 9:11 PM, Alan Stern st...@rowland.harvard.edu wrote:
That's the error code returned by the USB stack when a request is
cancelled synchronously. But it is intended for internal kernel use
only; it should not appear at the userspace level. Without knowing the
details of
On Thu, 13 Dec 2012, prasannatsmkumar wrote:
On Wed, Dec 12, 2012 at 2:07 AM, Alan Stern st...@rowland.harvard.edu wrote:
STOP UNIT means spin down the disk or eject the disc. Since your phone
doesn't have a disk drive or an optical disc, no wonder this step
failed.
Yes of course it
On Thu, Dec 13, 2012 at 11:40 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Thu, 13 Dec 2012, prasannatsmkumar wrote:
On Wed, Dec 12, 2012 at 2:07 AM, Alan Stern st...@rowland.harvard.edu
wrote:
STOP UNIT means spin down the disk or eject the disc. Since your phone
doesn't have a
Add device driver for USB2CAN interface from 8 devices
(http://www.8devices.com).
changes since v6:
* changed some variable types to big endian equivalent
* small cleanups
changes since v5:
* unlock mutex on error
changes since v4:
* removed FSF address
* renamed struct usb_8dev
* removed
On Thu, Dec 13, 2012 at 04:58:36PM +0200, Felipe Balbi wrote:
Hi Greg,
Here's my first set of fixes for this -rc cycle. Let me
know if you want any changes to this pull request.
I'm basing it off of Linus' current master as there are no
tags yet. If you want to wait until -rc1 is tagged,
On Thu, Dec 13, 2012 at 10:50:39AM -0800, Greg KH wrote:
On Thu, Dec 13, 2012 at 04:58:36PM +0200, Felipe Balbi wrote:
Hi Greg,
Here's my first set of fixes for this -rc cycle. Let me
know if you want any changes to this pull request.
I'm basing it off of Linus' current master as
On Thu, 13 Dec 2012 07:35:55 -0800, Frank Schäfer
fschaefer@googlemail.com wrote:
I write a quirk patch. Can you test?
Yes, that makes it work !
I just find one MCP51 and two MCP79 OHCI id. Can you provide more buggy
hcd id via lspci -nnvvv?
Thanks.
I have the MCP61 (rev. A2) with id
On Wed, Dec 12, 2012 at 10:32:05AM +0800, Huang Ying wrote:
Please try the patch attached. With it, USB host controller can be
waken up with USB card reader plugging in on my test machine.
This patch works for me. When I enable runtime PM for both the root port
and the host controller, and I
Hello,
I'm having a problem with a Digi Inside Out Networks Edgeport/416
device. According to the kernel.org file (see exerpt below) this
particular model is not listed in the supported products. Is this info
still valid?
The device is connected to a 32 bit CentOS 6.3 machine running with
kernel
Hi Samuel,
* Roger Quadros rog...@ti.com [121210 02:23]:
Instead of using cpu_is_omap..() macros in the device driver we
rely on information provided in the platform data.
The only information we need is whether the USB Host module has
a single ULPI bypass control bit for all ports or
Hi Tony,
On Thu, Dec 13, 2012 at 01:49:49PM -0800, Tony Lindgren wrote:
Hi Samuel,
* Roger Quadros rog...@ti.com [121210 02:23]:
Instead of using cpu_is_omap..() macros in the device driver we
rely on information provided in the platform data.
The only information we need is whether
On 2012年12月13日 23:47, Alan Stern wrote:
On Thu, 13 Dec 2012, Frank Schäfer wrote:
I write a quirk patch. Can you test?
Yes, that makes it work !
I just find one MCP51 and two MCP79 OHCI id. Can you provide more buggy
hcd id via lspci -nnvvv?
Thanks.
I have the MCP61 (rev. A2) with id
On 2012年12月13日 23:35, Frank Schäfer wrote:
Am 13.12.2012 09:45, schrieb Lan Tianyu:
[snip]
I am curious about whether disabling usb device's wakeup rather than usb
hc's would make suspend work. Can you do a test?
Go to /sys/bus/usb/devices/ and enter the usb 1,1 device
directory(normally
From: fangxiaozhi huana...@huawei.com
1. Add a new macro define for USB storage match rule.
2. Optimize the match rules with new macro for Huawei USB storage devices,
to avoid to load USB storage driver for the modem interface
with Huawei devices.
3. Add to support new switch command for
Hi,
Alan Stern st...@rowland.harvard.edu writes:
If you read the confidentiality notice, you'll see that it merely
says that the contents of the email _may_ be confidential. Also, it
warns people who _aren't_ the intended addressees -- but if the
message was sent to a public
Hi,
# ls /dev/mmc*
/dev/mmc0 /dev/mmc2 /dev/mmcblk0p1
/dev/mmc1 /dev/mmcblk0/dev/mmcblk0p2
# mount /dev/mmcblk0 /mnt
# ls /mnt/
initramfs.gz
# umount /mnt
umounting 1
umounting 0
# insmod kagen2_udc.ko
# insmod
On Fri, Dec 14, 2012 at 12:49 AM, Alan Stern st...@rowland.harvard.edu wrote:
On Thu, 13 Dec 2012, prasannatsmkumar wrote:
On Thu, Dec 13, 2012 at 11:40 PM, Alan Stern st...@rowland.harvard.edu
wrote:
On Thu, 13 Dec 2012, prasannatsmkumar wrote:
On Wed, Dec 12, 2012 at 2:07 AM, Alan
Tegra USB host driver is using port instance number,
to handle some of the hardware issues on SOC e.g. reset PORT0
twice etc. As instance number based handling looks ugly,
added a new property to USB DT node for this purpose.
Modified host driver to make use of the information passed
through DT to
As Tegra USB host driver is using instance number for resetting
PORT0 twice, adding a new DT property for handling this.
Signed-off-by: Venu Byravarasu vbyravar...@nvidia.com
---
.../bindings/usb/nvidia,tegra20-ehci.txt |2 ++
arch/arm/boot/dts/tegra20.dtsi |
Tegra USB host driver is using port instance number,
to handle some of the hardware issues on SOC e.g. reset PORT0
twice etc. As instance number based handling looks ugly,
making use of information passed through DT for achieving this.
Signed-off-by: Venu Byravarasu vbyravar...@nvidia.com
---
Hi,
If you read the confidentiality notice, you'll see that it
merely says that the contents of the email _may_ be
confidential. Also, it warns people who _aren't_ the intended
addressees -- but if the message was sent to a public email list
then obviously there are no
45 matches
Mail list logo
