Adding support to enable/disable VBUS controlled by a
regulator, to enable vbus supply on the port.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
Changes from v6:
- Rebased on top of [PATCH v7 1/2] phy: Add new Exynos5 USB 3.0 PHY driver.
drivers/phy/phy-exynos5-usbdrd.c | 32
Add a new driver for the USB 3.0 PHY on Exynos5 series of SoCs.
The new driver uses the generic PHY framework and will interact
with DWC3 controller present on Exynos5 series of SoCs.
Thereby, removing old phy-samsung-usb3 driver and related code
used untill now which was based on usb/phy
GTSYS -
Unit A01, 24/F Gold King Industrial Building,
35-41 Tai Lin Pai Road, Kwai Chung,
Hong Kong
新界葵涌大連排道35-41號金基工業大廈24樓A01室
On Thursday, April 24, 2014 01:07 PM, Peter Chen wrote:
This patch can cover both ULPI DT support version in future and
current version (can fix sasche's problem),
On Fri, 2014-04-25 at 15:53 -0500, Felipe Balbi wrote:
On Thu, Apr 24, 2014 at 01:49:38PM -0300, Fabio Estevam wrote:
On Thu, Apr 24, 2014 at 12:48 PM, Ivan T. Ivanov iiva...@mm-sol.com wrote:
+ motg-vddcx = devm_regulator_get(motg-phy.dev, HSUSB_VDDCX);
+ if
On Fri, 2014-04-25 at 15:53 -0500, Felipe Balbi wrote:
On Thu, Apr 24, 2014 at 09:06:24PM +0400, Sergei Shtylyov wrote:
Hello.
On 04/24/2014 07:48 PM, Ivan T. Ivanov wrote:
From: Ivan T. Ivanov iiva...@mm-sol.com
They could be more than one USB2.0 PHY's on the platform.
Since we have already removed the usage of CONFIG_USB_DEBUG, it is
meaningless that there is still a configuration entry for CONFIG_USB_DEBUG.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/core/Kconfig |7 ---
1 files changed, 0 insertions(+), 7 deletions(-)
diff
Change to use struct device instead of struct platform_device
for some static functions.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Cc: Jingoo Han jg1@samsung.com
Cc: Alan Stern st...@rowland.harvard.edu
---
drivers/usb/host/ehci-exynos.c |5 ++---
1 file changed, 2
Add support to consume phy provided by Generic phy framework.
Keeping the support for older usb-phy intact right now, in order
to prevent any functionality break in absence of relevant
device tree side change for ohci-exynos.
Once we move to new phy in the device nodes for ohci, we can
remove the
Change to use struct device instead of struct platform_device
for some static functions.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Cc: Jingoo Han jg1@samsung.com
Cc: Alan Stern st...@rowland.harvard.edu
---
drivers/usb/host/ohci-exynos.c | 20 +---
1 file
Based and tested on 'usb-next' branch of Greg's usb tree, with relevant
device tree patches[1]
Changes from v2:
- Added two patches in the series for some cleanup.
usb: ohci-exynos: Use struct device instead of platform_device
usb: ehci-exynos: Use struct device instead of platform_device
Based and tested on 'usb-next' branch of Greg's usb tree, with relevant
device tree patches[1]
Changes from v2:
- Added two patches in the series for some cleanup.
usb: ohci-exynos: Use struct device instead of platform_device
usb: ehci-exynos: Use struct device instead of platform_device
On 04/24/2014 09:52 PM, Greg KH wrote:
On Mon, Apr 14, 2014 at 01:46:11PM +0200, Robert Baldyga wrote:
This patchset adds many improvements to extcon class driver and extcon
provider drivers. It changes extcon API to faster and safer by replaceing
function taking extcon and cable names with
Since usb otg fsm implementation is not related to usb phy.
We move it from usb/phy/ to usb/common/, and rename it to
reflect its real meaning.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/common/Makefile|1 +
.../{phy/phy-fsm-usb.c =
Hi Greg,
This patch set creates usb/common for usb common things, and moves
otg fsm implementation from usb/phy/ to usb/common/. I have a
discussion with Felipe about it at below link:
http://www.spinics.net/lists/linux-usb/msg106357.html
Thanks.
Peter Chen (2):
usb: move usb/usb-common.c to
Since we will have more usb-common things, and it will let
usb-common.c be larger and larger, we create a folder named usb/common
for all usb common things.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/Makefile |2 +-
drivers/usb/common/Makefile
On Monday, April 28, 2014 6:25 PM, Vivek Gautam wrote:
Change to use struct device instead of struct platform_device
for some static functions.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Cc: Jingoo Han jg1@samsung.com
Acked-by: Jingoo Han jg1@samsung.com
Best regards,
On Monday, April 28, 2014 6:26 PM, Vivek Gautam wrote:
Change to use struct device instead of struct platform_device
for some static functions.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Cc: Jingoo Han jg1@samsung.com
Acked-by: Jingoo Han jg1@samsung.com
Best regards,
Pci_enable_device() will set device power state to D0,
so it's no need to do it again after call pci_enable_device().
Signed-off-by: Yijing Wang wangyij...@huawei.com
---
drivers/usb/core/hcd-pci.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git
On 04/27/2014 11:11 AM, John Freed wrote:
I hope you don't mind me writing you directly, and if someone else can
handle this better please let me know.
I'm trying to do some backend work on libusb and I notice that the
kernel keeps all the information on the Device Descriptors except for
the
Hi Felipe,
Are you going to merge this examples, or should they be merged through
another tree?
Best regards
Robert Baldyga
Samsung RD Institute Poland
On 02/11/2014 11:43 AM, Robert Baldyga wrote:
This patch adds two example applications showing usage of Asynchronous I/O API
of FunctionFS.
On Mon, Apr 28, 2014 at 02:12:38PM +0800, Peter Chen wrote:
Since we have already removed the usage of CONFIG_USB_DEBUG, it is
meaningless that there is still a configuration entry for CONFIG_USB_DEBUG.
We finally did it? Nice, I didn't realize that last bits were now gone,
thanks for
On Sat, Apr 26, 2014 at 02:10:21AM +0800, Felipe Balbi wrote:
On Fri, Apr 25, 2014 at 02:27:11PM +0530, Pratyush Anand wrote:
On Tue, Apr 22, 2014 at 10:41:06PM +0800, Felipe Balbi wrote:
On Tue, Apr 22, 2014 at 10:46:13AM +0530, Pratyush Anand wrote:
On Tue, Apr 22, 2014 at 12:43:55PM
On 04/25/2014 07:35 PM, Greg KH wrote:
On Fri, Apr 25, 2014 at 07:20:12PM +0300, Mathias Nyman wrote:
Hi Greg
Second try at this xhci fixes series for 3.15-rc usb-linus.
Most of them are very small fixes that didn't make
it to 3.14, sitting and waiting for 3.15-rc1 to come out.
Only the
From: Ivan T. Ivanov iiva...@mm-sol.com
Eliminating global variables allows driver to handle multiple
device instances.
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
---
drivers/usb/phy/phy-msm-usb.c | 82 ---
include/linux/usb/msm_hsusb.h | 3 ++
2
From: Ivan T. Ivanov iiva...@mm-sol.com
New platform uses RBCPR hardware feature, with that voting for
absolute voltage of VDD CX is not required. Hence vote for corner of
VDD CX which uses nominal corner voltage on VDD CX.
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
Cc: Mayank Rana
From: Tim Bird tbird...@gmail.com
Select the secondary PHY using the TCSR register, if phy-num=1
in the DTS (or phy_number is set in the platform data). The
SOC has 2 PHYs which can be used with the OTG port, and this
code allows configuring the correct one.
Note: This resolves the problem I
From: Ivan T. Ivanov iiva...@mm-sol.com
Allow support to use 2nd HSPHY with USB2 Core.
Some platforms may have configuration to allow USB controller
work with any of the two HSPHYs present. By default driver
configures USB core to use primary HSPHY. Add support to allow
user select 2nd HSPHY
From: Ivan T. Ivanov iiva...@mm-sol.com
This fixes following:
WARNING: drivers/usb/phy/built-in.o(.data+0x68): Section mismatch in reference
from the variable msm_otg_driver to the function .init.text:msm_otg_probe()
The variable msm_otg_driver references
the function __init msm_otg_probe()
From: Ivan T. Ivanov iiva...@mm-sol.com
There could be more than one USB2.0 PHY's on the platform.
This will allow all of them to be registered successfully.
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
---
drivers/usb/phy/phy-msm-usb.c | 3 ++-
1 file changed, 2 insertions(+), 1
From: Ivan T. Ivanov iiva...@mm-sol.com
Put the transceiver in non-driving mode. Otherwise host
may not detect soft-disconnection.
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
Cc: Pavankumar Kondeti pkond...@codeaurora.org
---
drivers/usb/phy/phy-msm-usb.c | 18 ++
1 file
From: Tim Bird tbird...@gmail.com
Fix the value used for Parallel Transceiver Select (PTS) for the MSM USB
controller. This is a standard chipidea PORTSC definition, where
a PHY_TYPE of 10b (30) is ULPI and 11b (30) is SERIAL.
Fix the definitions and use them correctly in the driver code.
From: Ivan T. Ivanov iiva...@mm-sol.com
There are no references to 'pclk_src_name' in plaform code,
so it is unused.
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
---
drivers/usb/phy/phy-msm-usb.c | 26 +-
include/linux/usb/msm_hsusb.h | 5 -
2 files changed, 1
From: Ivan T. Ivanov iiva...@mm-sol.com
This fixes following:
WARNING: quoted string split across lines
WARNING: Prefer seq_puts to seq_printf
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
---
drivers/usb/phy/phy-msm-usb.c | 39 ++-
1 file changed, 14
From: Ivan T. Ivanov iiva...@mm-sol.com
On few legacy platforms, USB PHY is having dedicated reset clk.
It is used to reset USB PHY after putting USB PHY into low power
mode and for calibration of USB PHY. Putting USB PHY into low
power mode is causing ulpi read/write timeout as expected. USB PHY
From: Ivan T. Ivanov iiva...@mm-sol.com
Function return negative code on error.
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
---
drivers/usb/phy/phy-msm-usb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/phy/phy-msm-usb.c b/drivers/usb/phy/phy-msm-usb.c
On Mon, Apr 28, 2014 at 02:59:16PM +0300, Mathias Nyman wrote:
On 04/27/2014 11:11 AM, John Freed wrote:
I hope you don't mind me writing you directly, and if someone else can
handle this better please let me know.
I'm trying to do some backend work on libusb and I notice that the
From: Ivan T. Ivanov iiva...@mm-sol.com
Move memory, regulators, clocks and irq allocation to
devm_* variants. Properly check for valid clk handles.
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
---
drivers/usb/phy/phy-msm-usb.c | 187 +++---
1 file
From: Ivan T. Ivanov iiva...@mm-sol.com
Whether regulators are available or not is checked at driver
probe. If they are not available driver will refuse to load,
so no need to check them again.
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
---
drivers/usb/phy/phy-msm-usb.c | 10 --
1
From: Ivan T. Ivanov iiva...@mm-sol.com
Using platform_driver_probe() prevent driver from requesting
probe deferral. Fix this.
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
---
drivers/usb/phy/phy-msm-usb.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
From: Ivan T. Ivanov iiva...@mm-sol.com
Use enum usb_dr_mode and drop default usb_dr_mode from platform data.
USB DT bindings states: dr_mode: ...In case this attribute isn't
passed via DT, USB DRD controllers should default to OTG...,
so remove redundand field.
Signed-off-by: Ivan T. Ivanov
From: Ivan T. Ivanov iiva...@mm-sol.com
Controller could be found on APQ and MSM platforms,
make configuration description more generic.
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
---
drivers/usb/phy/Kconfig | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
From: Ivan T. Ivanov iiva...@mm-sol.com
Allows controller to be specified via device tree.
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
---
.../devicetree/bindings/usb/msm-hsusb.txt | 67
drivers/usb/phy/phy-msm-usb.c | 113 +
From: Ivan T. Ivanov iiva...@mm-sol.com
Using reset framework eliminate need of platform specific
callbacks and enable reset lines to be specified in DT files.
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
---
drivers/usb/phy/phy-msm-usb.c | 29 +
From: Ivan T. Ivanov iiva...@mm-sol.com
Hi,
This is a new version of patches posted earlier[1].
Changes since v7
- Use bulk regulator request function in patch #05
- Fix errors in patch #20 commit message
[1] http://www.spinics.net/lists/linux-arm-msm/msg08997.html
Ivan T. Ivanov (18):
From: Ivan T. Ivanov iiva...@mm-sol.com
Prefix did not bring any useful information. Currently none
of the MSM platforms define these regulators, so it is safe
to rename them.
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
---
drivers/usb/phy/phy-msm-usb.c | 6 +++---
1 file changed, 3
Add the sysconfig class bits for the Super Speed USB
controllers
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm/mach-omap2/omap_hwmod_7xx_data.c
This clock gate description is missing in the older Reference manuals.
It is present on the SoC to provide 960MHz reference clock to the
internal USB PHYs.
Reference: DRA75x_DRA74x_ES1.1_NDA_TRM_vO.pdf, pg. 900,
Table 3-812. CM_COREAON_L3INIT_60M_GFCLK_CLKCTRL
Use l3init_960m_gfclk as parent of
Add wkupclk and refclk information to DT binding information.
Signed-off-by: Roger Quadros rog...@ti.com
---
Documentation/devicetree/bindings/phy/ti-phy.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git a/Documentation/devicetree/bindings/phy/ti-phy.txt
Add USB pinmux information and USB modes
for the USB controllers.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/dra7-evm.dts | 24
1 file changed, 24 insertions(+)
diff --git a/arch/arm/boot/dts/dra7-evm.dts b/arch/arm/boot/dts/dra7-evm.dts
index
Hi,
This series enables the 2 USB ports on the DRA7-evm.
NOTE: USB1 port is hard coded to work in peripheral mode and USB2 port
in host mode. This is due to missing ID pin interrupt in pre ver.E boards.
USB1 port doesn't in peripheral mode out of the box due to missing VBUS
detection
and
Add nodes for the Super Speed USB controllers, omap-control-usb,
USB2 PHY and USB3 PHY devices.
Remove ocp2scp1 address space from hwmod data as it is
now provided via device tree.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/dra7.dtsi | 149
The USB2 PHY driver expects named clocks for wakeup clock
and reference clock. Provide this information for USB2 PHY
nodes in OMAP4 and OMAP5 SoC DTS.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/omap4.dtsi | 2 ++
arch/arm/boot/dts/omap5.dtsi | 2 ++
2 files changed, 4
As clocks might be named differently on multiple platforms, use a generic
name in the driver and allow device tree node to specify the platform
specific clock name.
Signed-off-by: Roger Quadros rog...@ti.com
---
drivers/phy/phy-omap-usb2.c | 8
1 file changed, 4 insertions(+), 4
On Fri, 2014-04-25 at 03:10 +, Peter Chen wrote:
On Thu, 2014-04-24 at 08:38 +0800, Peter Chen wrote:
On Wed, Apr 23, 2014 at 03:28:01PM +0300, Ivan T. Ivanov wrote:
From: Ivan T. Ivanov iiva...@mm-sol.com
This series intend to fix driver, which was broken for a while.
On 4/14/14 4:11 PM, dingu...@altera.com wrote:
From: Dinh Nguyen dingu...@altera.com
The dwc2 IP on the SOCFPGA cannot use the default HW configured
FIFO sizes. The total FIFO depth as read from GHWCFG3 reports 0x1f80 or 8064
32-bit words. But the GRXFSIZ, GNPTXFSIZ, and HPTXFSIZ register
On Mon, 28 Apr 2014, Yijing Wang wrote:
Pci_enable_device() will set device power state to D0,
so it's no need to do it again after call pci_enable_device().
Signed-off-by: Yijing Wang wangyij...@huawei.com
---
drivers/usb/core/hcd-pci.c |1 -
1 files changed, 0 insertions(+), 1
On Mon, 28 Apr 2014, Mathias Nyman wrote:
On 04/27/2014 11:11 AM, John Freed wrote:
I hope you don't mind me writing you directly, and if someone else can
handle this better please let me know.
I'm trying to do some backend work on libusb and I notice that the
kernel keeps all the
On Mon, 28 Apr 2014, Vivek Gautam wrote:
Add support to consume phy provided by Generic phy framework.
Keeping the support for older usb-phy intact right now, in order
to prevent any functionality break in absence of relevant
device tree side change for ohci-exynos.
Once we move to new phy
On Sat, 26 Apr 2014, Peter Münster wrote:
On Tue, Apr 22 2014, Alan Stern wrote:
Here's diag5; it's essentially a subset of diag4. Test it in the same
way.
(Not being able to wake up the system from the keyboard is expected
for diag4. With diag5, you may or may not be able to use
On Mon, Apr 28, 2014 at 04:49:23PM -0400, Zhuang Jin Can wrote:
Adds a debugfs file snapshot to dump dwc3 requests, trbs and events.
you need to explain what are you trying to provide to our users here.
What problem are you trying to solve ?
As ep0 requests are more complex than others. It's
Per reference manuals of Freescale P1020 and P2020 SoCs, USB controller
present in these SoCs has bit 17 of USBx_CONTROL register marked as
Reserved - there is no PHY_CLK_VALID bit there.
Testing for this bit in ehci_fsl_setup_phy() behaves differently on two
P1020RDB boards available here - on
On Mon, Apr 28, 2014 at 05:01:24PM +0300, Roger Quadros wrote:
The USB2 PHY driver expects named clocks for wakeup clock
and reference clock. Provide this information for USB2 PHY
nodes in OMAP4 and OMAP5 SoC DTS.
Signed-off-by: Roger Quadros rog...@ti.com
Reviewed-by: Felipe Balbi
Hi,
On Mon, Apr 28, 2014 at 05:01:23PM +0300, Roger Quadros wrote:
As clocks might be named differently on multiple platforms, use a generic
name in the driver and allow device tree node to specify the platform
specific clock name.
Signed-off-by: Roger Quadros rog...@ti.com
---
On Mon, Apr 28, 2014 at 05:01:25PM +0300, Roger Quadros wrote:
Add wkupclk and refclk information to DT binding information.
Signed-off-by: Roger Quadros rog...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
---
Documentation/devicetree/bindings/phy/ti-phy.txt | 7 +++
1 file changed,
On Mon, Apr 28, 2014 at 05:01:26PM +0300, Roger Quadros wrote:
Add nodes for the Super Speed USB controllers, omap-control-usb,
USB2 PHY and USB3 PHY devices.
Remove ocp2scp1 address space from hwmod data as it is
now provided via device tree.
Signed-off-by: Roger Quadros rog...@ti.com
On Mon, Apr 28, 2014 at 04:29:24PM +0800, Peter Chen wrote:
Since usb otg fsm implementation is not related to usb phy.
We move it from usb/phy/ to usb/common/, and rename it to
reflect its real meaning.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/common/Makefile
On Mon, Apr 28, 2014 at 05:01:27PM +0300, Roger Quadros wrote:
Add USB pinmux information and USB modes
for the USB controllers.
Signed-off-by: Roger Quadros rog...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
---
arch/arm/boot/dts/dra7-evm.dts | 24
1 file
On Mon, 2014-04-28 at 12:03 -0500, Felipe Balbi wrote:
On Mon, Apr 28, 2014 at 09:00:43PM +0400, Sergei Shtylyov wrote:
Hello.
On 04/28/2014 05:34 PM, Ivan T. Ivanov wrote:
From: Ivan T. Ivanov iiva...@mm-sol.com
This fixes following:
WARNING:
Dear valued customer,
Do you need an urgent loan to pay of your bills, invest more on your business,
if yes PREMIUM CAPITAL LOAN offer loan at 3% interest rate. We are fast and
reliable when it comes to loan lending contact email:
premiumcapitall...@hotmail.co.uk for more information.
Contact
On Mon, Apr 28, 2014 at 07:30:26PM +0200, Apelete Seketeli wrote:
Hi Felipe,
On Mon, Apr-14-2014 at 10:12:56 PM +0200, Apelete Seketeli wrote:
Document the process of writing an musb glue layer by taking the
Ingenic JZ4740 glue layer as an example, as it seems more simple than
most glue
On Mon, Apr 28, 2014 at 08:52:48PM +0300, Ivan T. Ivanov wrote:
On Mon, 2014-04-28 at 12:03 -0500, Felipe Balbi wrote:
On Mon, Apr 28, 2014 at 09:00:43PM +0400, Sergei Shtylyov wrote:
Hello.
On 04/28/2014 05:34 PM, Ivan T. Ivanov wrote:
From: Ivan T. Ivanov iiva...@mm-sol.com
Hello.
On 04/28/2014 06:01 PM, Roger Quadros wrote:
Add wkupclk and refclk information to DT binding information.
Signed-off-by: Roger Quadros rog...@ti.com
---
Documentation/devicetree/bindings/phy/ti-phy.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git
On Mon, Apr 28, 2014 at 11:25 AM, Alan Stern st...@rowland.harvard.edu wrote:
On Fri, 25 Apr 2014, Dan Williams wrote:
@@ -4892,11 +4897,17 @@ static void hub_events(void)
/* deal with port status changes */
for (i = 1; i = hdev-maxchild; i++) {
+
On Fri, 25 Apr 2014, Dan Williams wrote:
Here's a second question. I don't know if there's any definitive
answer. What do you think of passing values like hdev, hcd, and
port_dev as arguments, as opposed to re-deriving them from the other
values?
In theory, it could result in
On Fri, 25 Apr 2014, Dan Williams wrote:
@@ -4892,11 +4897,17 @@ static void hub_events(void)
/* deal with port status changes */
for (i = 1; i = hdev-maxchild; i++) {
+ struct usb_port *port_dev = hub-ports[i - 1];
+
On Mon, 2014-04-28 at 12:54 -0500, Felipe Balbi wrote:
On Mon, Apr 28, 2014 at 08:52:48PM +0300, Ivan T. Ivanov wrote:
On Mon, 2014-04-28 at 12:03 -0500, Felipe Balbi wrote:
On Mon, Apr 28, 2014 at 09:00:43PM +0400, Sergei Shtylyov wrote:
Hello.
On 04/28/2014 05:34 PM, Ivan T.
This set contains a few fixes for formatting issues and compile warnings
in UWB. Some of the changes for lines over 80 chars required pulling
deeply nested code into separate functions which makes that patch look
more significant than it really is.
Thomas Pugliese (3):
uwb: whitespace and
Fix variable set but not used warnings in UWB.
Signed-off-by: Thomas Pugliese thomas.pugli...@gmail.com
---
drivers/uwb/beacon.c | 3 ---
drivers/uwb/est.c| 2 --
drivers/uwb/ie-rcv.c | 2 --
3 files changed, 7 deletions(-)
diff --git a/drivers/uwb/beacon.c b/drivers/uwb/beacon.c
index
Comment typo fix.
Signed-off-by: Thomas Pugliese thomas.pugli...@gmail.com
---
drivers/uwb/radio.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/uwb/radio.c b/drivers/uwb/radio.c
index fd23d98..2427e94 100644
--- a/drivers/uwb/radio.c
+++ b/drivers/uwb/radio.c
@@
Fix whitespace and line length issues reported by checkpatch.
Signed-off-by: Thomas Pugliese thomas.pugli...@gmail.com
---
drivers/uwb/drp.c | 294 ++
1 file changed, 166 insertions(+), 128 deletions(-)
diff --git a/drivers/uwb/drp.c
Hi Felipe,
On Mon, Apr-14-2014 at 10:12:56 PM +0200, Apelete Seketeli wrote:
Document the process of writing an musb glue layer by taking the
Ingenic JZ4740 glue layer as an example, as it seems more simple than
most glue layers due to the basic feature set of the JZ4740 USB device
From: linux-usb-ow...@vger.kernel.org
[mailto:linux-usb-ow...@vger.kernel.org] On Behalf Of Felipe Balbi
Sent: Monday, April 28, 2014 8:56 AM
On Mon, Apr 28, 2014 at 04:49:23PM -0400, Zhuang Jin Can wrote:
Adds a debugfs file snapshot to dump dwc3 requests, trbs and events.
snip
+
Alan and Rajaram, thanks for your help. I have not looked at Linux
kernel builds in this detail before. I have been trying to recompile
modules for the Linaro 3.5 kernel that we adopted last year. I can see
now there is no choice but to start building kernels and modules
together. I have
On Wed, 19 Mar 2014, Dan Williams wrote:
Unconditionally wake up the child device when the power session is
recovered.
This address 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
On Mon, Apr 28, 2014 at 1:29 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Wed, 19 Mar 2014, Dan Williams wrote:
Unconditionally wake up the child device when the power session is
recovered.
This address the following scenarios:
1/ The device may need a reset on power-session loss,
On Mon, Apr 28, 2014 at 2:00 PM, Dan Williams dan.j.willi...@intel.com wrote:
On Mon, Apr 28, 2014 at 1:29 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Wed, 19 Mar 2014, Dan Williams wrote:
[..]
But this got me thinking... It looks like the reference to
port_dev-child in
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
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
Changes since v7 [1]:
* Added patch 8 usb: make usb_port flags atomic
* Added patch 15 usb: hub_handle_remote_wakeup() depends on
CONFIG_PM_RUNTIME=y
* Fixed patch 16 usb: resume (wakeup) child device when port is powered
on
- added USB_PORTDEV_WAKE flag to force usb_remote_wakeup() in
The current port name portX is ambiguous. Before adding more port
messages rename ports to hub-device-name-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
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
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.
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 =
Unconditionally wake up the child device when the power session is
recovered.
This address 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 to
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
Before we add another 2 bitfields to the port state, convert it to an
unsigned long and use bitops helpers to manipulate it. This later
enables setting bits to request action without worrying about colliding
updates. In particular, a flag to request that the child device be
woken up when the
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) set pm_qos_no_poweroff to '0' for port1
(1) hub 2-2:1.0: hub_resume
(2) hub 2-2:1.0: port
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
From: Lan Tianyu tianyu@intel.com
describe the mechanisms for controlling port power policy and
discovering the port power state.
Cc: Oliver Neukum oneu...@suse.de
[oliver]: fixes, clarification of wakeup vs port-power-control
Signed-off-by: Lan Tianyu tianyu@intel.com
[sarah]:
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
1 - 100 of 111 matches
Mail list logo
