On Tue, 23 Jun 2015 17:28:46 +0530
Kishon Vijay Abraham I kis...@ti.com wrote:
No functional change. Previously omap_control_phy_power() was used to power
off the PHY during probe. But once PIPE3 driver is adapted to use syscon,
omap_control_phy_power() cannot be used. Hence used
Since 39b2bbe3d715 (gpio: add flags argument to gpiod_get*() functions)
which appeared in v3.17-rc1, the gpiod_get* functions take an additional
parameter that allows to specify direction and initial value for output.
Use this additional parameter and the _optional variant to simplify the
driver
From: Of James Bottomley
Sent: 22 June 2015 18:36
To: Alan Stern
...
Obviously, for a disk with a writeback cache that can't do flush, that
window is much wider and the real solution should be to try to switch
the cache to write through.
I agree. Doing the switch manually (by
Hi Kishon,
On Tue, 23 Jun 2015 17:28:47 +0530
Kishon Vijay Abraham I kis...@ti.com wrote:
Deprecate using phy-omap-control driver to power on/off the PHY and
use *syscon* framework to do the same.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
Hi all,
is that right that setting urb-interval does not work for the xhci
driver? Seems so that the driver (in my case the usbduxsigma.c) needs to
request the xhci_interval and then has to live with that frame rate so
essentially 125us? Is that right?
/Bernd
xhci-ring.c: (I've added a
On Tue, Jun 23, 2015 at 02:56:06PM +0300, Roger Quadros wrote:
+ Kukjin, Stephen,
for board specific USB question.
On Tue, 23 Jun 2015 16:35:49 +0800
Li Jun b47...@freescale.com wrote:
On Tue, Jun 23, 2015 at 10:43:28AM +0300, Roger Quadros wrote:
If the dr_mode was otg for
On Tue, 23 Jun 2015, Ruslan Bilovol wrote:
Change behavior during registration of gadgets and
gadget drivers in udc-core. Instead of previous
approach when for successful probe of usb gadget driver
at least one usb gadget should be already registered
use another one where gadget drivers and
Some of the register names defined here are matching with registers
defined in other places. Like DCR is defined here and DCR is also
a register in mn10300 architecture. So when we are building this with
mn10300, build fails.
To avoid we rename all the registers.
Signed-off-by: Sudip Mukherjee
From: Vivek Bhagat vivek.bhaga...@gmail.com
Date: Sun, 21 Jun 2015 11:41:43 +0530
From d178065c9e3cfa8a45ef537fae7412775339beb0 Mon Sep 17 00:00:00 2001
From: Vivek Kumar Bhagat vivek.bha...@samsung.com
Date: Thu, 11 Jun 2015 07:23:46 -0700
Subject: [PATCH] ax88179_178a: add reset
Hello Gregory Herrero,
The patch d17ee77b3044: usb: dwc2: add controller hibernation
support from Apr 29, 2015, leads to the following static checker
warning:
drivers/usb/dwc2/core.c:77 dwc2_backup_host_registers()
error: scheduling with locks held: 'spin_lock:lock'
Hello Dan Carpenter,
Yousaf Kaukab did a patch to embed those backup registers in struct dwc2_hsotg.
This way, there is no more allocation needed in dwc2_backup_host_registers().
Here is the patch title: usb: dwc2: embed storage for reg backup in struct
dwc2_hsotg
It has been submitted to
Hi all,
is that right that setting urb-interval does not work for the xhci
driver? Seems so that the driver (in my case the usbduxsigma.c) needs to
request the xhci_interval and then has to live with that frame rate so
essentially 125us? Is that right?
/Bernd
xhci-ring.c: (I've added a
On 6/22/2015 4:00 PM, Doug Anderson wrote:
Hi,
On Thu, Jun 4, 2015 at 6:12 AM, Kaukab, Yousaf yousaf.kau...@intel.com
wrote:
Tested-by: Heiko Stuebner he...@sntech.de
-- 8 --
[ 19.799200] BUG: sleeping function called from invalid context at
mm/slab.c:2863
John and Felipe,
On Tue, Jun 23, 2015 at 10:56 AM, John Youn john.y...@synopsys.com wrote:
On 6/22/2015 4:00 PM, Doug Anderson wrote:
Hi,
On Thu, Jun 4, 2015 at 6:12 AM, Kaukab, Yousaf yousaf.kau...@intel.com
wrote:
Tested-by: Heiko Stuebner he...@sntech.de
-- 8
On Tue, Jun 23, 2015 at 02:56:23PM -0700, Doug Anderson wrote:
John and Felipe,
On Tue, Jun 23, 2015 at 10:56 AM, John Youn john.y...@synopsys.com wrote:
On 6/22/2015 4:00 PM, Doug Anderson wrote:
Hi,
On Thu, Jun 4, 2015 at 6:12 AM, Kaukab, Yousaf yousaf.kau...@intel.com
wrote:
+ Kukjin, Stephen,
for board specific USB question.
On Tue, 23 Jun 2015 16:35:49 +0800
Li Jun b47...@freescale.com wrote:
On Tue, Jun 23, 2015 at 10:43:28AM +0300, Roger Quadros wrote:
If the dr_mode was otg for such case and we want OTG disabled then it
is really the DT fault.
Add syscon-phy-power property and remove the deprecated ctrl-module
property from USB PHY dt node.
Since omap_control_usb2phy devicetree node is no longer used,
remove it.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/omap4.dtsi |8 +---
1 file changed, 1
Add syscon-phy-power property and remove the deprecated ctrl-module
property from USB PHY device tree node.
Since am43xx_control_usb2phy1 and am43xx_control_usb2phy2
devicetree nodes are no longer used, remove it.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
Add syscon-phy-power property and remove the deprecated ctrl-module
property from SATA PHY node.
Since omap_control_sata devicetree node is no longer used, remove it.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/omap5.dtsi | 10 +-
1 file changed, 1
Add syscon-otghs property and remove the deprecated ctrl-module
property from MUSB devicetree node.
Since omap_control_usbotg devicetree node is no longer used, remove
it.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/omap4.dtsi |8 +---
1 file changed, 1
Add new device tree node for the control module register space where
PCIe registers are present.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/dra7.dtsi |5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/dra7.dtsi
Add syscon-phy-power property and remove the deprecated ctrl-module
property from USB PHY devicetree nodes.
Since omap_control_usb2phy1, omap_control_usb3phy1 and
omap_control_usb2phy2 devicetree nodes are no longer used, remove it.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
Add syscon-phy-power property and remove the deprecated ctrl-module
property from USB PHY devicetree node.
Since omap_control_usb2phy and omap_control_usb3phy devicetree nodes
are no longer used, remove it.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/omap5.dtsi |
Add syscon-phy-power property and remove the deprecated ctrl-module
property from SATA PHY node. Since omap_control_sata note is no longer
used, remove it.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/dra7.dtsi | 10 +-
1 file changed, 1 insertion(+), 9
Deprecate using phy-omap-control driver to power on/off the PHY and
use *syscon* framework to do the same.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
Documentation/devicetree/bindings/phy/ti-phy.txt | 10 ++-
drivers/phy/phy-ti-pipe3.c | 91
The USB2 PHY2 has a different register map compared to USB2 PHY1
to power on/off the PHY. In order to handle it, add a new
compatible string.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
Documentation/devicetree/bindings/phy/ti-phy.txt |2 ++
drivers/phy/phy-omap-usb2.c
phy-omap-control driver was added when there was no proper
infrastructure for doing control module initializations.
Now with SYSCON framework being added to the kernel, phy-omap-control
shouldn't be needed.
This series is about adapting phy-omap-usb2, phy-ti-pipe3 and omap2430
to use SYSCON
Deprecate using phy-omap-control driver to set PCS value of the PHY
and start using *syscon* framework to do the same.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
Documentation/devicetree/bindings/phy/ti-phy.txt |2 ++
drivers/phy/phy-ti-pipe3.c | 32
No functional change. Previously omap_control_phy_power() was used to power
off the PHY during probe. But once PIPE3 driver is adapted to use syscon,
omap_control_phy_power() cannot be used. Hence used ti_pipe3_power_off
to power off the PHY.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Add syscon-phy-power property and syscon-pcs property which can
be used to perform the control module initializations and remove
the deprecated ctrl-module property from PCIe PHY dt nodes.
Phandle to sysclk clock node is also added to the PCIe PHY node
since some of the syscon initializations is
Deprecate using phy-omap-control driver to power on/off the PHY,
and use *syscon* framework to do the same. This handles
powering on/off the PHY for the USB2 PHYs used in various TI SoCs.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
Documentation/devicetree/bindings/phy/ti-phy.txt |
The USB2 PHY2 has a different register map compared to USB2 PHY1
to power on/off the PHY. In order to handle it, use the new compatible
string ti,dra7x-usb2-phy2 for the second instance of USB2 PHY.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/dra7.dtsi |2 +-
1
No functional change. Previously omap_control_phy_power() was used to power
off the PHY during probe. But once phy-omap-usb2 driver is adapted to
use syscon, omap_control_phy_power() cannot be used. Hence used
omap_usb_power_off to power off the PHY.
Signed-off-by: Kishon Vijay Abraham I
Deprecate using phy-omap-control driver to write to the mailbox register
and start using *syscon* framework to do the same.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
Documentation/devicetree/bindings/usb/omap-usb.txt |7 +-
drivers/usb/musb/omap2430.c|
On Wed, Jun 17, 2015 at 07:40:15PM +0800, Li Jun wrote:
Set gadget's otg capabilities according to controller's capability and otg
properties in device tree.
Signed-off-by: Li Jun jun...@freescale.com
---
drivers/usb/chipidea/core.c | 8
drivers/usb/chipidea/udc.c | 7 ++-
On Wed, Jun 24, 2015 at 11:04:43AM +0800, Peter Chen wrote:
On Wed, Jun 17, 2015 at 07:40:15PM +0800, Li Jun wrote:
Set gadget's otg capabilities according to controller's capability and otg
properties in device tree.
Signed-off-by: Li Jun jun...@freescale.com
---
On Mon, 2015-06-22 at 11:43 +0200, Johan Hovold wrote:
On Thu, Jun 18, 2015 at 06:43:35AM -0500, Peter E. Berger wrote:
From: Peter E. Berger pber...@brimson.com
The io_ti driver fails to download firmware to Edgeport
devices such as the EP/416, even when the on-disk firmware image
On Mon, 2015-06-22 at 12:01 +0200, Johan Hovold wrote:
On Thu, Jun 18, 2015 at 06:43:36AM -0500, Peter E. Berger wrote:
From: Peter E. Berger pber...@brimson.com
When using newer Edgeport devices such as the EP/416, idle ports are
automatically bounced (disconnected and then reconnected)
On Mon, 2015-06-22 at 10:45 +0200, Johan Hovold wrote:
On Thu, Jun 18, 2015 at 06:43:34AM -0500, Peter E. Berger wrote:
From: Peter E. Berger pber...@brimson.com
The io_ti driver fails to download firmware to Edgeport devices such as
the EP/416. One of the problems is that the default 1
On Mon, Jun 22, 2015 at 10:11:35PM +0200, Stefan Agner wrote:
On 2015-06-22 19:26, Johan Hovold wrote:
Instead, hang the gpio chip directly off the usb interface (not the
port), add a new config option, and keep the gpio implementation under
drivers/usb/serial (possibly in its own file
On Fri, Jun 12, 2015 at 09:10:19AM +0200, Uwe Kleine-König wrote:
Since 39b2bbe3d715 (gpio: add flags argument to gpiod_get*() functions)
which appeared in v3.17-rc1, the gpiod_get* functions take an additional
parameter that allows to specify direction and initial value for output.
Introduces the Xen pvUSB frontend. With pvUSB it is possible for a Xen
domU to communicate with a USB device assigned to that domU. The
communication is all done via the pvUSB backend in a driver domain
(usually Dom0) which is owner of the physical device.
The pvUSB frontend is a USB hcd for a
This series adds XEN guest pvUSB support. With pvUSB it is possible to
use physical USB devices from a XEN domain.
The support consists of a frontend in form of a virtual hcd driver in
the unprivileged domU passing I/O-requests to the backend in a driver
domain (usually Dom0). The backend is not
Add the definition of pvUSB protocol used between the pvUSB frontend in
a Xen domU and the pvUSB backend in a Xen driver domain (usually Dom0).
This header was originally provided by Fujitsu for Xen based on Linux
2.6.18.
Changes are:
- adapt to Linux style guide
Signed-off-by: Juergen Gross
Add myself as maintainer for the Xen pvUSB stuff.
Signed-off-by: Juergen Gross jgr...@suse.com
Acked-by: Konrad Rzeszutek Wilk konrad.w...@oracle.com
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index d8afd29..8ef4e83 100644
---
On Mon, 22 Jun 2015 22:36:40 +0800
Li Jun b47...@freescale.com wrote:
On Mon, Jun 22, 2015 at 04:32:56PM +0300, Roger Quadros wrote:
On Mon, 22 Jun 2015 18:45:37 +0800
Li Jun b47...@freescale.com wrote:
On Mon, Jun 22, 2015 at 12:41:22PM +0300, Roger Quadros wrote:
On Thu, 18 Jun
On Tue, Jun 23, 2015 at 10:43:28AM +0300, Roger Quadros wrote:
If the dr_mode was otg for such case and we want OTG disabled then it
is really the DT fault.
It's ID pin detect for dual role switch as many current OTG controllers
have.
not DT fault, its dt only has a dr_mode =
On Thu, Jun 18, 2015 at 05:47:50PM +0530, Sudip Mukherjee wrote:
While building with mn10300 it failed with:
error: expected identifier before '(' token
#define __SYSREG(ADDR, TYPE) (*(volatile TYPE *)(ADDR))
note: in expansion of macro '__SYSREG'
#define DCR __SYSREG(0xc030, u16) /*
On Fri, Jun 19, 2015 at 01:12:36AM +0800, ChengYi He wrote:
put_device is required to release the last reference to the device.
Signed-off-by: ChengYi He chengyihetai...@gmail.com
---
drivers/usb/common/ulpi.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
Hi Doug,
Am Montag, 22. Juni 2015, 16:00:42 schrieb Doug Anderson:
On Thu, Jun 4, 2015 at 6:12 AM, Kaukab, Yousaf yousaf.kau...@intel.com
wrote:
Tested-by: Heiko Stuebner he...@sntech.de
-- 8 --
[ 19.799200] BUG: sleeping function called from invalid
On Wed, Jun 24, 2015 at 11:34:23AM +0800, Li Jun wrote:
On Wed, Jun 24, 2015 at 11:04:43AM +0800, Peter Chen wrote:
On Wed, Jun 17, 2015 at 07:40:15PM +0800, Li Jun wrote:
Set gadget's otg capabilities according to controller's capability and otg
properties in device tree.
On 2015-06-23 11:22, Johan Hovold wrote:
On Mon, Jun 22, 2015 at 10:11:35PM +0200, Stefan Agner wrote:
On 2015-06-22 19:26, Johan Hovold wrote:
Instead, hang the gpio chip directly off the usb interface (not the
port), add a new config option, and keep the gpio implementation under
52 matches
Mail list logo
