Remove 'start_new' variable from dwc3_endpoint_transfer_complete(),
since this variable has not been used.
Signed-off-by: Jingoo Han jg1@samsung.com
---
drivers/usb/dwc3/gadget.c |7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/usb/dwc3/gadget.c
Commit e56e69cc0ff4 (usb: gadget: net2280: Use pr_* function) is
included in today's linux-next (ie, next-20140704).
It contains this odd chunk:
@@ -1566,7 +1563,7 @@ static const struct usb_gadget_ops net2280_ops
On Wed, 2014-07-02 at 17:53 +0200, Stefan Klug wrote:
@@ -1471,6 +1526,57 @@ static int proc_do_submiturb(struct
usb_dev_state
*ps, struct usbdevfs_urb *uurb
}
totlen -= u;
}
+} else if(num_pages) {
+pages =
On Fri, Jul 04, 2014 at 02:09:35AM +0100, Tuomas Tynkkynen wrote:
Hi all,
Here's a second version of the probe order issue series. This time I've
added the USB1 resets to the PHYs, thus replacing the really ugly parts
with something slightly better. Old device trees will still probe
Commit e56e69cc0ff4 (usb: gadget: net2280: Use pr_* function)
includes a editing mistake on one of the #ifdef.
This patch fixes it.
Reported-by: Paul Bolle pebo...@tiscali.nl
Signed-off-by: Ricardo Ribalda Delgado ricardo.riba...@gmail.com
---
drivers/usb/gadget/udc/net2280.c | 2 +-
1 file
My fault. Thank you very much for reporting it. I have just posted the patch
Regards
On Fri, Jul 4, 2014 at 9:37 AM, Paul Bolle pebo...@tiscali.nl wrote:
Commit e56e69cc0ff4 (usb: gadget: net2280: Use pr_* function) is
included in today's linux-next (ie, next-20140704).
It contains this odd
On Fri, Jul 04, 2014 at 01:39:08AM +, Peter Chen wrote:
Yes, it has already implemented at ci_usc_vbus_session.
I see the code path in ci_udc_vbus_session of udc.c to trigger such
an event, but unfortunately it was never possible to run into that
code.
The
The ldousb_reg regulator provides power to the USB1 and USB2
High Speed PHYs.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/dra7-evm.dts | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/dra7-evm.dts b/arch/arm/boot/dts/dra7-evm.dts
index
If probe fails then we need to call pm_runtime_disable() to balance
out the previous pm_runtime_enable() call. Else it will cause
unbalanced pm_runtime_enable() call in the succeding probe call.
This anomaly was observed when the call to devm_phy_create() failed
with -EPROBE_DEFER.
Balance out
phy-supply is a phandle to the regulator that provides power to the
PHY. This regulator is managed during the PHY power on/off sequence
by the phy core driver.
Signed-off-by: Roger Quadros rog...@ti.com
---
Documentation/devicetree/bindings/phy/phy-bindings.txt | 4
1 file changed, 4
Some PHYs can be powered by an external power regulator.
e.g. USB_HS PHY on DRA7 SoC. Make the PHY core support a
power regulator.
Signed-off-by: Roger Quadros rog...@ti.com
---
drivers/phy/phy-core.c | 26 ++
include/linux/phy/phy.h | 2 ++
2 files changed, 28
Prevent resources from being freed twice in case device_add() call
fails within phy_create(). Also use ida_simple_remove() instead of
ida_remove() as we had used ida_simple_get() to allocate the ida.
Signed-off-by: Roger Quadros rog...@ti.com
---
drivers/phy/phy-core.c | 7 ---
1 file
After clarification from the hardware team it was found that
this 1.8V PHY supply can't be switched OFF when SoC is Active.
Since the PHY IPs don't contain isolation logic built in the design to
allow the power rail to be switched off, there is a very high risk
of IP reliability and additional
Hi,
On DRA7-evm, the VDDA_1V8_PHY supply must be always-on for proper functioning
of the PHYs on the SoC.
The 3.3V USB supply (ldousb_reg) can be turned OFF when the High Speed USB PHYs
are not in use. We add regulator support in the PHY framework core to manage
the PHY's regulator during PHY
Resolves kernel crash issue when a USB flash drive is inserted
into USB1 port with USB2 port configured as otg. Removing
else block so that the controller coming up in non-otg mode
doesn't return -ENODEV. Returning ENODEV results in platform
framework unbinding platform-drv from controller
Signed-off-by: Peter Griffin peter.grif...@linaro.org
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 702ca10..269ad3b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1325,6 +1325,7 @@ F:drivers/pinctrl/pinctrl-st.c
F:
This patch documents the device tree documentation required for
the ST usb3 controller glue layer found in STiH407 devices.
Signed-off-by: Giuseppe Cavallaro peppe.cavall...@st.com
Signed-off-by: Peter Griffin peter.grif...@linaro.org
---
Documentation/devicetree/bindings/usb/dwc3-st.txt | 58
This patch adds the ST glue logic to manage the DWC3 HC
on STiH407 SoC family. It manages the powerdown signal,
and configures the internal glue logic and syscfg registers.
Signed-off-by: Giuseppe Cavallaro peppe.cavall...@st.com
Signed-off-by: Peter Griffin peter.grif...@linaro.org
---
This series adds support for the ST glue logic to manage the DWC3 HC
on STiH407 SoC family chipsets.
Peter Griffin (3):
usb: dwc3: add ST dwc3 glue layer to manage dwc3 HC
ARM: dts: sti: Add st-dwc3 devicetree bindings documentation
MAINTAINERS: Add dwc3-st.c file to ARCH/STI architecture
hi Alan:
2014-06-26 23:57 GMT+08:00 Alan Stern st...@rowland.harvard.edu:
On Thu, 26 Jun 2014, loody wrote:
hi all:
I try below flow:
1. plug in usb card reader
2. wait 2 seconds
3. plug in SD card
on ubuntu PC system, the udev can get SD plug in event
but on my embedded system, there
This patch adds support for Exynos3250 SoC to Exynos2USB PHY driver.
Although Exynos3250 has only one device phy interface, the register
layout and all operations that are required to get it enabled are almost
same as on Exynos4x12. The only different is one more register
(REFCLKSEL) which need to
2014-07-04 13:13 GMT+02:00 Peter Griffin:
+Required properties:
+ - compatible : must be st,stih407-dwc3
+ - reg : glue logic base address and USB syscfg ctrl register offest
+ - reg-names : Should be reg-glue and syscfg-reg.
+ - st,syscon: should be phandle to system
2014-07-04 13:13 GMT+02:00 Peter Griffin:
diff --git a/drivers/usb/dwc3/Kconfig b/drivers/usb/dwc3/Kconfig
index 8eb996e..f7b0518 100644
--- a/drivers/usb/dwc3/Kconfig
+++ b/drivers/usb/dwc3/Kconfig
@@ -77,6 +77,15 @@ config USB_DWC3_KEYSTONE
default USB_DWC3
help
From: Abbas Raza abbas_r...@mentor.com
When gadget driver is inserted and OTG is in host mode, interrupts
occur which are not handled by chipidea driver causing following
problem. To avoid this problem, don't allow insertion of gadget
driver in host mode.
root@mx6q:~# echo -n host
On Thu, 2014-07-03 at 18:48 +0530, arun wrote:
Bus 001 Device 031: ID 2001:7d01 D-Link Corp.
The verbose output text file is attached.
2 things i would like to mention:
- As soon as it is inserted , it is 2001:a706. But after sometime (few
seconds) it changes to the above. I guess this is
Oliver Neukum oneu...@suse.de writes:
On Thu, 2014-07-03 at 18:48 +0530, arun wrote:
Bus 001 Device 031: ID 2001:7d01 D-Link Corp.
The verbose output text file is attached.
2 things i would like to mention:
- As soon as it is inserted , it is 2001:a706. But after sometime (few
seconds)
Hi,
While porting an internal BSP (a design based on a at91sam9g20 SoC)
from 3.10 to 3.14, I got flooded with messages like:
~# usb 1-1: new full-speed USB device number 3 using at91_ohci
usb 1-1: ath9k_htc: Firmware htc_9271.fw requested
usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size:
From: Pratyush Anand pratyush.an...@st.com
As best case, a host controller should support U0 to U1 switching for
the devices connected below any tier of hub level supported by usb
specification. Therefore xhci_check_tier_policy should always return
success as default implementation.
A host
From: Pratyush Anand pratyush.an...@st.com
If an xhci platform supports USB3 LPM capability then enable
XHCI_LPM_SUPPORT quirk flag.
Signed-off-by: Pratyush Anand pratyush.an...@st.com
Signed-off-by: Mathias Nyman mathias.ny...@linux.intel.com
---
From: Pratyush Anand pratyush.an...@st.com
To use auto U0-U1/U2 transition by xhci platform device add
(en/dis)able_usb3_lpm_timeout function to the xhci_plat_xhci_driver struct.
Signed-off-by: Pratyush Anand pratyush.an...@st.com
Tested-by: Aymen Bouattay aymen.bouat...@st.com
Signed-off-by:
Hi Greg, Felipe
This patchseries by Pratyush Anand provide LPM support
for the dwc3 xhci hosts.
Patch 4/5 touches dwc3, Felipe already gave feedback on an earlier version but
I can't find an Ack anywhere?
Patch 5/5 touches usb core hub code, not much, but still outside xhci
-Mathias
Pratyush
From: Pratyush Anand pratyush.an...@st.com
When a USB device is disconnected, usb_unbind_interface is called, which
tries to enable and disable LPM. usb_enable_lpm also try to send a
control command SET SEL to the device.
Since device is already disconnected, therefore it does not make sense
to
From: Pratyush Anand pratyush.an...@st.com
All dwc3 based xhci host controller supports USB3.0 LPM functionality.
Therefore enable it in platform data for all dwc3 based xhci device if
DWC3_HOST_USB3_LPM_ENABLE is selected in Kconfig.
Signed-off-by: Pratyush Anand pratyush.an...@st.com
On 2014-07-04 20:26, Bjørn Mork wrote:
Oliver Neukum oneu...@suse.de writes:
On Thu, 2014-07-03 at 18:48 +0530, arun wrote:
Bus 001 Device 031: ID 2001:7d01 D-Link Corp.
The verbose output text file is attached.
2 things i would like to mention:
- As soon as it is inserted , it is 2001:a706.
I've already told him (off the list) to upgrade to Ubuntu 14.04.
Ubuntu 12.04 which is an LTS distro is hopeless behind in drivers and
their usb_modeswitch
version is two and a half years old.
The Ubuntu maintainers seems to have their own definition of LTS.
Not as back as RHEL5 (2.6.18
On 07/01/2014 09:07 AM, Mike Mammarella wrote:
Hi
Can you add xhci debugging by enabling CONFIG_DYNAMIC_DEBUG, and run
`echo -n 'module xhci_hcd =p' /sys/kernel/debug/dynamic_debug/control`
as root,
and send me the output of dmesg.
Without debugging info it's hard to guess what's going
hi all:
when I trace kernel driver source about usb scsi storage driver, I
have below 2 questions:
1. in sd.c - static int sd_probe(struct device *dev)
we use below macro to get scsi_device.
struct scsi_device *sdp = to_scsi_device(dev);
take usb for example, is usb storage
On 07/04/2014 04:44 PM, loody wrote:
2. at the end of sd.c - sd_probe, why we call async_schedule_domain like
below
async_schedule_domain(sd_probe_async, sdkp, scsi_sd_probe_domain);
to finish scsi device initialization?
Couldn't we put what sd_probe_async directly in
On Fri, 4 Jul 2014, Anders Darander wrote:
Hi,
While porting an internal BSP (a design based on a at91sam9g20 SoC)
from 3.10 to 3.14, I got flooded with messages like:
~# usb 1-1: new full-speed USB device number 3 using at91_ohci
usb 1-1: ath9k_htc: Firmware htc_9271.fw requested
usb
On Fri, 4 Jul 2014, loody wrote:
hi all:
when I trace kernel driver source about usb scsi storage driver, I
have below 2 questions:
1. in sd.c - static int sd_probe(struct device *dev)
we use below macro to get scsi_device.
struct scsi_device *sdp = to_scsi_device(dev);
On Tue, Jun 24, 2014 at 07:44:10AM +0100, sundeep subbaraya wrote:
Ping
Thanks,
Sundeep.B.S.
On Tue, Jun 10, 2014 at 5:34 PM, subbaraya.sundeep.bha...@xilinx.com wrote:
From: Subbaraya Sundeep Bhatta sbha...@xilinx.com
Add devicetree bindings for Xilinx axi udc driver.
Am 04.07.2014 18:30, schrieb Alan Stern:
On Fri, 4 Jul 2014, Anders Darander wrote:
Hi,
While porting an internal BSP (a design based on a at91sam9g20 SoC)
from 3.10 to 3.14, I got flooded with messages like:
~# usb 1-1: new full-speed USB device number 3 using at91_ohci
usb 1-1:
This patch fixes the call to ompa_cfg_reg(USB2_SPEED) in the case
that the cpu is a omap16xx and the nwires are not equal to 3.
Signed-off-by: Nicholas Krause xerofo...@gmail.com
---
arch/arm/mach-omap1/usb.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
Hi Marek,
Please see my comments inline.
On 04.07.2014 14:13, Marek Szyprowski wrote:
This patch adds support for Exynos3250 SoC to Exynos2USB PHY driver.
Although Exynos3250 has only one device phy interface, the register
layout and all operations that are required to get it enabled are
Hello.
On 06/25/2014 02:32 PM, Vivek Gautam wrote:
From Sergei Shtylyov sergei.shtyl...@cogentembedded.com
Add the generic PHY support, analogous to the USB PHY support. Intended it to be
used with the PCI EHCI/OHCI drivers and the xHCI platform driver.
Signed-off-by: Sergei Shtylyov
Hello,
The name of the NOP transceiver driver was changed during v3.16
release cycle from usb_phy_gen_xceiv to usb_phy_generic.
The patch that comes as a follow up of this message registers the NOP
transceiver driver before calling usb_get_phy() to avoid issues
related to accessing its data
Following the name change of the nop transceiver driver in commit
4525bee, make sure to register the transceiver driver before calling
usb_get_phy() to avoid issues related to accessing its data structure
while it was not registered.
Signed-off-by: Apelete Seketeli apel...@seketeli.net
---
Hi Daniele,
Thankyou for reviewing.
+config USB_DWC3_ST
+ tristate STMicroelectronics Platforms
+ depends on ARCH_STI OF
+ default USB_DWC3_HOST
+ help
+ STMicroelectronics SoCs chip with one DesignWare Core USB3 IP
+ inside (i.e. STiH407).
48 matches
Mail list logo
