On Wed, Mar 26, 2014 at 1:10 PM, Alan Stern wrote:
> On Wed, 19 Mar 2014, Dan Williams wrote:
>
>> 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:
On Wed, Mar 26, 2014 at 12:44 PM, Alan Stern wrote:
> On Wed, 19 Mar 2014, Dan Williams wrote:
>
>> 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 regardl
Hi Vivek,
I have reviewed v5 without noticing this one, but I think most of the
comments still apply.
Best regards,
Tomasz
On 22.04.2014 13:24, Vivek Gautam wrote:
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
Hi Vivek,
On 22.04.2014 10:03, Vivek Gautam wrote:
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 cod
Sparse warns about the __le16 wValue from the USB SetAddress
command being used without converting it to CPU endianness. Fix
that, and also add a bit of defensive masking of the received
wValue before using it.
Reported-by: Fengguang Wu
Signed-off-by: Paul Zimmerman
---
Greg, please apply this t
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 wrote:
>
> > + motg->vddcx = devm_regulator_get(motg->phy.dev, "HSUSB_VDDCX");
> > + if (IS_ERR(motg->vddcx)) {
> > + dev_err(motg->phy.dev, "unable to get h
On Thu, 24 Apr 2014, Dennis New wrote:
> So, it crashed again after almost a week. But ohci-pci seemed to have
> gotten in an infinite loop, constantly repeating about 30 times per
> second:
>
> [256283.572813] ohci-pci :00:13.1: OHCI SF watchdog triggered
> [256283.572819] ohci-pci :00:1
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"
>
> >They could be more than one USB2.0 PHY's on the platform.
>
>s/They/There/
>
> >This will allow all of them to be registred successf
The NovaTech OrionLXm uses an onboard FTDI serial converter for JTAG and
console access.
Here is the lsusb output:
Bus 004 Device 123: ID 0403:7c90 Future Technology Devices
International, Ltd
Signed-off-by: George McCollister
---
drivers/usb/serial/ftdi_sio.c | 2 ++
drivers/usb/serial/ftd
Dear Arnd Bergmann,
On Fri, 25 Apr 2014 22:01:51 +0200, Arnd Bergmann wrote:
> I think you're doing it the wrong way around: You have a specialized
> version of the generic xhci-plat driver. The normal way to handle this
> is to have a loadable module that contains all the Armada specific
> code
Hi,
On Fri, Apr 25, 2014 at 10:01:51PM +0200, Arnd Bergmann wrote:
> On Friday 25 April 2014 16:07:01 Gregory CLEMENT wrote:
> > @@ -148,6 +149,9 @@ static int xhci_plat_probe(struct platform_device *pdev)
> > if (ret)
> > return ret;
> >
> > + if (of_device_is_comp
On Friday 25 April 2014 16:07:01 Gregory CLEMENT wrote:
> @@ -148,6 +149,9 @@ static int xhci_plat_probe(struct platform_device *pdev)
> if (ret)
> return ret;
>
> + if (of_device_is_compatible(pdev->dev.of_node,
> "marvell,armada-380-xhci"))
> + xhci_
All the "non Gobi" Qualcomm based devices handled by this
driver share a common standard Sierra Wireless specific
layout. Adding code specifically for this layout allow
us to reduce the number of match entries per device from
three to one.
This change will result in a penalty wrt stable backports,
Dan writes:
"The Dell drivers use the same configuration for PIDs:
81A2: Dell Wireless 5806 Gobi(TM) 4G LTE Mobile Broadband Card
81A3: Dell Wireless 5570 HSPA+ (42Mbps) Mobile Broadband Card
81A4: Dell Wireless 5570e HSPA+ (42Mbps) Mobile Broadband Card
81A8: Dell Wireless 5808 Gobi(TM) 4G LTE M
I just have to admit that using the per-interface number matching
here wasn't such a good idea after all. It just does not scale
well when adding new devices, and I think we should break now
before we have added even more redundant match entries.
This series refactors the device layout selecting c
Matching on interface numbers was not such a good idea
for multi-function serial devices after all. It is much
better do create well defined device layouts, allowing
a single match entry per device.
Remove this now unused code.
Signed-off-by: Bjørn Mork
---
drivers/usb/serial/qcserial.c | 7 ---
Preparing for more supported standard device layouts. Keeping
the matching macros unchanged to avoid breaking stable
backporting of new device additions.
Signed-off-by: Bjørn Mork
---
drivers/usb/serial/qcserial.c | 22 --
1 file changed, 16 insertions(+), 6 deletions(-)
dif
That way it's easy for humans looking at dmesg
and humans(?) looking at Databooks.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/gadget.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c
index f0dc0ee..f5adf3f 100644
this makes it slightly easier to read generic CMD
logs. It also helps make sure we're sending proper
parameters for each command.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/gadget.c | 29 +
1 file changed, 29 insertions(+)
diff --git a/drivers/usb/dwc3/gadget.c
Ouch... This didn't apply on top of the other series I just sent. Sorry
about that. New version coming up in a second.
Bjørn (writing too much too fast with only one usable arm - yes, I have
my excuses :-)
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a m
On Fri, Apr 25, 2014 at 02:15:29PM -0500, Felipe Balbi wrote:
> this makes it slightly easier to read link state
> change interrupt logs.
>
> Signed-off-by: Felipe Balbi
> ---
> drivers/usb/dwc3/gadget.c | 44 +---
> 1 file changed, 41 insertions(+), 3 del
this makes it slightly easier to read link state
change interrupt logs.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/gadget.c | 44 +---
1 file changed, 41 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.
Preparing for more supported standard device layouts. Keeping
the matching macros unchanged to avoid breaking stable
backporting of new device additions.
Signed-off-by: Bjørn Mork
---
drivers/usb/serial/qcserial.c | 22 --
1 file changed, 16 insertions(+), 6 deletions(-)
dif
All the "non Gobi" Qualcomm based devices handled by this
driver share a common standard Sierra Wireless specific
layout. Adding code specifically for this layout allow
us to reduce the number of match entries per device from
three to one.
This change will result in a penalty wrt stable backports,
Matching on interface numbers was not such a good idea
for multi-function serial devices after all. It is much
better do create well defined device layouts, allowing
a single match entry per device.
Remove this now unused code.
Signed-off-by: Bjørn Mork
---
drivers/usb/serial/qcserial.c | 7 ---
I just have to admit that using the per-interface number matching
here wasn't such a good idea after all. It just does not scale
well when adding new devices, and I think we should break now
before we have added even more redundant match entries.
This series refactors the device layout selecting c
Dan writes:
"The Dell drivers use the same configuration for PIDs:
81A2: Dell Wireless 5806 Gobi(TM) 4G LTE Mobile Broadband Card
81A3: Dell Wireless 5570 HSPA+ (42Mbps) Mobile Broadband Card
81A4: Dell Wireless 5570e HSPA+ (42Mbps) Mobile Broadband Card
81A8: Dell Wireless 5808 Gobi(TM) 4G LTE M
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 +0800, Felipe Balbi wrote:
> > > > On Tue, Apr 22, 2014 at 09:
Hello.
On 04/25/2014 06:07 PM, Gregory CLEMENT wrote:
Extend the compatible string list with armada-380-xhci. It is used to
describe xhci controller which is in the Armada 38x SoCs.
Signed-off-by: Gregory CLEMENT
---
Documentation/devicetree/bindings/usb/usb-xhci.txt | 3 ++-
1 file chan
On Fri, Apr 25, 2014 at 09:35:05AM -0700, Greg KH wrote:
> On Fri, Apr 25, 2014 at 07:20:12PM +0300, Mathias Nyman wrote:
> > Hi Greg
> >
> >
Dan writes:
"The Dell drivers use the same configuration for PIDs:
81A2: Dell Wireless 5806 Gobi(TM) 4G LTE Mobile Broadband Card
81A3: Dell Wireless 5570 HSPA+ (42Mbps) Mobile Broadband Card
81A4: Dell Wireless 5570e HSPA+ (42Mbps) Mobile Broadband Card
81A8: Dell Wireless 5808 Gobi(TM) 4G LTE M
>From Lenovo Windows driver.
Signed-off-by: Bjørn Mork
---
drivers/net/usb/qmi_wwan.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/usb/qmi_wwan.c b/drivers/net/usb/qmi_wwan.c
index e3458e3c44f1..f4c9290aa117 100644
--- a/drivers/net/usb/qmi_wwan.c
+++ b/drivers/net/usb/qmi_wwa
Adding some new and some old QMI devices. A similar series for
usb-serial support will be posted as well.
These new device ID patches should also go to all maintained stable kernels
where they apply. I believe that should be stable-3.10 and newer.
Bjørn Mork (7):
net: qmi_wwan: add Sierra Wir
>From Sierra Wireless' "USB Driver Developer's Guide"
Signed-off-by: Bjørn Mork
---
drivers/net/usb/qmi_wwan.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/net/usb/qmi_wwan.c b/drivers/net/usb/qmi_wwan.c
index f4c9290aa117..60a95ab243d6 100644
--- a/drivers/net/usb/qmi_wwan.c
+
>From https://bug726613.bugzilla-attachments.gnome.org/attachment.cgi?id=272246
Signed-off-by: Bjørn Mork
---
drivers/net/usb/qmi_wwan.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/usb/qmi_wwan.c b/drivers/net/usb/qmi_wwan.c
index 60a95ab243d6..336b5375b00b 100644
--- a/drive
A number of older CMOTech modems are based on Qualcomm
chips and exporting a QMI/wwan function.
Reported-by: Lars Melin
Signed-off-by: Bjørn Mork
---
drivers/net/usb/qmi_wwan.c | 16
1 file changed, 16 insertions(+)
diff --git a/drivers/net/usb/qmi_wwan.c b/drivers/net/usb/qmi
Device interface layout:
0: ff/ff/ff - serial
1: ff/00/00 - serial AT+PPP
2: ff/ff/ff - QMI/wwan
3: 08/06/50 - storage
Signed-off-by: Bjørn Mork
---
drivers/net/usb/qmi_wwan.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/usb/qmi_wwan.c b/drivers/net/usb/qmi_wwan.c
index 127b74
Device interface layout:
0: ff/ff/ff - serial
1: ff/ff/ff - serial AT+PPP
2: 08/06/50 - storage
3: ff/ff/ff - serial
4: ff/ff/ff - QMI/wwan
Reported-by: Julio Araujo
Signed-off-by: Bjørn Mork
---
drivers/net/usb/qmi_wwan.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/usb/qmi_
Device interface layout:
0: ff/ff/ff - serial
1: ff/ff/ff - serial AT+PPP
2: 08/06/50 - storage
3: ff/ff/ff - serial
4: ff/ff/ff - QMI/wwan
Cc:
Reported-by: Julio Araujo
Signed-off-by: Bjørn Mork
---
drivers/usb/serial/option.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/us
A number of older CMOTech modems are based on Qualcomm
chips. The blacklisted interfaces are QMI/wwan.
Reported-by: Lars Melin
Cc:
Signed-off-by: Bjørn Mork
---
drivers/usb/serial/option.c | 74 ++---
1 file changed, 70 insertions(+), 4 deletions(-)
di
>From Sierra Wireless' "USB Driver Developer's Guide"
Cc:
Signed-off-by: Bjørn Mork
---
drivers/usb/serial/qcserial.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/usb/serial/qcserial.c b/drivers/usb/serial/qcserial.c
index 662235240f3f..1d1bc9b41337 100644
--- a/drivers/usb/se
>From Lenovo Windows driver.
Cc:
Signed-off-by: Bjørn Mork
---
drivers/usb/serial/qcserial.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/usb/serial/qcserial.c b/drivers/usb/serial/qcserial.c
index 968a40201e5f..662235240f3f 100644
--- a/drivers/usb/serial/qcserial.c
+++ b/dri
>From https://bug726613.bugzilla-attachments.gnome.org/attachment.cgi?id=272246
Cc:
Signed-off-by: Bjørn Mork
---
drivers/usb/serial/qcserial.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/usb/serial/qcserial.c b/drivers/usb/serial/qcserial.c
index 1d1bc9b41337..7ed681a714a5 1
Device interface layout:
0: ff/ff/ff - serial
1: ff/00/00 - serial AT+PPP
2: ff/ff/ff - QMI/wwan
3: 08/06/50 - storage
Cc:
Signed-off-by: Bjørn Mork
---
drivers/usb/serial/option.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/usb/serial/option.c b/drivers/usb/serial/option.c
i
Adding some new and some old Qualcomm based devices. All these also
support QMI and a similar series for qmi_wwan will be posted as well.
Bjørn Mork (6):
usb: qcserial: add Sierra Wireless EM7355
usb: qcserial: add Sierra Wireless MC73xx
usb: qcserial: add Sierra Wireless MC7305/MC7355
us
On Fri, Apr 25, 2014 at 07:20:12PM +0300, Mathias Nyman wrote:
> Hi Greg
>
>
>
> Second try at th
Hi Greg
Second try at this xhci fixes series for 3.15-rc usb-linus.
From: Julius Werner
We have observed a rare cycle state desync bug after Set TR Dequeue
Pointer commands on Intel LynxPoint xHCs (resulting in an endpoint that
doesn't fetch new TRBs and thus an unresponsive USB device). It always
triggers when a previous Set TR Dequeue Pointer command has set th
From: Denis Turischev
The same issue like with Panther Point chipsets. If the USB ports are
switched to xHCI on shutdown, the xHCI host will send a spurious interrupt,
which will wake the system. Some BIOS have work around for this, but not all.
One example is Compulab's mini-desktop, the Intense
On Fri, Apr 25, 2014 at 04:07:12PM +0200, Gregory CLEMENT wrote:
> The Armada 375 SoC comes with an USB2 host and device controller and
> an USB3 controller. The USB cluster control register allows to manage
> common features of both USB controllers.
>
> Signed-off-by: Gregory CLEMENT
> ---
> ar
On Thu, 24 Apr 2014, Matteo Fortini wrote:
> After some time, we finally had another hangup on kernel 3.14.
>
> @Alan: Here's the info we got in the files you mentioned. At any rate,
> we're keeping the board in the same state so that we can run/produce any
> other needed info.
>
> http://past
From: Igor Gnatenko
After suspend another Renesas PCI-X USB 3.0 card doesn't work.
[root@fedora-20 ~]# lspci -vmnnd 1912:
Device: 03:00.0
Class: USB controller [0c03]
Vendor: Renesas Technology Corp. [1912]
Device: uPD720202 USB 3.0 Host Controller [0015]
SVendor:Renesas Technology Corp.
On Fri, Apr 25, 2014 at 06:07:05PM +0200, Andrew Lunn wrote:
> On Fri, Apr 25, 2014 at 04:07:12PM +0200, Gregory CLEMENT wrote:
> > The Armada 375 SoC comes with an USB2 host and device controller and
> > an USB3 controller. The USB cluster control register allows to manage
> > common features of b
From: David Cohen
When CONFIG_PCI and CONFIG_PM are not selected, xhci.c gets this
warning:
drivers/usb/host/xhci.c:409:13: warning: ‘xhci_msix_sync_irqs’ defined
but not used [-Wunused-function]
Instead of creating nested #ifdefs, this patch fixes it by defining the
xHCI PCI stubs as inline.
T
On Fri, Apr 25, 2014 at 04:07:03PM +0200, Gregory CLEMENT wrote:
> The Marvell Armada 38x SoCs contain two xHCI host. This commit adds
> the Device Tree description of those interfaces at the SoC level, and
> also enables the two USB3 ports on the Armada 385 DB platform and one
> USB3 port on the A
> > +* We can't use usb2 and usb3 in the same time, so let's
> > +* disbale usb2 and complain about it to the user askinf
>
> typos: disable, asking
And it should be "at the same time", not in.
Andrew
--
To unsubscribe from this list: send the line "un
On Fri, Apr 25, 2014 at 04:07:00PM +0200, Gregory CLEMENT wrote:
> Some platform (such as the Armada 38x ones) can gate the clock of
> their USB controller. This patch add the support for the clock, by
> enabling them during probe and disabling them on remove.
>
> As not all platforms have clock s
On Apr 25, Gregory CLEMENT wrote:
> The Armada 375 SoC comes with an USB2 host and device controller and
> an USB3 controller. The USB cluster control register allows to manage
> common features of both USB controllers.
>
> Signed-off-by: Gregory CLEMENT
> ---
> arch/arm/mach-mvebu/Makefile
Fix an intermittent failure when changing channels and report better
errors during the channel change process.
Thomas Pugliese (2):
uwb: fix channel change failure
uwb: add error messages when reservation establish fails
drivers/uwb/beacon.c | 4 +++-
drivers/uwb/rsv.c| 21
Make the transition to the UWB_RSV_STATE_NONE state synchronous so that
there is not a race between uwb_rsv_terminate and uwb_rsv_establish.
uwb_rsv_terminate would set the rsv->state to UWB_RSV_STATE_NONE but did
not release the stream resource until a 320ms timeout had expired. If a
user cal
Add better error messages during the channel change/reservation establish
process.
Signed-off-by: Thomas Pugliese
---
drivers/uwb/beacon.c | 4 +++-
drivers/uwb/rsv.c| 14 --
2 files changed, 15 insertions(+), 3 deletions(-)
diff --git a/drivers/uwb/beacon.c b/drivers/uwb/beac
On Fri, Apr 25, 2014 at 09:54:33AM -0400, Alan Stern wrote:
> On Fri, 25 Apr 2014, Li Zhong wrote:
>
> > > I don't get why try_module_get() matters here. We can't call into
> > > ->store if the object at hand is already destroyed and the underlying
> > > module can't go away if the target device
On Fri, Apr 25, 2014 at 01:36:25PM +, David Laight wrote:
> From: Johan Hovold
> > During firmware download the device expects memory addresses in
> > big-endian byte order. As the wIndex parameter which hold the address is
> > sent in little-endian byte order regardless of host byte order, we
On Fri, Apr 25, 2014 at 04:07:01PM +0200, Gregory CLEMENT wrote:
> For the Armada 38x SoCs which come with an xhci controller, specific
> initialization must be done during probe related to the MBus windows
> configuration. This patch adds the support of this quirk.
>
> Signed-off-by: Gregory CLEM
Hi,
On Fri, Apr 25, 2014 at 04:07:00PM +0200, Gregory CLEMENT wrote:
> Some platform (such as the Armada 38x ones) can gate the clock of
> their USB controller. This patch add the support for the clock, by
> enabling them during probe and disabling them on remove.
>
> As not all platforms have cl
On Fri, Apr 25, 2014 at 04:06:59PM +0200, Gregory CLEMENT wrote:
> Sorting the headers in alphabetic order will help to reduce the conflict
> when adding new headers later.
>
> Signed-off-by: Gregory CLEMENT
> ---
Acked-by: Felipe Balbi
> drivers/usb/host/xhci-plat.c | 6 +++---
> 1 file chan
On 25/04/2014 16:44, Gregory CLEMENT wrote:
> On 25/04/2014 16:15, Thomas Petazzoni wrote:
>> Dear Gregory CLEMENT,
>>
>> On Fri, 25 Apr 2014 16:07:00 +0200, Gregory CLEMENT wrote:
>>> Some platform (such as the Armada 38x ones) can gate the clock of
>>> their USB controller. This patch add the sup
On Fri, 25 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 p
On 25/04/2014 16:15, Thomas Petazzoni wrote:
> Dear Gregory CLEMENT,
>
> On Fri, 25 Apr 2014 16:07:00 +0200, Gregory CLEMENT wrote:
>> Some platform (such as the Armada 38x ones) can gate the clock of
>> their USB controller. This patch add the support for the clock, by
>> enabling them during pro
I'm working with a line discipline in v3.11.10.5 in Ubuntu 12.04 LTS.
The kernel has been modified to use a HZ of 1000. CONFIG_HZ_1000=y and
CONFIG_HZ=1000 in .config.
I have a B&B USOPTL4 RS485 to USB converter connected, I have
usb-serial loaded and mos7840 loaded (CONFIG_USB_SERIAL=m and
CONFIG
On Fri, 25 Apr 2014, Vivek Gautam wrote:
> From: Kamil Debski
>
> Add the phy provider, supplied by new Exynos-usb2phy using
> 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
Sorting the headers in alphabetic order will help to reduce the conflict
when adding new headers later.
Signed-off-by: Gregory CLEMENT
---
drivers/usb/host/xhci-plat.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/host/xhci-plat.c b/drivers/usb/host/xhci-p
For the Armada 38x SoCs which come with an xhci controller, specific
initialization must be done during probe related to the MBus windows
configuration. This patch adds the support of this quirk.
Signed-off-by: Gregory CLEMENT
---
drivers/usb/host/Kconfig | 7 +
drivers/usb/host/Makefi
On Fri, Apr 25, 2014 at 04:07:00PM +0200, Gregory CLEMENT wrote:
> +#if defined(CONFIG_HAVE_CLK)
> +static int try_enable_clk(struct platform_device *pdev)
> +{
> + struct clk *clk = devm_clk_get(&pdev->dev, NULL);
> +
> + /* Not all platforms have a clk so it is not an error if the clock
>
Extend the compatible string list with armada-380-xhci. It is used to
describe xhci controller which is in the Armada 38x SoCs.
Signed-off-by: Gregory CLEMENT
---
Documentation/devicetree/bindings/usb/usb-xhci.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentatio
Dear Gregory CLEMENT,
On Fri, 25 Apr 2014 16:07:01 +0200, Gregory CLEMENT wrote:
> +#define USB3_MAX_WINDOWS 4
> +#define USB3_WIN_CTRL(w) (0x0 + ((w) * 8))
> +#define USB3_WIN_BASE(w) (0x4 + ((w) * 8))
> +
> +static void __init mv_usb3_conf_mbus_windows(void __iomem *base,
> +
The Marvell Armada 38x SoCs contain two xHCI host. This commit adds
the Device Tree description of those interfaces at the SoC level, and
also enables the two USB3 ports on the Armada 385 DB platform and one
USB3 port on the Armada 385 RD platforms.
Signed-off-by: Gregory CLEMENT
---
arch/arm/bo
Some platform (such as the Armada 38x ones) can gate the clock of
their USB controller. This patch add the support for the clock, by
enabling them during probe and disabling them on remove.
As not all platforms have clock support then enabling and disabling
the clocks have been placed in separate
The Marvell Armada 38x platform needs the xhci_mvebu driver enabled
for the xHCI USB hosts, so this commit enables the corresponding
Kconfig option in mvebu_v7_defconfig.
Signed-off-by: Gregory CLEMENT
---
arch/arm/configs/mvebu_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/ar
This patch add the selection of the config symbol to build the USB3
support for Armada 38x.
Signed-off-by: Gregory CLEMENT
---
arch/arm/mach-mvebu/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/mach-mvebu/Kconfig b/arch/arm/mach-mvebu/Kconfig
index 3f73eecbcfb0..7960f218702
Dear Gregory CLEMENT,
On Fri, 25 Apr 2014 16:07:00 +0200, Gregory CLEMENT wrote:
> Some platform (such as the Armada 38x ones) can gate the clock of
> their USB controller. This patch add the support for the clock, by
> enabling them during probe and disabling them on remove.
>
> As not all platf
The Marvell Armada 38x platform needs the xhci_mvebu driver enabled
for the xHCI USB hosts, so this commit enables the corresponding
Kconfig option in multi_v7_defconfig.
Signed-off-by: Gregory CLEMENT
---
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/ar
On Fri, Apr 25, 2014 at 03:19:59PM +0200, Robert Baldyga wrote:
> On 04/22/2014 09:51 PM, Mark Brown wrote:
> >> .../devicetree/bindings/extcon/extcon-adc-jack.txt | 60
> >> +++
> >> .../devicetree/bindings/extcon/extcon-arizona.txt | 47 +++
> >> .../devicetree
For the Armada 375 SoC which comes with an xhci controller. Currently
the quirk is the same that the Armada 380/385 one, but by introducing
a new compatible string it will allow to make the driver evolve
seamless.
Signed-off-by: Gregory CLEMENT
---
drivers/usb/host/xhci-plat.c | 4
1 file c
Armada 375 comes with an USB2 host and device controller and an USB3
controller. The USB cluster control register allows to manage common
features of both USB controllers.
Signed-off-by: Gregory CLEMENT
---
.../devicetree/bindings/arm/armada-375-usb-cluster.txt | 17 +
1 file ch
On Armada 375, the USB cluster allows to control the cluster composed
of the USB2 and USB3 host controllers.
Signed-off-by: Gregory CLEMENT
---
arch/arm/boot/dts/armada-375.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/armada-375.dtsi
b/arch/arm/boot/dts/armada
Extend the compatible string list with armada-375-xhci. It is used to
describe xhci controller which is in the Armada 375 SoC.
Signed-off-by: Gregory CLEMENT
---
Documentation/devicetree/bindings/usb/usb-xhci.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation
This commit adds the support for the USB3 controller in the Armada 375
SoC. The following things have been taken in consideration:
- The usb3-controller node has to be *outside* of the internal-regs{}
node, because this device needs to access special windows.
- The usb3-controller node has o
This patch add the selection of the config symbol to build the USB3
support for Armada 375.
Signed-off-by: Gregory CLEMENT
---
arch/arm/mach-mvebu/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/mach-mvebu/Kconfig b/arch/arm/mach-mvebu/Kconfig
index 7960f218702b..95afc7677ee
In order to enable the USB3 host controller on the Armada 375 DB
platform, we need to create a ranges at the soc node level to describe
the special static window for USB3.
Signed-off-by: Gregory CLEMENT
---
arch/arm/boot/dts/armada-375-db.dts | 10 --
1 file changed, 8 insertions(+), 2 d
The Armada 375 SoC comes with an USB2 host and device controller and
an USB3 controller. The USB cluster control register allows to manage
common features of both USB controllers.
Signed-off-by: Gregory CLEMENT
---
arch/arm/mach-mvebu/Makefile | 2 +-
arch/arm/mach-mvebu/usb-cluster.c | 96
The Marvell Armada 375 SoC contains one EHCI host. This commit adds
the Device Tree description of this interface at the SoC level.
Signed-off-by: Gregory CLEMENT
---
arch/arm/boot/dts/armada-375.dtsi | 18 ++
1 file changed, 18 insertions(+)
diff --git a/arch/arm/boot/dts/armad
The Marvell Armada 38x SoCs contain one EHCI host. This commit adds
the Device Tree description of this interface at the SoC level, and
also enables the USB2 port on the Armada 385 DB platform.
Signed-off-by: Gregory CLEMENT
---
arch/arm/boot/dts/armada-385-db.dts | 4
arch/arm/boot/dts/arm
Hello,
This patch set adds the USB support for the Armada 38x Armada
375. These SoCs use an xHCI but still need specific initialization,
mainly to setup the windows memory on the mbus. They also use the same
controller that the other mvebu SoC for EHCI.
Since the 1st version this patch set add xH
On Fri, 25 Apr 2014, Li Zhong wrote:
> > No, this isn't self removal. The driver-attribute (not device-attribute)
> > store operation simply grabs a lock that is also held while the driver
> > is being deregistered at module unload. Taking a reference to the module
> > in this case will prevent de
On Fri, 25 Apr 2014, Li Zhong wrote:
> > I don't get why try_module_get() matters here. We can't call into
> > ->store if the object at hand is already destroyed and the underlying
> > module can't go away if the target device is still alive.
> > try_module_get() doesn't actually protect the obje
From: Johan Hovold
> During firmware download the device expects memory addresses in
> big-endian byte order. As the wIndex parameter which hold the address is
> sent in little-endian byte order regardless of host byte order, we need
> to use swab16 rather than cpu_to_be16.
That doesn't sound corr
During firmware download the device expects memory addresses in
big-endian byte order. As the wIndex parameter which hold the address is
sent in little-endian byte order regardless of host byte order, we need
to use swab16 rather than cpu_to_be16.
Also make sure to handle the struct ti_i2c_desc si
On 04/22/2014 09:51 PM, Mark Brown wrote:
> On Mon, Apr 14, 2014 at 01:46:12PM +0200, Robert Baldyga wrote:
>
> That's quite some CC list you've got there, and the mail seems a bit
> corrupted too (it confused my MUA).
>
>> This patch adds extcon devicetree bindings. Documentation describes in
>
This patch adds sysreg-syscon node to exynos5250 and exynos5420 device
tree, to access System Register's registers using syscon driver.
Signed-off-by: Kamil Debski
[gautam.vi...@samsung.com: Split this syreg-syscon dts entry from
dts: Add usb2phy to Exynos 5250 patch]
[gautam.vi...@samsung.com: a
1 - 100 of 114 matches
Mail list logo
