On Thu, Sep 20, 2012 at 03:56:56PM +, Arnd Bergmann wrote:
> Ok, fair enough. I think we can put it in arm-soc/for-next as a staging
> branch anyway to give it some exposure to linux-next, and then we can
> decide whether a rebase is necessary before sending it to Linus.
>
I just saw the annou
On Fri, Sep 21, 2012 at 1:01 AM, Shawn Guo wrote:
> On Thu, Sep 20, 2012 at 03:56:56PM +, Arnd Bergmann wrote:
>> Ok, fair enough. I think we can put it in arm-soc/for-next as a staging
>> branch anyway to give it some exposure to linux-next, and then we can
>> decide whether a rebase is neces
Hi,
here is the patch that does everything I consider theoretically necessary
to have bundling of frames in usbnet and adapting cdc-ncm to it.
I'd appreciate any review in case I am doing something stupid.
Regards
Oliver
diff --git a/drivers/net/usb/cdc_ncm.c b/drivers/n
This series moves some of the misplaced ARM header files, which
contain driver platform data, out of arch/arm/include/asm/mach
and into include/linux/platform_data.
arch/arm/include/asm/mach is supposed to be for include files
exporting generic ARM code structures and functions to ARM platforms,
n
This is really driver platform data, so move it to the appropriate
directory.
Signed-off-by: Russell King
---
arch/arm/include/asm/mach/serial_sa1100.h | 31 -
arch/arm/mach-sa1100/assabet.c |2 +-
arch/arm/mach-sa1100/badge4.c |2 +-
Move the PXA2xx/IXP4xx UDC header file into linux/platform_data as it
only contains a driver platform data structure.
Signed-off-by: Russell King
---
arch/arm/include/asm/mach/udc_pxa2xx.h | 26 --
arch/arm/mach-ixp4xx/include/mach/udc.h |2 +-
arch/arm/mach-pxa/
The definitions provided by serial_at91.h are only used by the
atmel_serial driver, and the function that uses it is never called
from anywhere in the kernel. Therefore, these definitions are unused
and/or obsolete, and can be removed.
Signed-off-by: Russell King
---
arch/arm/include/asm/mach/s
On Fri, Sep 21, 2012 at 5:36 PM, Russell King
wrote:
> Move the PXA2xx/IXP4xx UDC header file into linux/platform_data as it
> only contains a driver platform data structure.
>
> Signed-off-by: Russell King
> ---
> arch/arm/include/asm/mach/udc_pxa2xx.h | 26 --
> arc
Hi,
On Thu, Sep 20, 2012 at 05:32:36PM +0530, Venu Byravarasu wrote:
> Thanks Greg, for quick response.
I'm waiting for a newer version fixing Kishon's comments. BTW, his
comment about pdata usage is 100% valid. You should fix that.
--
balbi
signature.asc
Description: Digital signature
On Fri, Sep 21, 2012 at 10:36:27AM +0100, Russell King wrote:
> Move the PXA2xx/IXP4xx UDC header file into linux/platform_data as it
> only contains a driver platform data structure.
>
> Signed-off-by: Russell King
after fixing Eric's comment:
Acked-by: Felipe Balbi
> ---
> arch/arm/include
On Fri, Sep 21, 2012 at 05:40:07PM +0800, Eric Miao wrote:
> On Fri, Sep 21, 2012 at 5:36 PM, Russell King
> wrote:
> > diff --git a/arch/arm/mach-ixp4xx/include/mach/udc.h
> > b/arch/arm/mach-ixp4xx/include/mach/udc.h
> > index 80d6da2..b47cc0d 100644
> > --- a/arch/arm/mach-ixp4xx/include/mach/
> -Original Message-
> From: Felipe Balbi [mailto:ba...@ti.com]
> Sent: Friday, September 21, 2012 3:07 PM
> To: Venu Byravarasu
> Cc: gre...@linuxfoundation.org; ba...@ti.com; Stephen Warren; linux-
> ker...@vger.kernel.org; linux-usb@vger.kernel.org; linux-
> te...@vger.kernel.org; Stephe
On 09/20/2012 07:06 AM, Olivier Sobrie wrote:
> This driver provides support for several Kvaser CAN/USB devices.
> Such kind of devices supports up to three CAN network interfaces.
>
> It has been tested with a Kvaser USB Leaf Light (one network interface)
> connected to a pch_can interface.
> The
On Fri, Sep 21, 2012 at 12:49 AM, Alan Stern wrote:
>
> The results will be more impressive if you plug three of the hubs
> directly into the fourth and attach the fourth hub to the computer.
See all the logs in the below link for the test case above.
http://kernel.ubuntu.com/~ming/ke
On Fri, Sep 21 2012, Leo Song wrote:
> If connect an UMS device (for example, an Android phone) to Linux PC and
> Windows PC, then copy a big file (~500MB) to the device, you will find that
> Linux PC's write speed is much faster than Windows PC. This issue can be fixed
> by hiding the "caching mod
>-Original Message-
>From: Michal Nazarewicz [mailto:m...@google.com] On Behalf Of Michal
>Nazarewicz
>Sent: 2012年9月21日 19:23
>To: Leo Song; Felipe Balbi; linux-usb@vger.kernel.org
>Cc: Leo Song
>Subject: Re: [PATCH] USB: g_mass_storage: Hide caching mode page to improve
>write speed for Wi
NVIDIA produces several Tegra SoCs viz Tegra20, Tegra30 etc.
In order to support USB PHY drivers on these SoCs, existing
PHY driver is split into SoC agnostic common USB PHY driver
and Tegra20-specific USB phy driver. This will facilitate
easy addition and deletion of phy drivers for Tegra SoCs.
S
Hi,
On Fri, Sep 21, 2012 at 5:50 PM, Venu Byravarasu wrote:
> NVIDIA produces several Tegra SoCs viz Tegra20, Tegra30 etc.
> In order to support USB PHY drivers on these SoCs, existing
> PHY driver is split into SoC agnostic common USB PHY driver
> and Tegra20-specific USB phy driver. This will f
> Michal Nazarewicz:
>> How does it interact with the nofua attribute? With f_mass_storage,
>> you can write 1 to nofua file in sysfs's directory for given lun to
>> make it ignore the FUA bit.
On Fri, Sep 21 2012, Leo Song wrote:
> Actually this patch does not interact with the nofua attribute
>
Apologies, this is my first ever upstream report. I hope I did alright
by whoever gets this.
-
0711:5100 sisusbvga driver not working with StarTech USB2VGAE2
Along with the bug posted at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/517934
I am not able to use this device. I have not
On Fri, 21 Sep 2012, Ming Lei wrote:
> >> IMO, suppose it is a problem, we should try to use 0 to make it
> >> working because 'lsusb' is just a tool which isn't involved into actual
> >> hub function.
> >>
> >> I will try to study 'lsusb' to see if there is one problem and try to
> >> solve it.
On Fri, 21 Sep 2012, Ming Lei wrote:
> On Fri, Sep 21, 2012 at 1:04 AM, Alan Stern wrote:
> >
> > I vaguely remember seeing this same effect with one of my hubs. If a
> > port status change occurred before the hub was suspended, the hub would
> > not issue a remote wakeup request. This was a bu
On Fri, Sep 21, 2012 at 11:53 PM, Alan Stern wrote:
> The hub will also be resumed when a child is accessed via libusb, and
> suspended when the child is released. As a result, the hub gets
> suspended and resumed multiple times: once for itself and once for each
> descendant. If the autosuspen
On Fri, 21 Sep 2012, Ming Lei wrote:
> On Fri, Sep 21, 2012 at 12:49 AM, Alan Stern
> wrote:
> >
> > The results will be more impressive if you plug three of the hubs
> > directly into the fourth and attach the fourth hub to the computer.
>
> See all the logs in the below link for the test case
DMA_ADDR_INVALID is used by the UDC driver and the gadgets should
provide only a buffer address. Everything else should be taken core of
by the UDC and udc-core.
Signed-off-by: Sebastian Andrzej Siewior
---
drivers/usb/gadget/f_uac2.c |3 ---
drivers/usb/gadget/inode.c |3 ---
2 files c
There is no need for this variable in between.
Signed-off-by: Sebastian Andrzej Siewior
---
drivers/usb/gadget/f_uac2.c | 30 ++
1 file changed, 10 insertions(+), 20 deletions(-)
diff --git a/drivers/usb/gadget/f_uac2.c b/drivers/usb/gadget/f_uac2.c
index 503dd97..
This patch does two things actually:
- It removes the conditional allocation of string ids. This check is not
required because bind is called only once at modprobe time. So we
never can optimize this one away.
- Instead of calling usb_string_id() multiple times I replace it with
one usb_strin
This patch removes the shifting and masking of interface and its alt
setting and provides its own variable.
This looks better and is smaller:
textdata bss dec hex filename
x86-32
6940 956 5679521f10 gadget/audio.o.old
6908 956 5679201ef0 gadget/a
On 09/21/2012 07:09 AM, ABRAHAM, KISHON VIJAY wrote:
> Hi,
>
> On Fri, Sep 21, 2012 at 5:50 PM, Venu Byravarasu
> wrote:
>> NVIDIA produces several Tegra SoCs viz Tegra20, Tegra30 etc.
>> In order to support USB PHY drivers on these SoCs, existing
>> PHY driver is split into SoC agnostic common
On Sat, Sep 22, 2012 at 12:07 AM, Alan Stern wrote:
> On Fri, 21 Sep 2012, Ming Lei wrote:
>
>> On Fri, Sep 21, 2012 at 12:49 AM, Alan Stern
>> wrote:
>> >
>> > The results will be more impressive if you plug three of the hubs
>> > directly into the fourth and attach the fourth hub to the comput
On Fri, Sep 21, 2012 at 11:55 PM, Alan Stern wrote:
> On Fri, 21 Sep 2012, Ming Lei wrote:
>
>> On Fri, Sep 21, 2012 at 1:04 AM, Alan Stern
>> wrote:
>> >
>> > I vaguely remember seeing this same effect with one of my hubs. If a
>> > port status change occurred before the hub was suspended, the
Hi Olof,
On Fri, Sep 21, 2012 at 01:26:43AM -0700, Olof Johansson wrote:
> I'll take a look at merging it tomorrow after I've dealt with smp_ops;
> if it looks reasonably conflict-free I'll pull it in. We need the
> sound dependency sorted out (or agreed upon) first though.
>
I just published the
On Sat, Sep 22, 2012 at 12:46:26AM +0800, Shawn Guo wrote:
> I just published the branch below with this series rebased on top of
> the necessary dependant branches.
>
> git://git.linaro.org/people/shawnguo/linux-2.6.git staging/imx-multiplatform
>
> The dependant branches include:
>
Forgot t
From: Bjørn Mork
Date: Thu, 20 Sep 2012 09:18:05 +0200
> This is the net-next version of the previously posted patch with the
> same title. I totally forgot that I had messed with the .driver_info
> fields, making it impossible to apply the same patch to both net and
> net-next.
>
> Sorry abou
On Fri, Sep 21, 2012 at 11:16:01AM +0800, Lan Tianyu wrote:
> On 2012年09月21日 08:25, Sarah Sharp wrote:
> > Hi Tianyu,
> >
> > You're correct that the USB core and the xHCI driver has a slightly
> > different architecture than the ACPI representation. We have one PCI
> > device that has two USB bu
Applied.
thanks,
Len Brown, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On 09/21/2012 06:20 AM, Venu Byravarasu wrote:
> NVIDIA produces several Tegra SoCs viz Tegra20, Tegra30 etc.
> In order to support USB PHY drivers on these SoCs, existing
> PHY driver is split into SoC agnostic common USB PHY driver
> and Tegra20-specific USB phy driver. This will facilitate
> eas
On Fri, Sep 21, 2012 at 11:36:37AM +0800, Lan Tianyu wrote:
> On 2012年09月21日 09:52, Peter Chen wrote:
> >>
> >> Where I would like to see this work go is to have a certain set of
> >> "safe" internal USB devices be powered off by default when they are
> >> suspended. I think fingerprint readers an
On Fri, 21 Sep 2012, Leo Song wrote:
> If connect an UMS device (for example, an Android phone) to Linux PC and
> Windows PC, then copy a big file (~500MB) to the device, you will find that
> Linux PC's write speed is much faster than Windows PC. This issue can be fixed
> by hiding the "caching mo
On Fri, 21 Sep 2012, Leo Song wrote:
> Actually this patch does not interact with the nofua attribute
> directly. The original code will let Windows PC go into a confused
What's confused about it?
> state, and Windows will always send WRITE COMMAND with FUA=1. If
> manually "echo 1 > ./f_mass_st
Hi,
Sarah Sharp wrote:
> Two weeks ago at Linux Plumbers Conference, I presented about the
> Intel Lynx Point USB port power off mechanism.
Good session with some participation, thanks to all!
> The end result of those patches is that we expose a sysfs file per USB
> port to userspace to allow
Sarah Sharp wrote:
> a userspace program claims the interface via usbfs and reads from
> the device when it wants to capture a finger scan. The kernel's
> "auto" power policy would turn back on the port as soon as the
> interface was claimed through usbfs.
This translates to a slightly less appea
On Sat, 22 Sep 2012, Ming Lei wrote:
> On Fri, Sep 21, 2012 at 11:53 PM, Alan Stern
> wrote:
>
> > The hub will also be resumed when a child is accessed via libusb, and
> > suspended when the child is released. As a result, the hub gets
> > suspended and resumed multiple times: once for itself
On Fri, 21 Sep 2012, Sebastian Andrzej Siewior wrote:
> DMA_ADDR_INVALID is used by the UDC driver and the gadgets should
> provide only a buffer address. Everything else should be taken core of
> by the UDC and udc-core.
>
> Signed-off-by: Sebastian Andrzej Siewior
> ---
> drivers/usb/gadget/f
On Sat, 22 Sep 2012, Ming Lei wrote:
> > So your patch does not fix the problem, although it does make the
> > problem less likely to occur.
>
> Exactly.
>
> Considered that runtime suspend may be often happened on hub devices,
> and status endpoint interval is about 256ms which should be a bit
On Fri, Sep 21, 2012 at 08:21:01PM +0200, Peter Stuge wrote:
> Sarah Sharp wrote:
> > a userspace program claims the interface via usbfs and reads from
> > the device when it wants to capture a finger scan. The kernel's
> > "auto" power policy would turn back on the port as soon as the
> > interfa
On Fri, Sep 21, 2012 at 08:18:21PM +0200, Peter Stuge wrote:
> Hi,
>
> Sarah Sharp wrote:
> > Two weeks ago at Linux Plumbers Conference, I presented about the
> > Intel Lynx Point USB port power off mechanism.
>
> Good session with some participation, thanks to all!
>
>
> > The end result of t
On Fri, 21 Sep 2012, Anthony Hook wrote:
> Apologies, this is my first ever upstream report. I hope I did alright
> by whoever gets this.
> -
> 0711:5100 sisusbvga driver not working with StarTech USB2VGAE2
>
> Along with the bug posted at:
>
> https://bugs.launchpad.net/ubuntu/+source/linux
Sarah Sharp wrote:
> > How will userspace know why powering off the port does not work?
>
> We can expose the power resources in sysfs, so userspace can figure out
> which ports are under which power resources.
Sorry, I should have clarified.
> If userspace really wants the port off (e.g. to di
On Wed, Sep 19, 2012 at 05:02:29PM -0400, Alan Stern wrote:
> This patch (as1606) converts two warning messages in the ehci-hcd
> driver to debug messages, and adds a little extra information to each.
>
> The log messages occur when an EHCI controller takes too long (more
> than 20 ms) to turn its
On Tue, Sep 18, 2012 at 04:52:39PM +0800, Shengzhou Liu wrote:
> when missing USB PHY clock, kernel booting up will hang during USB
> initialization. We should check USBGP[PHY_CLK_VALID] bit to avoid
> CPU hanging in this case.
>
> Signed-off-by: Shengzhou Liu
> ---
> v3 change: no check for UTMI
On Sat, Sep 08, 2012 at 04:26:37PM -0500, Caylan Larson wrote:
> Hi,
>
> I have three, 4-port USB-to-Serial adapters connected to a Linux
> system running kernel 3.3.7-1. These three adapters are connected to
> the system via a USB hub. The application is a DOS app (point of sale
> system), runn
On Thu, 20 Sep 2012, Sarah Sharp wrote:
> Two weeks ago at Linux Plumbers Conference, I presented about the Intel
> Lynx Point USB port power off mechanism. This email is a report out of
> what was discussed, and a kick off point for further discussion.
> - Len Brown mentioned that it's likely
On Fri, Sep 21, 2012 at 08:54:38PM +0200, Peter Stuge wrote:
> Sarah Sharp wrote:
> > > How will userspace know why powering off the port does not work?
> >
> > We can expose the power resources in sysfs, so userspace can figure out
> > which ports are under which power resources.
>
> Sorry, I sh
On Thu, 20 Sep 2012, Gian-Carlo Pascutto wrote:
> On 19/09/12 21:00, Alan Stern wrote:
>
> > It would be good if you could determine for certain which device has
> > the problem. Maybe run some tests where you use only the headset or
> > only the webcam.
>
> I spent time trying to reproduce p
On Fri, 21 Sep 2012, Sarah Sharp wrote:
> > > If userspace really wants the port off (e.g. to disconnect and
> > > reconnect a misbehaving device), then it can set the sysfs file
> > > to off.
> >
> > And unless all ganged ports are also off it will fail. Userspace will
> > want to know about tha
Sarah Sharp wrote:
> > > If userspace really wants the port off (e.g. to disconnect and
> > > reconnect a misbehaving device), then it can set the sysfs file
> > > to off.
> >
> > And unless all ganged ports are also off it will fail. Userspace will
> > want to know about that, and why, along with
On Fri, Sep 21, 2012 at 04:09:13PM -0400, Alan Stern wrote:
> On Thu, 20 Sep 2012, Sarah Sharp wrote:
>
> > Two weeks ago at Linux Plumbers Conference, I presented about the Intel
> > Lynx Point USB port power off mechanism. This email is a report out of
> > what was discussed, and a kick off poi
2012/9/6 Kishon Vijay Abraham I :
> All the PHY configuration other than VBUS, ID GND and OTG SRP are removed
> from twl6030. The phy configurations are taken care by the dedicated
> usb2 phy driver. So twl6030 is made as comparator driver for VBUS and
> ID detection.
>
> Signed-off-by: Kishon Vija
Hi Paul,
On Wed, Sep 19, 2012 at 08:39:40PM +, Paul Walmsley wrote:
>
> Hi Samuel,
>
> I've queued patch 1 of this series for 3.7, which should go upstream via
> the OMAP -> arm-soc path. Also asked Keshava to re-send patch 5 to me
> once patches 2-4 have been merged.
>
> It's up to you
On Fri, Sep 21, 2012 at 10:36:07AM +0100, Russell King wrote:
> This is really driver platform data, so move it to the appropriate
> directory.
>
> Signed-off-by: Russell King
Acked-by: Greg Kroah-Hartman
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a m
On Fri, Sep 21, 2012 at 10:36:27AM +0100, Russell King wrote:
> Move the PXA2xx/IXP4xx UDC header file into linux/platform_data as it
> only contains a driver platform data structure.
>
> Signed-off-by: Russell King
Acked-by: Greg Kroah-Hartman
--
To unsubscribe from this list: send the line "
On Fri, Sep 21, 2012 at 10:36:48AM +0100, Russell King wrote:
> The definitions provided by serial_at91.h are only used by the
> atmel_serial driver, and the function that uses it is never called
> from anywhere in the kernel. Therefore, these definitions are unused
> and/or obsolete, and can be r
Quoting Stephen Boyd (2012-09-20 19:26:48)
> This patchset moves the existing MSM clock code and affected drivers to the
> common clock framework. A prerequisite of moving to the common clock
> framework is to use clk_prepare() and clk_enable() so the first
> few patches migrate drivers to that cal
On Sat, Sep 22, 2012 at 2:28 AM, Alan Stern wrote:
> Can you check the port statuses only for buggy hubs? Or at least, only
> for those with Vendor ID = 0x05e3 (Genesys Logic)? Maybe introduce a
> bitflag for this quirk in the usb_hub structure.
OK, will do it.
Thanks,
--
Ming Lei
--
To unsub
On Sat, Sep 22, 2012 at 2:24 AM, Alan Stern wrote:
> Well, we can go ahead and try it. The main situation where it would
> matter would be if two connect or disconnect events occur in quick
> succession, and I admit this doesn't happen very often.
OK.
Also even wrt. the two quick connect or di
Hi,
Sorry for the late feedback but I didn't notice this until I looked at
the pull request from Jason.
Please go back and revisit these bindings. I'll merge in the current
version but they need to be fixed up.
Also, always cc devicetree-discuss and the DT maintainers on new bindings.
On Sat, S
67 matches
Mail list logo
