The patchset is based on the pm qos flags patches and now on
the linux-pm's next tree and pm-qos.
http://git.kernel.org/?p=linux/kernel/git/rafael/linux-pm.git;a=shortlog;h=refs/heads/pm-qos
usb: add usb port's pm qos flags request to change NO_POWER_OFF flag
usb: add runtime pm support for usb po
This patch is to register usb port's acpi power resources. Create
link between usb port device and its acpi power resource.
Signed-off-by: Lan Tianyu
---
drivers/usb/core/hub.c |3 ++-
drivers/usb/core/usb-acpi.c | 23 +++
drivers/usb/core/usb.h |6 ++
This patch is to add usb port auto power off mechanism.
When usb device is suspending, usb core will send clear usb port's
POWER feature requst to power off port if all conditions were met.
These conditions are remote wakeup enable, pm qos NO_POWER_OFF flags
and persist feature. When device is susp
This patch is to expose usb port's pm qos flags(pm_qos_no_power_off,
pm_qos_remote_wakeup) to user space. The pm_qos_no_power_off will
be used to control usb port auto power off mechanism from user space.
Signed-off-by: Lan Tianyu
---
drivers/usb/core/hub.c |9 +
1 file changed, 9 in
Some usb devices can't be resumed correctly after power off. This
patch is to add pm qos flags request to change NO_POWER_OFF and
provide usb_device_allow_power_off() for device drivers to allow or
prohibit usb core to power off the device.
Signed-off-by: Lan Tianyu
---
drivers/usb/core/hub.c |
When pm qos flags is changing, the pm core will keep device not
in RPM_SUSPEND via pm_runtime_get_sync/put(dev). When the flags are
changed, this will affect usb device status. If NO_POWER_OFF flag was
set when the device was power off, it would need to be resumed and
suspended again without power
Hello,
I'm using the Meego's MTP code on a TI8148 evaluation board (Inventra
HDRC Peripheral Controller). When connecting to Win7 it's detected as
Protable Device and I'm offered to open the explorer. But on WinXP it's
detected as Digital Camera and thus I am offered to open scan- and
image-e
Hi Felipe,
On Thu, Nov 8, 2012 at 8:30 PM, Felipe Balbi wrote:
> Hi,
>
> On Thu, Nov 08, 2012 at 08:07:57PM +0100, Dmytro Milinevskyy wrote:
>> > On Wed, Nov 07, 2012 at 02:14:00PM +0100, Dmytro Milinevskyy wrote:
>> >> Unfortunately I have some issues with git send-email.
>> >> I've attached the
On 11/9/2012 12:53 AM, Sergei Shtylyov wrote:
Look at this fragment of ehci-hub.c:
Thanks Sergei for pointing it out.
I apologize for the noise. SPEAr is also an EHCI implementation. Having
following code, actually we should not need this patch for SPEAr.
Regards
Pratyush
807
Hi,
On Fri, Nov 09, 2012 at 10:31:47AM +0100, Dmytro Milinevskyy wrote:
> Hi Felipe,
>
> On Thu, Nov 8, 2012 at 8:30 PM, Felipe Balbi wrote:
> > Hi,
> >
> > On Thu, Nov 08, 2012 at 08:07:57PM +0100, Dmytro Milinevskyy wrote:
> >> > On Wed, Nov 07, 2012 at 02:14:00PM +0100, Dmytro Milinevskyy wro
Hi,
On Tue, Oct 30, 2012 at 10:27:32AM +0530, Praveen Paneri wrote:
> Changes from v6:
> Modified register definitions according to the existing ones.
> Changed default PHY clk selection for SoCs.
> Improved binding text and rebased to the latest usb-next.
>
> Changes from v5:
> Moved clk_get() t
Hi Kukjin,
On Fri, Nov 9, 2012 at 5:24 PM, Felipe Balbi wrote:
> Hi,
>
> On Tue, Oct 30, 2012 at 10:27:32AM +0530, Praveen Paneri wrote:
>> Changes from v6:
>> Modified register definitions according to the existing ones.
>> Changed default PHY clk selection for SoCs.
>> Improved binding text and
Hello.
On 08-11-2012 22:48, Sergei Shtylyov wrote:
USB specs says that if an over-current is detected then a hub must switch off
all affected port, wait to cool down and then switch on.
There are few controllers, which does not follow it, and expects software
to switch off the port power.
On Fri, Nov 9, 2012 at 8:54 PM, Felipe Balbi wrote:
> Hi,
>
> On Tue, Oct 30, 2012 at 10:27:32AM +0530, Praveen Paneri wrote:
>> Changes from v6:
>> Modified register definitions according to the existing ones.
>> Changed default PHY clk selection for SoCs.
>> Improved binding text and rebased to
Hi,
On Fri, Nov 9, 2012 at 6:06 PM, Kyungmin Park wrote:
> On Fri, Nov 9, 2012 at 8:54 PM, Felipe Balbi wrote:
>> Hi,
>>
>> On Tue, Oct 30, 2012 at 10:27:32AM +0530, Praveen Paneri wrote:
>>> Changes from v6:
>>> Modified register definitions according to the existing ones.
>>> Changed default P
Hi,
is it and how is it possible when using the acm_tty that
there is not sent any interrupt or control URB?
My connected device has problems handling this stuff and
doesn't respond to the bulk URB which is timed somewhere
between.
I've found e.g.
URB_NO_INTERRUPT and USBDEVFS_URB_NO_INTERRUPT
Hi,
On Fri, Nov 09, 2012 at 06:50:44PM +0530, Praveen Paneri wrote:
> Hi,
>
> On Fri, Nov 9, 2012 at 6:06 PM, Kyungmin Park wrote:
> > On Fri, Nov 9, 2012 at 8:54 PM, Felipe Balbi wrote:
> >> Hi,
> >>
> >> On Tue, Oct 30, 2012 at 10:27:32AM +0530, Praveen Paneri wrote:
> >>> Changes from v6:
>
On Friday 09 November 2012 14:42:24 Markus Kolb wrote:
> Hi,
>
> is it and how is it possible when using the acm_tty that
> there is not sent any interrupt or control URB?
It is not possible.
> My connected device has problems handling this stuff and
> doesn't respond to the bulk URB which is ti
Karl Krach wrote:
> How to be detected as USB\MS_COMP_MTP?
Microsoft OS Descriptors
http://msdn.microsoft.com/en-us/library/windows/hardware/gg463179.aspx
http://msdn.microsoft.com/en-us/library/windows/hardware/ff537430%28v=vs.85%29.aspx
http://msdn.microsoft.com/en-us/windows/hardware/gg463179.
On Fri, 9 Nov 2012, Lan Tianyu wrote:
> This patch is to register usb port's acpi power resources. Create
> link between usb port device and its acpi power resource.
> +int usb_acpi_unregister_power_resources(struct usb_device *udev)
> +{
> + acpi_handle port_handle = DEVICE_ACPI_HANDLE(&udev
On Fri, 9 Nov 2012, Lan Tianyu wrote:
> This patch is to add usb port auto power off mechanism.
> When usb device is suspending, usb core will send clear usb port's
> POWER feature requst to power off port if all conditions were met.
> These conditions are remote wakeup enable, pm qos NO_POWER_OFF
On Fri, 9 Nov 2012, Lan Tianyu wrote:
> This patch is to add usb port auto power off mechanism.
> When usb device is suspending, usb core will send clear usb port's
> POWER feature requst to power off port if all conditions were met.
Actually, this is the wrong approach.
What you should do, if a
Hello, I've noticed Linux seems to have issues with external USB
enclosures containing drives > 2 TB. The USB mass storage driver
apparently emulates a SCSI device and sends a read/write(10) for all
requests where the target sector is not large enough to require the
use of read(16). The issue is
On Fri, 9 Nov 2012, Lan Tianyu wrote:
> When pm qos flags is changing, the pm core will keep device not
> in RPM_SUSPEND via pm_runtime_get_sync/put(dev). When the flags are
> changed, this will affect usb device status. If NO_POWER_OFF flag was
> set when the device was power off, it would need t
From: "Jason J. Herne"
Force large capacity (> 2TB) drives in USB enclosures to use READ(16) instead
of READ(10). Some(most/all?) enclosures do not like READ(10) commands when a
large capacity drive is installed.
Signed-off-by: Jason J. Herne
---
drivers/scsi/sd.c |7 +--
On Fri, 9 Nov 2012, Lan Tianyu wrote:
> Some usb devices can't be resumed correctly after power off. This
> patch is to add pm qos flags request to change NO_POWER_OFF and
> provide usb_device_allow_power_off() for device drivers to allow or
> prohibit usb core to power off the device.
If the rea
On Fri, 9 Nov 2012, Jason J. Herne wrote:
> Hello, I've noticed Linux seems to have issues with external USB
> enclosures containing drives > 2 TB. The USB mass storage driver
> apparently emulates a SCSI device and sends a read/write(10) for all
Actually, it's the SCSI disk driver which decide
On 09.11.2012 15:43, Oliver Neukum wrote:
On Friday 09 November 2012 14:42:24 Markus Kolb wrote:
[...]
I've found e.g.
URB_NO_INTERRUPT and USBDEVFS_URB_NO_INTERRUPT in
http://code.metager.de/source/xref/linux/stable/drivers/usb/core/devio.c#1386
but how do I set this?
You don't. This is for
I recommend broadening this patch. T10 is discussing making READ (10), WRITE
(10), etc. obsolete in SBC-4 in favor of their 16-byte CDB counterparts.
The algorithm should be:
1. During discovery, determine if 16-byte CDBs are supported. There are
several ways to determine this:
a) REPORT SUP
On 09.11.2012 16:40, Peter Stuge wrote:
Microsoft OS Descriptors
Thanks a lot. It seams that the Android [1] has the 'Microsoft OS
Descriptors' implemented while Meego has not. Porting from the Android
code don't seems to be straightforward for me - do you know a better
solution?
Accordin
Hi Greg,
Here are the transceiver patches for v3.8 merge window. Let me know
if you want any changes.
Have a nice weekend
ps: for samsung folks, I'm sorry but I couldn't wait any longer.
The following changes since commit ddffeb8c4d0331609ef2581d84de4d763607bd37:
Linux 3.7-rc1 (2012-10-14 14
Hi Greg,
MUSB changes for v3.8 follow. This will conflict with your usb-next branch,
below you can find the resolution I used:
diff --cc drivers/usb/musb/musb_dsps.c
index ff5f112,e770f79..cf08966a
--- a/drivers/usb/musb/musb_dsps.c
+++ b/drivers/usb/musb/musb_dsps.c
@@@ -458,14 -489,24 +489,24 @
Hi Greg,
Here are dwc3 patches for v3.8. This will also conflict with your usb-next
branch and below you can find my resolution:
diff --cc drivers/usb/dwc3/core.c
index c14ebc9,2bd007d..4174054
--- a/drivers/usb/dwc3/core.c
+++ b/drivers/usb/dwc3/core.c
@@@ -408,11 -355,6 +355,10 @@@ err0
stati
Hi Greg,
Here are gadget patches for v3.8, and it also conflicts with your
usb-next branch. Below you can find my resolution (suggested
by Kuninori):
diff --cc drivers/usb/renesas_usbhs/fifo.c
index c021b20,72ad375..9538f0f
--- a/drivers/usb/renesas_usbhs/fifo.c
+++ b/drivers/usb/renesas_usbhs/fi
On Fri, 9 Nov 2012, Lan Tianyu wrote:
> This patch is to expose usb port's pm qos flags(pm_qos_no_power_off,
> pm_qos_remote_wakeup) to user space. The pm_qos_no_power_off will
> be used to control usb port auto power off mechanism from user space.
Something here doesn't look right...
> @@ -1289
On 29/10/12 06:14 PM, Alan Stern wrote:
On Mon, 29 Oct 2012, Richard Retanubun wrote:
Focusing down on one of the dumps:
unreferenced object 0xd3849740 (size 8):
comm "khubd", pid 1026, jiffies 232553037 (age 506.597s)
hex dump (first 8 bytes):
4d 43 38 37 30 35 00 00
36 matches
Mail list logo
