On Mon, May 19, 2014 at 05:40:29PM +0200, Andrzej Pietrasiewicz wrote:
> Hi Peter,
>
> W dniu 16.05.2014 11:00, Peter Chen pisze:
> >Hi Felipe & Alan,
> >
> >To continue with topic discussed at
> >http://www.spinics.net/lists/linux-usb/msg105279.html,
> >I implement the gadget bus to bind udc to g
On Monday, May 19, 2014 02:19:52 PM you wrote:
> On Sat, 2014-05-17 at 05:08 +0700, Alif Mubarak Ahmad wrote:
> > This device vendor and product id is 1c9e:9800
> > It is working as serial interface with generic usbserial driver.
> > I thought it is more suitable to use usbserial option driver, whi
On Mon, 2014-05-19 at 23:35 +0300, Dan Carpenter wrote:
> My previous patch introduced a bug which prevented this driver from
> loading. devm_ioremap_resource() has a call to
> devm_request_mem_region() which will fail because the address space is
> shared between this PHY driver and CI device con
why not reuse the musb_irq_work?
On Wed, Apr 2, 2014 at 7:58 PM, Daniel Mack wrote:
> Handle BABBLE interrupt error conditions from a work struct handler.
> This indirection is necessary as we can't be certain that the phy
> functions don't sleep.
>
> Platform layer implementation may pass a babb
On Tue, 2014-05-20 at 14:02 +0700, Alif Mubarak Ahmad wrote:
> On Monday, May 19, 2014 02:19:52 PM you wrote:
> I've applied the patch, but it seems rejected. I am using kernel 3.10.36 for
> use with OpenWrt.
It was against git HEAD. Sorry.
> For your information, manually triggering echo 1c9e
[adding Greg Suarez to the Cc list after noticing that he was missing
from this thread. Sorry Greg, that was not my intention. This
discussion is just as relevant to cdc_mbim as to cdc_ncm, defining a
new common userspace API for all the cdc_ncm based drivers]
Bjørn Mork writes:
> Lars Melin
On Monday 19 May 2014 16:42:18 Rob Herring wrote:
> On Mon, May 19, 2014 at 10:56 AM, Catalin Marinas
> wrote:
> > On Mon, May 19, 2014 at 10:44:51AM +0100, Arnd Bergmann wrote:
> > > On Monday 19 May 2014 10:03:40 Catalin Marinas wrote:
> > > > On Mon, May 19, 2014 at 09:32:43AM +0100, Arnd Bergm
On Tue, May 20, 2014 at 10:19:12AM +0300, Ivan T. Ivanov wrote:
> On Mon, 2014-05-19 at 23:35 +0300, Dan Carpenter wrote:
> > My previous patch introduced a bug which prevented this driver from
> > loading. devm_ioremap_resource() has a call to
> > devm_request_mem_region() which will fail because
From: Alan Stern
...
> > -static struct usb_request *
> > -net2280_alloc_request (struct usb_ep *_ep, gfp_t gfp_flags)
> > +static struct usb_request *net2280_alloc_request(struct usb_ep *_ep,
> > + gfp_t gfp_flags)
>
> What's with the extreme inde
Not for grep...
But if this is an issue I have no problem going back to the original.
We can spend a whole year just talking about codestyle.
On Tue, May 20, 2014 at 10:52 AM, David Laight wrote:
> From: Alan Stern
> ...
>> > -static struct usb_request *
>> > -net2280_alloc_request (struct usb
>
> On Tue, 6 May 2014, Peter Chen wrote:
>
> > 3. Besides, I have tried two configurations, and each configuration
> > with one function, I find the host PC always set configuration 1 (The
> first
> > configuration), any ways to switch configuration at host side?
> > libusb?
>
> Y
Hi Geert-san,
(2014/05/19 20:58), Geert Uytterhoeven wrote:
> Hi Shimoda-san,
>
> On Mon, May 19, 2014 at 12:08 PM, Yoshihiro Shimoda
> wrote:
< snip >
>> +config USB_XHCI_RCAR
>> + tristate "xHCI support for Renesas R-Car SoCs"
>> + select USB_XHCI_PLATFORM
>> + depends on ARC
Hi Magnus-san,
(2014/05/19 19:21), Magnus Damm wrote:
> Hi Shimoda-san,
>
> Thanks for your patches, I did however find one typo below:
>
> On Mon, May 19, 2014 at 7:08 PM, Yoshihiro Shimoda
> wrote:
< snip >
>> static int xhci_plat_start(struct usb_hcd *hcd)
>> {
>> + struct device_nod
Hello,
(2014/05/19 21:14), Sergei Shtylyov wrote:
> Hello.
>
> On 19-05-2014 14:08, Yoshihiro Shimoda wrote:
< snip >
>> static int xhci_plat_start(struct usb_hcd *hcd)
>> {
>> +struct device_node *of_node = hcd->self.controller->of_node;
>> +
>> +if (of_device_is_compatible(of_node,
On 05/20/2014 04:01 AM, Greg KH wrote:
> On Thu, May 08, 2014 at 07:25:55PM +0300, Mathias Nyman wrote:
>> From: Dan Williams
>>
>> Add a command line switch for disabling ehci port switchover. Useful
>> for working around / debugging xhci incompatibilities where ehci
>> operation is available.
>
At Tue, 20 May 2014 12:47:36 +0300,
Mathias Nyman wrote:
>
> On 05/20/2014 04:01 AM, Greg KH wrote:
> > On Thu, May 08, 2014 at 07:25:55PM +0300, Mathias Nyman wrote:
> >> From: Dan Williams
> >>
> >> Add a command line switch for disabling ehci port switchover. Useful
> >> for working around /
On Monday 19 May 2014 19:08:05 Yoshihiro Shimoda wrote:
>
> #include "xhci.h"
> #include "xhci-mvebu.h"
> +#include "xhci-rcar.h"
>
> static void xhci_plat_quirks(struct device *dev, struct xhci_hcd *xhci)
> {
> @@ -39,6 +40,12 @@ static int xhci_plat_setup(struct usb_hcd *hcd)
>
> static i
Hi Shimoda-san,
On Tue, May 20, 2014 at 11:35 AM, Yoshihiro Shimoda
wrote:
> (2014/05/19 20:58), Geert Uytterhoeven wrote:
>> On Mon, May 19, 2014 at 12:08 PM, Yoshihiro Shimoda
>> wrote:
> < snip >
>>> +config USB_XHCI_RCAR
>>> + tristate "xHCI support for Renesas R-Car SoCs"
>>> +
Patch "xhci: Switch Intel Lynx Point ports to EHCI on shutdown."
commit c09ec25d3684cad74d851c0f028a495999591279 is not fully correct
It switches both Lynx Point and Lynx Point-LP ports to EHCI on shutdown.
On some Lynx Point machines it causes spurious interrupt,
which wake the system: bugzilla.k
On Mon, May 19, 2014 at 05:55:56PM +0100, Arnd Bergmann wrote:
> On Monday 19 May 2014 16:56:08 Catalin Marinas wrote:
> > On Mon, May 19, 2014 at 10:44:51AM +0100, Arnd Bergmann wrote:
> > > On Monday 19 May 2014 10:03:40 Catalin Marinas wrote:
> > > > On Mon, May 19, 2014 at 09:32:43AM +0100, Arn
On Tuesday 20 May 2014 12:02:46 Catalin Marinas wrote:
> On Mon, May 19, 2014 at 05:55:56PM +0100, Arnd Bergmann wrote:
> > On Monday 19 May 2014 16:56:08 Catalin Marinas wrote:
> > > On Mon, May 19, 2014 at 10:44:51AM +0100, Arnd Bergmann wrote:
> > > > On Monday 19 May 2014 10:03:40 Catalin Marin
On Tuesday, May 20, 2014 09:35:40 AM Oliver Neukum wrote:
> It was against git HEAD. Sorry.
Nevermind
> Looks good, but I'd prefer a full test.
>
> Thanks
> Oliver
I've compiled the firmware and tested it.
It works perfectly. Here is some dmesg of OpenWrt boot. The 3g dongle is
USB3503 chip supports 8 values of reference clock. The value is
specified by REF_SEL[1:0] pins and INT_N line. This patch add support
for getting 'refclk' clock, enabling it and setting INT_N line according
to the value of the gathered clock. If no clock has been specified,
driver defaults to the o
On Tue, May 20, 2014 at 01:53:42PM +0200, Marek Szyprowski wrote:
> + hub->clk = devm_clk_get(dev, "refclk");
> + if (!IS_ERR(hub->clk)) {
This won't handle deferred probe - the driver should error out if it
gets -EPROBE_DEFER since it means the clock exists and might be p
>From experiments with real hardware, it seems that URSTCON bits for
HSIC0 and HSIC1 seems to be swapped, so updated macro definitions for
them. HSIC1 also requires enabling power to device phy to get properly
enabled (similar hack is already implemented for HSIC0).
Signed-off-by: Marek Szyprowski
Hello,
On 2014-05-20 13:57, Mark Brown wrote:
On Tue, May 20, 2014 at 01:53:42PM +0200, Marek Szyprowski wrote:
> + hub->clk = devm_clk_get(dev, "refclk");
> + if (!IS_ERR(hub->clk)) {
This won't handle deferred probe - the driver should error out if it
gets -EPROBE_DEFER sin
Hi Denis,
thank you very much, works fine !
But my diff to the original xhcp-pci.c of Kernel 3.14.4 is:
$ diff xhci-pci.c-original xhci-pci.c-changed
137,138d136
<
< xhci->quirks |= XHCI_SPURIOUS_REBOOT;
139a138,141
> if (pdev->vendor == PCI_VENDOR_ID_INTEL &&
>
On Tue, May 20, 2014 at 12:08:58PM +0100, Arnd Bergmann wrote:
> On Tuesday 20 May 2014 12:02:46 Catalin Marinas wrote:
> > On Mon, May 19, 2014 at 05:55:56PM +0100, Arnd Bergmann wrote:
> > > On Monday 19 May 2014 16:56:08 Catalin Marinas wrote:
> > > > On Mon, May 19, 2014 at 10:44:51AM +0100, Ar
On Mon, 19 May 2014, Ricardo Ribalda Delgado wrote:
> Instead of using magic numbers use #defines
>
> Signed-off-by: Ricardo Ribalda Delgado
> ---
> drivers/usb/gadget/net2280.c | 68
> +++-
> drivers/usb/gadget/net2280.h | 1 +
> 2 files changed, 36 in
On Tue, 20 May 2014, Heinz Diehl wrote:
> Hi,
>
> the use of the ASMedia AS2105 controller on USB 3.0 leads to the
> syslog being spammed with a lot of entries like this:
>
> usb 9-2: reset SuperSpeed USB device number 3 using xhci_hcd
> [ 232.682214] usb 9-2: Parent hub missing LPM exit latenc
From: Oliver Neukum
Reported by Alif Mubarak Ahmad:
This device vendor and product id is 1c9e:9800
It is working as serial interface with generic usbserial driver.
I thought it is more suitable to use usbserial option driver, which has better
capability distinguishing between modem serial inter
Hello Alan
In this case, there are only two family of devices supported by the
driver. Maybe quirks are too much.
At the end:
ep->dev->pdev->vendor == PCI_VENDOR_ID_PLX_LEGACY
is not much bigger than
ep->dev->quirk_flag & PLX_NET2280_QUIRK
But if you prefer the quirk I dont mind implementing
On Tue, 20 May 2014, Ricardo Ribalda Delgado wrote:
> Hello Alan
>
> In this case, there are only two family of devices supported by the
> driver. Maybe quirks are too much.
>
> At the end:
>
> ep->dev->pdev->vendor == PCI_VENDOR_ID_PLX_LEGACY
>
> is not much bigger than
>
> ep->dev->quirk_fl
Forgive my intrusion ...
Im hoping to get a driver made for a Fresco Logic FL2000 USB to VGA adapter ...
Device ID 1d5c:2000
Mike KC7NOA
--
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://vg
On Thu, May 15, 2014 at 09:22:00PM +0200, Stephen Warren wrote:
> On 05/14/2014 06:33 PM, Andrew Bresticker wrote:
> > Initialize the XUSB-related clocks with appropriate parents and rates
> > for both Tegra114 and Tegra124.
>
> These first 4 clock driver patches look plausible to me, although I
>
On 20.05.2014, Alan Stern wrote:
> I have no idea if this will help, but you can try posting a usbmon
> trace showing what happens when the device is plugged in and the errors
> occur.
Connected the drive and did some "dd if=/dev/zero..." to it.
It failed within seconds. This is what "dmesg" s
On 20.05.2014, Heinz Diehl wrote:
> The usbmon dump of the whole process is here:
> http://www.fritha.org/usblog.zip
And here's another one, while popping in and out.
http://www.fritha.org/usblog2.zip
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a messa
- Move logical continuations to end of line
- Improve spacing
Signed-off-by: Ricardo Ribalda Delgado
---
v2: Comments by Alan Stern
-Use octal notation istead of S_I
drivers/usb/gadget/net2280.c | 155 +--
drivers/usb/gadget/net2280.h | 4 +-
2
Use of quirks improve readability and will be easier to add new devices
to this driver.
Suggested-by: Alan Stern
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/usb/gadget/net2280.c | 83 +++-
drivers/usb/gadget/net2280.h | 6
2 files changed, 49
Replace a long and ugly expresion with an already available function.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/usb/gadget/net2280.c | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/drivers/usb/gadget/net2280.c b/drivers/usb/gadget/net2280.c
index bd851de..c
The USB 3380 is a PCI Express Gen 2 to USB 3.0 SuperSpeed Peripheral
Controller. It shares a lot functionatily with the net228x family.
This series of patches includes some resend of previous patches.
Please check the changelog for every patch. This time it has been placed
under the tear line
For bool variables
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/usb/gadget/net2280.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/usb/gadget/net2280.c b/drivers/usb/gadget/net2280.c
index 5b9368d..b43725a 100644
--- a/drivers/usb/gadget/net2280.c
+++
Improves readability of the code
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/usb/gadget/net2280.c | 572 +--
drivers/usb/gadget/net2280.h | 65 ++---
2 files changed, 318 insertions(+), 319 deletions(-)
diff --git a/drivers/usb/gadget/net2280.c b/
Instead of using magic numbers use #defines
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/usb/gadget/net2280.c | 68 +++-
drivers/usb/gadget/net2280.h | 1 +
2 files changed, 36 insertions(+), 33 deletions(-)
diff --git a/drivers/usb/gadget/net2280.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/usb/gadget/net2280.c | 19 +--
1 file changed, 5 insertions(+), 14 deletions(-)
diff --git a/drivers/usb/gadget/net2280.c b/drivers/usb/gadget/net2280.c
index b43725a..bd851de 100644
--- a/drivers/usb/gadget/net2280.c
+++ b/drive
Driver was using custom functions WARNING, ERROR, DEBUG, instead of
pr_err, pr_dgb...
New ep_* macros have been created that use standard pr_* functions.
Signed-off-by: Ricardo Ribalda Delgado
---
v2: Comment by Joe Perches and Alan Stern
-Use ep_* instead of custom DETDEV macro
drivers/usb
Hello Michal,
Recently I'm working with configfs and libusbg. I have been also using
FFS with it as it was merged in some recent kernel versions. While using
I have experienced some issue while mounting it. Let me describe my it:
$ cd /sys/kernel/config/usb_gadget
$ mkdir g1
$ mkdir g1/functions
On Tue, May 20, 2014 at 3:01 AM, Arnd Bergmann wrote:
> On Monday 19 May 2014 16:42:18 Rob Herring wrote:
>> On Mon, May 19, 2014 at 10:56 AM, Catalin Marinas
>> wrote:
>> > On Mon, May 19, 2014 at 10:44:51AM +0100, Arnd Bergmann wrote:
>> > > On Monday 19 May 2014 10:03:40 Catalin Marinas wrote:
On Tue, May 20 2014, Krzysztof Opasiak wrote:
> I found out that kernel returns -ENODEV error which when file system
> type has not been found. I look into code of ffs and found out that
> ffs_fs_mount() also returns this error if it was unable to acquire given
> device. I know that this error look
On Tue, May 20, 2014 at 2:51 AM, Takashi Iwai wrote:
> At Tue, 20 May 2014 12:47:36 +0300,
> Mathias Nyman wrote:
>>
>> On 05/20/2014 04:01 AM, Greg KH wrote:
>> > On Thu, May 08, 2014 at 07:25:55PM +0300, Mathias Nyman wrote:
>> >> From: Dan Williams
>> >>
>> >> Add a command line switch for dis
At Tue, 20 May 2014 11:25:37 -0700,
Dan Williams wrote:
>
> On Tue, May 20, 2014 at 2:51 AM, Takashi Iwai wrote:
> > At Tue, 20 May 2014 12:47:36 +0300,
> > Mathias Nyman wrote:
> >>
> >> On 05/20/2014 04:01 AM, Greg KH wrote:
> >> > On Thu, May 08, 2014 at 07:25:55PM +0300, Mathias Nyman wrote:
On Thu, 2014-04-24 at 18:51 -0700, Joe Perches wrote:
> Use a newline character appropriately.
>
> Signed-off-by: Joe Perches
> ---
Greg? Ping?
You inadvertently added this "/n" use in
commit 0a3fd536e685e0ceb646de1a43821bd11c0be75c
Author: Greg Kroah-Hartman
Date: Tue May 1 21:33:54 2012 -
On Tuesday 20 May 2014 15:12:49 Catalin Marinas wrote:
> On Tue, May 20, 2014 at 12:08:58PM +0100, Arnd Bergmann wrote:
> > On Tuesday 20 May 2014 12:02:46 Catalin Marinas wrote:
> > > On Mon, May 19, 2014 at 05:55:56PM +0100, Arnd Bergmann wrote:
> > > > On Monday 19 May 2014 16:56:08 Catalin Mari
Commit [ac8dde11: “usb: gadget: f_fs: Add flags to descriptors block”]
which introduced a new descriptor format for FunctionFS removed the
usb_functionfs_descs_head structure, which is still used by ffs-test.
tool.
Convert ffs-test by converting it to use the new header format. For
testing kernel
Hi,
On Tue, May 20, 2014 at 10:05:09AM -1000, Michal Nazarewicz wrote:
> Commit [ac8dde11: “usb: gadget: f_fs: Add flags to descriptors block”]
> which introduced a new descriptor format for FunctionFS removed the
> usb_functionfs_descs_head structure, which is still used by ffs-test.
> tool.
>
>
Use a more standard logging style.
Add terminating newlines to formats.
Remove __func__ as that can be added via dynamic debug.
Remove now unnecessary debug module parameter.
Remove the dbg macro too.
Signed-off-by: Joe Perches
---
compiled/untested, no hardware.
drivers/usb/misc/iowarrior.c
On Tue, May 20, 2014 at 12:26:53PM -0700, Joe Perches wrote:
> On Thu, 2014-04-24 at 18:51 -0700, Joe Perches wrote:
> > Use a newline character appropriately.
> >
> > Signed-off-by: Joe Perches
> > ---
>
> Greg? Ping?
>
> You inadvertently added this "/n" use in
> commit 0a3fd536e685e0ceb646d
On Tue, May 20, 2014 at 08:07:43AM -0700, Michael Durkin wrote:
> Forgive my intrusion ...
>
> Im hoping to get a driver made for a Fresco Logic FL2000 USB to VGA adapter
> ...
>
> Device ID 1d5c:2000
What type of chip is in this device? If it is a USB 3 device, odds are
that Linux doesn't sup
On Tue, May 20, 2014 at 11:25:37AM -0700, Dan Williams wrote:
> On Tue, May 20, 2014 at 2:51 AM, Takashi Iwai wrote:
> > At Tue, 20 May 2014 12:47:36 +0300,
> > Mathias Nyman wrote:
> >>
> >> On 05/20/2014 04:01 AM, Greg KH wrote:
> >> > On Thu, May 08, 2014 at 07:25:55PM +0300, Mathias Nyman wrot
On Tue, May 20, 2014 at 02:18:30PM +0200, Marek Szyprowski wrote:
> On 2014-05-20 13:57, Mark Brown wrote:
> >> + else
> >> + dev_err(dev,
> >> + "unsupported reference clock rate
> >> (%d)\n",
> >> +
It can be used on USB3 or USB2 .. depending on max resolution ... I
would be happy with USB2 800X600 resolution ...
I got the device off of ebay ... but i could send an email to Fresco
Logic (the maker of the IC) or to Orinco (who sells retail devices)
I have already sent an email to the seller wh
On Tue, May 20, 2014 at 1:34 PM, Greg KH wrote:
> On Tue, May 20, 2014 at 11:25:37AM -0700, Dan Williams wrote:
>> On Tue, May 20, 2014 at 2:51 AM, Takashi Iwai wrote:
>> > At Tue, 20 May 2014 12:47:36 +0300,
>> > Mathias Nyman wrote:
>> >>
>> >> On 05/20/2014 04:01 AM, Greg KH wrote:
>> >> > On
Hi,
On Wed, May 21, 2014 at 05:31:13AM +0900, Greg KH wrote:
> On Tue, May 20, 2014 at 08:07:43AM -0700, Michael Durkin wrote:
> > Forgive my intrusion ...
> >
> > Im hoping to get a driver made for a Fresco Logic FL2000 USB to VGA
> > adapter ...
> >
> > Device ID 1d5c:2000
>
> What type of ch
On Tue, May 20, 2014 at 06:38:01PM -0500, Felipe Balbi wrote:
> Hi,
>
> On Wed, May 21, 2014 at 05:31:13AM +0900, Greg KH wrote:
> > On Tue, May 20, 2014 at 08:07:43AM -0700, Michael Durkin wrote:
> > > Forgive my intrusion ...
> > >
> > > Im hoping to get a driver made for a Fresco Logic FL2000
On Fri, May 16, 2014 at 11:32 AM, Alan Stern wrote:
> On Wed, 7 May 2014, Dan Williams wrote:
>
>> We want to manipulate ->did_runtime_put in usb_port_runtime_resume(),
>> but we don't want that to collide with other updates. Move usb_port
>> flags to new port-bitmap fields in usb_hub. "did_runti
From: Alan Stern
The USB core doesn't properly handle mutual exclusion between
resetting a hub and changing the power states of the hub's ports. We
need to avoid sending port-power requests to the hub while it is being
reset, because such requests cannot succeed.
This patch fixes the problem by
A hub indicates whether it supports per-port power control via the
wHubCharacteristics field in its descriptor. If it is not supported
a hub will still emulate ClearPortPower(PORT_POWER) requests by
stopping the link state machine. However, since this does not save
power do not bother suspending.
Assume that the peer of a superspeed port is the port with the same id
on the shared_hcd root hub. This identification scheme is required of
external hubs by the USB3 spec [1]. However, for root hubs, tier mismatch
may be in effect [2]. Tier mismatch can only be enumerated via platform
firmware.
The current port name "portX" is ambiguous. Before adding more port
messages rename ports to "-portX"
This is an ABI change, but the suspicion is that it will go unnoticed as
the port power control implementation has been broken since its
introduction. If however, someone was relying on the old
We want to manipulate ->did_runtime_put in usb_port_runtime_resume(),
but we don't want that to collide with other updates. Move usb_port
flags to new port-bitmap fields in usb_hub. "did_runtime_put" is renamed
"child_usage_bits" to reflect that it is strictly standing in for the
fact that usb_dev
The usb topology after this change will have symlinks between usb3 ports
and their usb2 peers, for example:
usb2/2-1/2-1:1.0/2-1-port1/peer => ../../../../usb3/3-1/3-1:1.0/3-1-port1
usb2/2-1/2-1:1.0/2-1-port2/peer => ../../../../usb3/3-1/3-1:1.0/3-1-port2
usb2/2-1/2-1:1.0/2-1-port3/peer => ../../.
Three reasons:
1/ It's an invalid operation on usb3 ports
2/ There's no guarantee of when / if a usb2 port has entered an error
state relative to PORT_POWER request
3/ The port is active / powered at this point, so khubd will clear it as
a matter of course
Acked-by: Alan Stern
Signed-off-by
The port pm_runtime implementation unconditionally clears FEAT_C_ENABLE
after clearing PORT_POWER, but the bit is reserved on usb3 hub ports.
We expect khubd to be prevented from running because the port state is
not RPM_ACTIVE, so we need to clear any errors for usb2 ports.
Acked-by: Alan Stern
ACPI identifies peer ports by setting their 'group_token' and
'group_position' _PLD data to the same value. If a platform has tier
mismatch [1] , ACPI can override the default (USB3 defined) peer port
association for internal hubs. External hubs follow the default peer
association scheme.
Locati
Unconditionally wake up the child device when the power session is
recovered.
This addresses the following scenarios:
1/ The device may need a reset on power-session loss, without this
change port power-on recovery exposes khubd to scenarios that
usb_port_resume() is set to handle. Prior t
In preparation for synchronizing port handling with pm_runtime
transitions refactor port handling into its own subroutine.
We expect that clearing some status flags will be required regardless of
the port state, so handle those first and group all non-trivial actions
at the bottom of the routine.
ClearPortFeature(PORT_POWER) on a usb3 port places the port in either a
DSPORT.Powered-off-detect / DSPORT.Powered-off-reset loop, or the
DSPORT.Powered-off state. There is no way to ensure that RX
terminations will persist in this state, so it is possible a device will
degrade to its usb2 connect
Per Alan:
"You mean from within hub_handle_remote_wakeup()? That routine will
never get called if CONFIG_PM_RUNTIME isn't enabled, because khubd
never sees wakeup requests if they arise during system suspend.
In fact, that routine ought to go inside the "#ifdef CONFIG_PM_RUNTIME"
portion of hub.c
From: Lan Tianyu
describe the mechanisms for controlling port power policy and
discovering the port power state.
Cc: Oliver Neukum
[oliver]: fixes, clarification of wakeup vs port-power-control
Signed-off-by: Lan Tianyu
[sarah]: wordsmithing
[djbw]: updates for peer port changes
Signed-off-by:
Resuming a powered down port sometimes results in the port state being
stuck in the training sequence.
hub 3-0:1.0: debounce: port 1: total 2000ms stable 0ms status 0x2e0
port1: can't get reconnection after setting port power on, status -110
hub 3-0:1.0: port 1 status .02e0 after resume, -
If a port is powered-off, or in the process of being powered-off, prevent
khubd from operating on it. Otherwise, the following sequence of events
leading to an unintended disconnect may occur:
Events:
(0)
(1) hub 2-2:1.0: hub_resume
(2) hub 2-2:1.0: port 1: status 0301 change
(3) hub 2-2:1.
Ok ill join them and see if linux-me...@vger.kernel.org are working on it ...
i had no idea where to start ...
Mike KC7NOA
On Tue, May 20, 2014 at 5:25 PM, Greg KH wrote:
> On Tue, May 20, 2014 at 06:38:01PM -0500, Felipe Balbi wrote:
>> Hi,
>>
>> On Wed, May 21, 2014 at 05:31:13AM +0900, Greg
Given that root hub port peers are already established, external hub peer
ports can be determined by traversing the device topology:
1/ ascend to the parent hub and find the upstream port_dev
2/ walk ->peer to find the peer port
3/ descend to the peer hub via ->child
4/ find the port with the m
Once usb-acpi has set the port's connect type the usb_device's
->removable attribute can be set in the standard location
set_usb_port_removable().
This also changes behavior in the case where the firmware says that the
port connect type is unknown. In that case just use the default setting
determ
Greg,
Here is the port power control rework for your consideration now that
Alan has finished acking it (see summary below). Patch 9 had one
outstanding minor question from Alan that I believe I have addressed.
Patch 16 has a checkpatch warning "WARNING: msleep < 20ms can sleep for
up to 20ms", b
In general we do not want khubd to act on port status changes that are
the result of in progress resets or USB runtime PM operations.
Specifically port power control testing has been able to trigger an
unintended disconnect in hub_port_connect_change(), paraphrasing:
if ((portstatus & USB_
Hi Greg,
Mike has the udlfb module, the Fresco does not work with it.
Hopefully he'll get a solution via the linux-media list as suggested.
Regards
Sid.
On 20/05/14 21:31, Greg KH wrote:
On Tue, May 20, 2014 at 08:07:43AM -0700, Michael Durkin wrote:
Forgive my intrusion ...
Im hoping to get a
On Tue, May 20, 2014 at 03:40:16PM -0700, Dan Williams wrote:
> On Tue, May 20, 2014 at 1:34 PM, Greg KH wrote:
> > On Tue, May 20, 2014 at 11:25:37AM -0700, Dan Williams wrote:
> >> On Tue, May 20, 2014 at 2:51 AM, Takashi Iwai wrote:
> >> > At Tue, 20 May 2014 12:47:36 +0300,
> >> > Mathias Nym
Hi all,
On Mon, 19 May 2014 09:21:09 +0200 Bjørn Mork wrote:
>
> The upper timer_interval limit is arbitrary and much higher
> than anything usable in the real world. Reducing it from 15s
> to ~4s to make the timer_interval fit in an u32 does not make
> much difference. The limit is still outsi
It has already been covered by udc core
Signed-off-by: Peter Chen
---
drivers/usb/gadget/m66592-udc.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/gadget/m66592-udc.c b/drivers/usb/gadget/m66592-udc.c
index 5396b24..2dc37d1 100644
--- a/drivers/usb/gadget
It has already been covered by udc core
Signed-off-by: Peter Chen
---
drivers/usb/gadget/omap_udc.c |5 +
1 files changed, 1 insertions(+), 4 deletions(-)
diff --git a/drivers/usb/gadget/omap_udc.c b/drivers/usb/gadget/omap_udc.c
index 2ae4f6d..e731373 100644
--- a/drivers/usb/gadget/om
It has already been covered by udc core
Signed-off-by: Peter Chen
---
drivers/usb/gadget/fusb300_udc.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/gadget/fusb300_udc.c b/drivers/usb/gadget/fusb300_udc.c
index 90d2836..e882d41 100644
--- a/drivers/usb/gad
It has already been covered by udc core
Signed-off-by: Peter Chen
---
drivers/usb/gadget/fsl_udc_core.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/drivers/usb/gadget/fsl_udc_core.c
b/drivers/usb/gadget/fsl_udc_core.c
index dd9ff29..0ae3705 100644
--- a/drivers/usb/
Hi Felipe,
This patch set cleans up unnecessary .unbind calling at udc driver,
the udc core covers gadget driver's .unbind calling well.
Peter Chen (5):
usb: gadget: fsl_udc_core: should not call gadget driver's .unbind
usb: gadget: fusb300_udc: should not call gadget driver's .unbind
usb:
It has already been covered by udc core, besides, we do not
need unbind at .udc_start
Signed-off-by: Peter Chen
---
drivers/usb/gadget/net2272.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/usb/gadget/net2272.c b/drivers/usb/gadget/net2272.c
index ca15405..05
From: Bjørn Mork
Date: Mon, 19 May 2014 09:21:09 +0200
> The upper timer_interval limit is arbitrary and much higher
> than anything usable in the real world. Reducing it from 15s
> to ~4s to make the timer_interval fit in an u32 does not make
> much difference. The limit is still outside the p
The otg queue work include operations: one is disable interrupt,
another one is call kernel queue work API. Many codes do this
operation, using one inline function to instead of them.
Signed-off-by: Peter Chen
---
drivers/usb/chipidea/core.c|6 +--
drivers/usb/chipidea/otg.h |5 +
On Tue, May 20, 2014 at 5:27 PM, Greg KH wrote:
>> Greg,
>>
>> Sorry, I don't think it is fair to users to force them to re-compile
>> their kernel to get their device to work.
>
> I totally agree.
>
>> Granted, I'm new to USB
>> development, but the rate of reports of endpoint devices that mess u
On Tue, May 20, 2014 at 11:21:03PM -0700, Dan Williams wrote:
> On Tue, May 20, 2014 at 5:27 PM, Greg KH wrote:
> >> Greg,
> >>
> >> Sorry, I don't think it is fair to users to force them to re-compile
> >> their kernel to get their device to work.
> >
> > I totally agree.
> >
> >> Granted, I'm ne
99 matches
Mail list logo
