At Wed, 11 Sep 2013 16:42:09 -0700,
Sarah Sharp wrote:
Hi Takashi,
You've added the PCI device IDs of the xHCI LPT and LPT-LP to pci_ids.h.
AFAIK, the xHCI driver is the only driver to use it, and I thought the
rule was that we would only add the device IDs to pci_ids.h if more than
one
The driver core clears the driver data to NULL after device_release
or on probe failure. Thus, it is not needed to manually clear the
device driver data to NULL.
Signed-off-by: Jingoo Han jg1@samsung.com
---
drivers/usb/gadget/amd5536udc.c |2 --
1 file changed, 2 deletions(-)
diff
The driver core clears the driver data to NULL after device_release
or on probe failure. Thus, it is not needed to manually clear the
device driver data to NULL.
Signed-off-by: Jingoo Han jg1@samsung.com
---
drivers/usb/gadget/goku_udc.c |1 -
1 file changed, 1 deletion(-)
diff --git
The driver core clears the driver data to NULL after device_release
or on probe failure. Thus, it is not needed to manually clear the
device driver data to NULL.
Signed-off-by: Jingoo Han jg1@samsung.com
---
drivers/usb/gadget/pch_udc.c |1 -
1 file changed, 1 deletion(-)
diff --git
The driver core clears the driver data to NULL after device_release
or on probe failure. Thus, it is not needed to manually clear the
device driver data to NULL.
Signed-off-by: Jingoo Han jg1@samsung.com
---
drivers/usb/gadget/net2280.c |1 -
1 file changed, 1 deletion(-)
diff --git
On Tue, Sep 10, 2013 at 01:02:34PM -0700, Gary E. Miller wrote:
Sure PPS over a local UART is 10 to 100 times better, but often PPS
over USB is your best second choice. As serial ports become extinct
it may become your best choice.
Ok. But, please, add a note about it into PPS documentation
Hi Kishon,
On Mon, Sep 2, 2013 at 9:13 PM, Kishon Vijay Abraham I kis...@ti.com wrote:
Adapted dwc3 core to use the Generic PHY Framework. So for init, exit,
power_on and power_off the following APIs are used phy_init(), phy_exit(),
phy_power_on() and phy_power_off().
However using the old
On Thursday 12 September 2013 02:57 PM, Vivek Gautam wrote:
Hi Kishon,
On Mon, Sep 2, 2013 at 9:13 PM, Kishon Vijay Abraham I kis...@ti.com wrote:
Adapted dwc3 core to use the Generic PHY Framework. So for init, exit,
power_on and power_off the following APIs are used phy_init(),
On Thu, Sep 12, 2013 at 3:40 PM, Kishon Vijay Abraham I kis...@ti.com wrote:
On Thursday 12 September 2013 02:57 PM, Vivek Gautam wrote:
Hi Kishon,
On Mon, Sep 2, 2013 at 9:13 PM, Kishon Vijay Abraham I kis...@ti.com wrote:
Adapted dwc3 core to use the Generic PHY Framework. So for init,
Hi Kishon,
On 09/02/2013 06:43 PM, Kishon Vijay Abraham I wrote:
There can be systems which does not have a external usb_phy, so get
usb_phy only if usb-phy property is added in the case of dt boot or if
platform_data indicates the presence of PHY. Also remove checking if
return value is
On Thu, Sep 12, 2013 at 4:06 PM, Roger Quadros rog...@ti.com wrote:
Hi Kishon,
On 09/02/2013 06:43 PM, Kishon Vijay Abraham I wrote:
There can be systems which does not have a external usb_phy, so get
usb_phy only if usb-phy property is added in the case of dt boot or if
platform_data
Hi,
On 09/12/2013 01:47 PM, Vivek Gautam wrote:
On Thu, Sep 12, 2013 at 4:06 PM, Roger Quadros rog...@ti.com wrote:
Hi Kishon,
On 09/02/2013 06:43 PM, Kishon Vijay Abraham I wrote:
There can be systems which does not have a external usb_phy, so get
usb_phy only if usb-phy property is added
Hi Kishon,
On 09/02/2013 06:43 PM, Kishon Vijay Abraham I wrote:
Adapted omap-usb3 PHY driver to Generic PHY Framework and moved phy-omap-usb3
driver in drivers/usb/phy to drivers/phy and also renamed the file to
phy-omap-pipe3 since this same driver will be used for SATA PHY and
PCIE PHY.
I
Hi,
On Thu, Sep 12, 2013 at 4:34 PM, Roger Quadros rog...@ti.com wrote:
Hi,
On 09/12/2013 01:47 PM, Vivek Gautam wrote:
On Thu, Sep 12, 2013 at 4:06 PM, Roger Quadros rog...@ti.com wrote:
Hi Kishon,
On 09/02/2013 06:43 PM, Kishon Vijay Abraham I wrote:
There can be systems which does not
On 09/12/2013 02:26 PM, Vivek Gautam wrote:
Hi,
On Thu, Sep 12, 2013 at 4:34 PM, Roger Quadros rog...@ti.com wrote:
Hi,
On 09/12/2013 01:47 PM, Vivek Gautam wrote:
On Thu, Sep 12, 2013 at 4:06 PM, Roger Quadros rog...@ti.com wrote:
Hi Kishon,
On 09/02/2013 06:43 PM, Kishon Vijay
On 09/02/2013 06:43 PM, Kishon Vijay Abraham I wrote:
Adapted dwc3 core to use the Generic PHY Framework. So for init, exit,
power_on and power_off the following APIs are used phy_init(), phy_exit(),
phy_power_on() and phy_power_off().
However using the old USB phy library wont be removed
Hi,
Need some commit log.
cheers,
-roger
On 09/02/2013 06:43 PM, Kishon Vijay Abraham I wrote:
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/omap5.dtsi |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap5.dtsi
On 09/02/2013 06:43 PM, Kishon Vijay Abraham I wrote:
Since now we have a separate folder for phy, move the PHY dt binding
documentation of OMAP to that folder.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
.../devicetree/bindings/{usb/usb-phy.txt = phy/omap-phy.txt}|
Hi,
On 09/02/2013 06:43 PM, Kishon Vijay Abraham I wrote:
renamed struct omap_control_usb to struct omap_control_phy since it can
be used to control PHY of USB, SATA and PCIE. Also moved the driver and
include files under *phy* and made the corresponding changes in the users
of
From: Marek Szyprowski m.szyprow...@samsung.com
On device tree based Samsung SoC platforms (like Exynos) no platform
devices are defined and CONFIG_S3C_DEV_USB_HSOTG is no longer available,
so change the driver dependency to more generic and approperiate
CONFIG_PLAT_SAMSUNG, as the driver can be
These patches add few fixes:
- remove unneeded disconnect from ErlySusp interrupt handling
- remove deprecated driver dependency CONFIG_S3C_DEV_USB_HSOTG
- fix driver unregistration function
- fix protocol stall handling, by enqueue new ep0 request when stalled
- add correct interrput handling in
From: Marek Szyprowski m.szyprow...@samsung.com
After driver conversion to udc_start/udc_stop infrastructure (commit
usb:hsotg:samsung: Use new udc_start and udc_stop callbacks
f65f0f1098) the gadget unregistration function is almost always called
with 'driver' parameter being NULL, what caused
This patch adds two fixes:
- Property halted of s3c_hsotg_ep structure is actually changed when halt is
set/cleared.
- All requests for endpoint are completed when it was halted, and the halt was
cleared by CLEAR_FEATURE, but not when new state is same as previous.
Signed-off-by: Robert
After normal handling of SetupDone interrupt, XferCompl interrupt occurs, and
then we enqueue new setup request. But when ep0 is stalled, there is no
XferCompl, so we have to enqueue setup request immediately after stalling ep.
Otherwise incoming control requests won't be processed correctly.
This patch adds few fixes:
- In s3c_hsotg_write_fifo function PTxFEmp/NPTxFEmp interrupts are enabled
only in shared-fifo mode. In dedicated-fifo mode they should not be used
(when enabled then cause interrupt storm).
- When s3c_hsotg_trytx is called for ep without enqueued request, interrupts
From: Chanho Park chanho61.p...@samsung.com
DWC2 databook indicates if the core sets ErlySusp bit, an idle state has been
detected on the USB for 3 ms. This situation can be occurred when waiting
a request from user daemon. So, we should keep the connection between udc and
gadget even though this
These last six patches should just be one patch to remove xhci_readl().
I know the patch will be pretty long, but it doesn't make sense to break
it up by file.
Sarah Sharp
On Mon, Sep 09, 2013 at 09:03:14PM +0300, Xenia Ragiadakou wrote:
Function xhci_readl() is used to read 32bit xHC registers
We can only reach this spot by breaking out of the scan loop,
so by construction ret 0.
Found by Coverity, in a copy of this file in the Xen sources.
Signed-off-by: Tim Deegan t...@xen.org
Cc: Greg Kroah-Hartman gre...@linuxfoundation.org
Cc: linux-usb@vger.kernel.org
Cc:
On Tue, Sep 03, 2013 at 01:51:55PM -0500, joe M wrote:
Hello Sarah,
Thanks for responding.
I'm the xHCI driver maintainer, can you please Cc me on any future bug
reports for xHCI hosts? Otherwise it gets lost in my mailing list
inbox.
Sure, will do so.
Is your device prepared
On Fri, 9 Aug 2013, Lionel Landwerlin wrote:
Hi there,
I'm playing with 2 small usb webcams, showing up the stream of the
camera with it's plugged in and hiding it when it's unplugged. I'm
basically using 2 external camera + the integrated one.
I've noticed the usb port just become
On Tue, Sep 03, 2013 at 03:46:40PM +0200, Gerd Hoffmann wrote:
Hi,
This patch series enables uas support in the linux kernel. First patch
fixes usb3 streams support in xhci, patches 2-4 improve uas error
handling and patch 5 removes BROKEN from the uas kernel config.
As these depend on
Hello,
We are offering loans to all despite bad credits for a low interest rate of
3%.For more info ,contact us via email fundsfinancialh...@gmail.com
--
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
On Wed, Sep 04, 2013 at 02:47:07PM +0200, Tom Gundersen wrote:
Most of the information in usb.ids is now contained in udev's hwdb. Read the
information from the hwdb instead of usb.ids.
This would allow distributions to no longer ship (most of) usb.ids by default,
but rather keep all the usb
On Wed, Sep 04, 2013 at 02:47:07PM +0200, Tom Gundersen wrote:
Most of the information in usb.ids is now contained in udev's hwdb. Read the
information from the hwdb instead of usb.ids.
This would allow distributions to no longer ship (most of) usb.ids by default,
but rather keep all the usb
On Wed, Aug 07, 2013 at 04:45:51PM -0700, Alexandra Yates wrote:
This patch adds USB2-LPM-Errata for USB2.0 Binary Object Store
Descriptor that support Best Effort Latency Tolerance (BELT),
with the Baseline BESL value, and Deep BESL values. Additionally, it
identifies if a Binary Object Store
On Wed, Sep 04, 2013 at 02:47:08PM +0200, Tom Gundersen wrote:
Also remove usb.ids from the repository. [Note that these were probably
never used by distributions regarless, as most distros ship the usb.ids
directly from upstream.]
Hardcode the usb-spec information that used to be in
On Wed, Aug 07, 2013 at 04:45:50PM -0700, Alexandra Yates wrote:
From: Alexandra Yates alexandra.ya...@linux.intel.com
This patch reports the low power state L1 for ports with attahced USB2
devices. The output will be part of the roothub port status as follows:
ayates@magd:~$ sudo lsusb
On Fri, Sep 13, 2013 at 12:47 AM, Greg Kroah-Hartman
gre...@linuxfoundation.org wrote:
On Wed, Sep 04, 2013 at 02:47:07PM +0200, Tom Gundersen wrote:
Most of the information in usb.ids is now contained in udev's hwdb. Read the
information from the hwdb instead of usb.ids.
This would allow
On Tue, Sep 10, 2013 at 02:03:15AM +0800, Xenia Ragiadakou wrote:
Function xhci_readl() is used to read 32bit xHC registers residing in MMIO
address space. It takes as first argument a pointer to the xhci_hcd although
it does not use it because internally it simply calls readl. This creates
an
39 matches
Mail list logo
