On 2013年03月30日 01:23, Alan Stern wrote:
> On Fri, 29 Mar 2013, Sarah Sharp wrote:
>> However, what happens if you echo 0 to pm_qos_no_power_off, the
>> power/control is set to auto, and there's a suspended USB device
>> attached to the port with remote wakeup enabled? Will the port be
>> powered o
FUSBH200 is an ehci-like controller with some differences.
First, register layout of FUSBH200 is incompatible with EHCI.
We use a quirk flag and modify struct ehci_regs with anonymous
union and struct to make sure driver of FUSBH200 and EHCI could
coexist. Furthermore, FUSBH200 is lack of siTDs whi
On 21 March 2013 21:01, Stephen Hemminger wrote:
> I may go out on a limb and look at colord internals.
Most likely it's not colord at all, but colord-sane. Old versions of
color-sane did indeed poll libsane for scanners (libsane being a
horrible, horrible API) but since the last half-dozen relea
Hi Alan,
> So either something more complicated is happening, or I messed up my
> bisection results. I'll retest the rev under suspicion and its parent
> and get back to you.
Seems you were right: The revision I bisected to was not the culprit.
It seems that there is some other factor involved th
Am 01.04.2013 01:10, schrieb Greg KH:
On Sun, Mar 31, 2013 at 07:15:22PM +0200, Karsten Malcher wrote:
Am 31.03.2013 18:58, schrieb Greg KH:
On Sun, Mar 31, 2013 at 06:33:24PM +0200, Karsten Malcher wrote:
Am 31.03.2013 17:50, schrieb Greg KH:
On Sun, Mar 31, 2013 at 05:20:06PM +0200, Karsten
With respect to latest xHCI spec :
Revision 1.0
with errata to 8/14/12
Page 114:
Note: Consider the case where there are multiple TDs posted for pipe for a
single data transfer and a
Short Packet or other condition on one TD means that the data transfer is
terminated,
and that the subsequent TD
On Sunday, March 31, 2013 08:29:20 PM Linus Torvalds wrote:
> On Sun, Mar 31, 2013 at 3:56 PM, Rafael J. Wysocki wrote:
> >
> > So, I have two patches (on top of the Linus' tree) that will follow shortly:
>
> Should I take these directly as patches, or expect them to show up in
> a pull soon (ie
Hi,
>>> Thanks. Working on this problem now. Another problem observed for
>>> SCSI_READ_10 command, when reading from the SD card, the gadget driver
>>> never sends the MBR address, the FAT boot record address, the start of FAT
>>> address, and the start of FAT cluster address to the SD card drive
This patch-series enables runtime power management on xhci-plat,
dwc3-core, dwc3-exynos as well as on Samsung's USB 2.0 type and
USB 3.0 type PHYs.
Based on 'next' branch of Felipe Balbi's USB tree.
Changes from v2:
- Using separate functions for USB PHY runtime power management, instead of
u
By enabling runtime pm in this driver allows users of
xhci-plat to enter into runtime pm. This is not full
runtime pm support (AKA xhci-plat doesn't actually power
anything off when in runtime suspend mode) but,
just basic enablement.
Signed-off-by: Vivek Gautam
CC: Doug Anderson
---
drivers/us
Enable autosuspending of Samsung usb2.0 PHY
Signed-off-by: Vivek Gautam
---
drivers/usb/phy/phy-samsung-usb2.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/phy/phy-samsung-usb2.c
b/drivers/usb/phy/phy-samsung-usb2.c
index 45ffe03..d378fe9 100644
--- a
The PHY controller can choose between ref_pad_clk (XusbXTI-external PLL),
or EXTREFCLK (XXTI-internal clock crystal) to generate the required clock.
Adding the provision for ref_pad_clk here.
Signed-off-by: Vivek Gautam
---
drivers/usb/phy/phy-samsung-usb3.c | 46 ++
Enable autosuspending of Samsung usb3.0 PHY
Signed-off-by: Vivek Gautam
---
drivers/usb/phy/phy-samsung-usb3.c |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/phy/phy-samsung-usb3.c
b/drivers/usb/phy/phy-samsung-usb3.c
index 54f6418..a713585 100644
---
Enabling runtime power management on dwc3-exynos
letting dwc3 controller to be autosuspended on exynos
platform when not in use.
Signed-off-by: Vivek Gautam
---
drivers/usb/dwc3/dwc3-exynos.c | 12
1 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/dwc3/dw
Right now it doesn't handle full runtime suspend/resume
functionality. However it allows to handle PHYs' sleep
and wakeup across runtime suspend/resume.
Signed-off-by: Vivek Gautam
---
drivers/usb/dwc3/core.c | 43 +++
1 files changed, 43 insertions(+),
Adding APIs to handle runtime power management on PHY
devices. PHY consumers may need to wake-up/suspend PHYs
when they work across autosuspend.
Signed-off-by: Vivek Gautam
---
include/linux/usb/phy.h | 141 +++
1 files changed, 141 insertions(+), 0
Allow dwc3 to enable auto power management only after its PHYs
are initialized so that any further PHY handling by dwc3's
runtime power management callbacks is fine.
Signed-off-by: Vivek Gautam
---
drivers/usb/dwc3/core.c | 18 +-
1 files changed, 9 insertions(+), 9 deletions(-
The current code in the dwc3 probe effectively disables runtime pm
from ever working because it calls a get() that was never put() until
device removal. Change the runtime pm code to match the standard
formula and allow runtime pm to function.
Signed-off-by: Vivek Gautam
CC: Doug Anderson
---
On Mon, 1 Apr 2013, Chen Gang wrote:
>
> when suspend, it need check 'udev->actconfig'.
> so when process failure, also need check it.
>
> Signed-off-by: Chen Gang
> ---
> drivers/usb/core/driver.c | 10 ++
> 1 files changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/driv
On Mon, 1 Apr 2013, victor yeo wrote:
> Here is the fresh usbmon trace. Four SCSI commands are shown. The
> first SCSI_READ_10 command has LBA of 0. The second SCSI_READ_10
> command has LBA of 0x00ed2900, which is wrong. Somehow, the first
> SCSI_READ_10 command got the wrong data, i think. Isn't
On Mon, 1 Apr 2013, Matthijs Kooijman wrote:
> Hi Alan,
>
> > So either something more complicated is happening, or I messed up my
> > bisection results. I'll retest the rev under suspicion and its parent
> > and get back to you.
> Seems you were right: The revision I bisected to was not the culp
On Mon, 1 Apr 2013, Lan Tianyu wrote:
> On 2013年03月30日 01:23, Alan Stern wrote:
> > On Fri, 29 Mar 2013, Sarah Sharp wrote:
> >> However, what happens if you echo 0 to pm_qos_no_power_off, the
> >> power/control is set to auto, and there's a suspended USB device
> >> attached to the port with remo
On Sun, 31 Mar 2013, Arnd Bergmann wrote:
> On Saturday 30 March 2013, Arnd Bergmann wrote:
> > > > In V3:
> > > > -Detailed commit message added here about why this patch is required.
> > > > -Eliminated ehci_spear_setup routine beacuse hcd registers
> > > > directly setting in spear_ehci_hcd
On Sat, 30 Mar 2013, Arnd Bergmann wrote:
> > I guess this means the onus is now on me to split up ohci-hcd into a
> > central library and separate bus drivers, like ehci-hcd...
>
> The original plan in my teams was that Manjunath would do that after
> he was done with the simple conversion of t
On Sat, 2013-03-30 at 22:11 +0800, Ming Lei wrote:
> On Fri, Mar 29, 2013 at 12:30 AM, Dan Williams wrote:
> >
> > Some drivers (sierra_net) need the status interrupt URB
> > active even when the device is closed, because they receive
> > custom indications from firmware. Add functions to refcoun
On Sun, Mar 31, 2013 at 9:55 PM, Jiri Kosina wrote:
> On Thu, 21 Mar 2013, Daniel Vetter wrote:
>
>> Indeed, this is pretty useful and allowed me to quickly reproduce that
>> phantom irq on my gm45. Thanks to module reloading we can even reset the
>> kernel's irq disabling logic and so test differ
On Mon, Apr 01, 2013 at 11:42:30AM +0200, Karsten Malcher wrote:
> Am 01.04.2013 01:10, schrieb Greg KH:
> >On Sun, Mar 31, 2013 at 07:15:22PM +0200, Karsten Malcher wrote:
> >>Am 31.03.2013 18:58, schrieb Greg KH:
> >>>On Sun, Mar 31, 2013 at 06:33:24PM +0200, Karsten Malcher wrote:
> Am 31.03
Just couple minor comments...
On 03/28/2013 06:43 AM, Kishon Vijay Abraham I wrote:
The PHY framework provides a set of APIs for the PHY drivers to
create/destroy a PHY and APIs for the PHY users to obtain a reference to the
PHY with or without using phandle. To obtain a reference to the PHY wit
Am 01.04.2013 21:12, schrieb Greg KH:
On Mon, Apr 01, 2013 at 11:42:30AM +0200, Karsten Malcher wrote:
Am 01.04.2013 01:10, schrieb Greg KH:
On Sun, Mar 31, 2013 at 07:15:22PM +0200, Karsten Malcher wrote:
Am 31.03.2013 18:58, schrieb Greg KH:
On Sun, Mar 31, 2013 at 06:33:24PM +0200, Karsten
Hi, Oliver
> -Original Message-
> From: Oliver Neukum [mailto:oli...@neukum.org]
> Sent: Saturday, March 30, 2013 10:34 AM
> To: Mike Verstegen
> Cc: linux-usb@vger.kernel.org
> Subject: Re: cdc_acm device - unexpected characters sent to USB device
>
> On Saturday 30 March 2013 03:20:15
Arnd Bergmann writes:
> On Friday 29 March 2013, Alan Stern wrote:
>> On Thu, 28 Mar 2013, Arnd Bergmann wrote:
>
>> This patch is good. However the ehci-msm driver itself is not. While
>> checking through the code, I was struck by the fact that it never calls
>> usb_add_hcd() or usb_remove_hcd
On 03/28/2013 06:43 AM, Kishon Vijay Abraham I wrote:
diff --git a/Documentation/devicetree/bindings/phy/phy-bindings.txt
b/Documentation/devicetree/bindings/phy/phy-bindings.txt
new file mode 100644
index 000..35696b2
--- /dev/null
+++ b/Documentation/devicetree/bindings/phy/phy-bindings.txt
On 04/01/2013 04:27 PM, Sylwester Nawrocki wrote:
> On 03/28/2013 06:43 AM, Kishon Vijay Abraham I wrote:
>> diff --git a/Documentation/devicetree/bindings/phy/phy-bindings.txt
>> +example2:
>> +phys: phy {
>> +compatible = "xxx";
>> +reg =<...>;
>> +.
>> +.
>> +phys =<&phys 1>
On 2013年04月01日 22:58, Alan Stern wrote:
> Thanks for spotting this.
>
> Acked-by: Alan Stern
thank you too.
--
Chen Gang
Asianux Corporation
--
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
The usb/misc/appledisplay driver doesn't use the HID layer, so its devices
should be blacklisted in HID. With this patch, supported Apple displays are
automatically recognized as backlight devices.
Signed-off-by: Ben Jencks
---
drivers/hid/hid-core.c |5 +
1 file changed, 5 insertions(+)
The usb/misc/appledisplay driver doesn't use the HID layer, so its devices
should be blacklisted in HID. With this patch, supported Apple displays are
automatically recognized as backlight devices.
Signed-off-by: Ben Jencks
---
Sorry for the resend to linux-usb; this should have gone to linux-inp
Add the Apple 24" LED Cinema display to the supported devices.
Signed-off-by: Ben Jencks
---
drivers/usb/misc/appledisplay.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/misc/appledisplay.c b/drivers/usb/misc/appledisplay.c
index 0fc6e5f..ba6a5d6 100644
--- a/drivers/usb/mi
37 matches
Mail list logo
