On Wed, Aug 27, 2014 at 05:26:37AM +0800, Felipe Balbi wrote:
Hi Felipe,
> Hi,
>
> On Tue, Aug 26, 2014 at 09:21:55PM +, Paul Zimmerman wrote:
> > > From: Felipe Balbi [mailto:ba...@ti.com]
> > > Sent: Tuesday, August 26, 2014 1:42 PM
> > >
> > > On Fri, Aug 22, 2014 at 04:56:46PM -0500, Fe
dep->endpoint.desc is checked at the beginning of
dwc3_gadget_ep_queue(), but after that it may be set to NULL
by another thread and then accessed again in dwc3_gadget_ep_queue().
This will lead to kernel oops.
Expand spinlock protection area to aviod race condition.
Signed-off-by: Zhuang Jin Can
(2014/09/02 8:39), Simon Horman wrote:
> On Mon, Sep 01, 2014 at 06:40:50PM +0200, Geert Uytterhoeven wrote:
>> On Mon, Sep 1, 2014 at 4:24 PM, Bartlomiej Zolnierkiewicz
>> wrote:
>>> Renesas USBHS controller support should be available only on
>>> Renesas ARM SoCs and SuperH architecture.
>>>
>>>
Hi Geert,
(2014/08/30 4:31), Geert Uytterhoeven wrote:
> If NO_DMA=y:
>
> drivers/built-in.o: In function `usbhsg_dma_map_ctrl':
> mod_gadget.c:(.text+0x53b226): undefined reference to `usb_gadget_map_request'
> mod_gadget.c:(.text+0x53b242): undefined reference to
> `usb_gadget_unmap_request'
>
On Fri, Aug 22, 2014 at 02:31:18PM +0530, Pratyush Anand wrote:
> On Tue, Aug 19, 2014 at 09:51:51AM +0800, Peter Chen wrote:
> > Changes for v3:
> > - Add possible role switch for unsupported HNP capable OTG B-peripheral,
> > see USB OTG & EH 2.0 spec page 38, this feature was deleted wrongly
> >
This driver supports other SoCs, but they need boards/Soc depend code.
So, this patch adds device tree support for R-Car H2 and M2 initially.
Signed-off-by: Yoshihiro Shimoda
Acked-by: Kuninori Morimoto
---
drivers/usb/renesas_usbhs/common.c | 44
1 file c
Document the device tree bindings for the Renesas USBHS controller.
Signed-off-by: Yoshihiro Shimoda
Acked-by: Kuninori Morimoto
---
.../devicetree/bindings/usb/renesas_usbhs.txt | 24
1 file changed, 24 insertions(+)
create mode 100644 Documentation/devicetree/bind
This driver supports other SoCs, but they need boards/Soc depend code.
So, this patch adds device tree support for R-Car H2 and M2 initially.
Changes from v2:
- Add "Acked-by: Kuninori Morimoto ".
Changes from v1:
- Change an optional property name from "buswait_bwait" to "buswait" in
patch
On Tue, Sep 2, 2014 at 8:07 PM, Felipe Balbi wrote:
> On Mon, Sep 01, 2014 at 01:30:21PM +0530, Vivek Gautam wrote:
>> On Thu, Aug 28, 2014 at 8:36 PM, Daniele Forsi wrote:
>> > 2014-08-28 10:02 GMT+02:00 Vivek Gautam:
>> >
>> >> This USB 3.0 PHY controller is also present on Exynos7
>> >> platfo
On Fri, Aug 29, 2014 at 12:58 AM, Felipe Balbi wrote:
> On Thu, Aug 28, 2014 at 01:31:59PM +0530, Vivek Gautam wrote:
>> The Exynos-DWC3 USB 3.0 DRD controller is also present on
>> Exynos7 platform, so adding the dependency on ARCH_EXYNOS7
>> for this driver.
>>
>> Signed-off-by: Vivek Gautam
>>
On Tue, Sep 02, 2014 at 03:25:05PM -0400, Alan Stern wrote:
> On Tue, 2 Sep 2014, Felipe Balbi wrote:
>
> > > You know, more and more it seems like this ought to be handled by the
> > > UDC core. There are two conditions for turning on the pullup: Vbus
> > > must be active, and the gadget's funct
On Tue, Sep 02, 2014 at 12:02:03PM -0400, Alan Stern wrote:
> On Tue, 2 Sep 2014, Felipe Balbi wrote:
>
> > On Tue, Sep 02, 2014 at 11:32:52AM -0400, Alan Stern wrote:
> > > On Fri, 29 Aug 2014, Felipe Balbi wrote:
> > >
> > > > > I still have some old patch files lying around, adding reset callb
Exchange the location of rtl8152_set_mac_address() and
set_ethernet_addr(). Then, the set_ethernet_addr() could
set the MAC address by calling rtl8152_set_mac_address()
later.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 34 +-
1 file changed, 17 insert
If the hw doesn't have a valid MAC address, give a random one and
set it to the hw.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 35 ---
1 file changed, 20 insertions(+), 15 deletions(-)
diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/r8152.c
in
If the interface has invalid MAC address, it couldn't
be used. In order to let it work normally, give a
random one.
v2:
Use "%pM" format specifier for printing a MAC address.
Hayes Wang (2):
r8152: change the location of rtl8152_set_mac_address
r8152: use eth_hw_addr_random
drivers/net/us
On Fri, Aug 29, 2014 at 1:50 PM, Felipe Balbi wrote:
> Hi,
>
> On Wed, Aug 27, 2014 at 02:58:30PM -0700, Todd Poynor wrote:
>> On Fri, Aug 22, 2014 at 10:12 AM, Felipe Balbi wrote:
>> ...
>> > you never explain why this is needed and you have also added some
>> > information to commit log which s
Assign ports previously owned by the EHCI controllers to the xHCI
controller. There are two external USB ports (UTMI ports 0/2 and
USB3 ports 0/1) and an internal USB port (UTMI port 1). PCIe lanes
0 and 1 are used by the USB3 ports.
Signed-off-by: Andrew Bresticker
---
Changes from v2:
- Upda
Add device-tree binding documentation for the xHCI controller present
on Tegra124 and later SoCs.
Signed-off-by: Andrew Bresticker
---
Changes from v2:
- Added mbox-names property.
Changes from v1:
- Updated to use common mailbox bindings.
- Added remaining XUSB-related clocks and resets.
- U
This series adds support for xHCI on NVIDIA Tegra SoCs. This includes:
- patches 1 and 2: adding a driver for the mailbox used to communicate
with the xHCI controller's firmware,
- patches 3 and 4: extending the XUSB pad controller driver to support
the USB PHY types (UTMI, HSIC, and USB3)
In addition to the PCIe and SATA PHYs, the XUSB pad controller also
supports 3 UTMI, 2 HSIC, and 2 USB3 PHYs. Each USB3 PHY uses a single
PCIe or SATA lane and is mapped to one of the three UTMI ports.
The xHCI controller will also send messages intended for the PHY driver,
so request and listen
The Tegra xHCI controller's firmware communicates requests to the host
processor through a mailbox interface. While there is only a single
physical channel, messages sent by the controller can be divided
into two groups: those intended for the PHY driver and those intended
for the host-controller
Add new bindings used for USB support by the Tegra XUSB pad controller.
This includes additional PHY types, USB-specific pinconfig properties, etc.
Signed-off-by: Andrew Bresticker
---
Changes from v2:
- Added nvidia,otg-hs-curr-level-offset property.
- Dropped "-otg" from VBUS supplies.
- Add
Assign USB ports previously owned by the EHCI controllers to the xHCI
controller. There is a mini-PCIe USB port (UTMI port 1) and a USB A
connector (UTMI port 2, USB3 port 0). PCIe lane 0 is used for USB3
port 0.
Signed-off-by: Andrew Bresticker
---
Changes from v2:
- Updated VBUS power supply
Add nodes for the Tegra XUSB mailbox and Tegra xHCI controller and
add the PHY mailbox channel to the XUSB padctl node.
Signed-off-by: Andrew Bresticker
---
Changes from v2:
- Dropped channel specifier from mailbox bindings.
- Added mbox-names properties.
Changes from v1:
- Updated to use comm
Add support for the on-chip xHCI host controller present on Tegra SoCs.
The driver is currently very basic: it loads the controller with its
firmware, starts the controller, and is able to service messages sent
by the controller's firmware. The hardware also supports device mode
as well as powerg
Add device-tree bindings for the Tegra XUSB mailbox which will be used
for communication between the Tegra xHCI controller's firmware and the
host processor.
Signed-off-by: Andrew Bresticker
---
Changes from v2:
- Dropped channel specifier.
- Added pointer to mailbox documentation.
Changes from
Hi Johan
Here are the debug logs you asked me
* dmesg output while connecting the device without dynamic debug
* dmesg output while connecting the device with dynamic debug
* .../dynamic_debug/control active rules for cdc_acm
* dmesg output with dyndbg while opening the port, writting to the por
Commit d24d481b7d36 (usb-storage: Modify and export adjust_quirks so
that it can be used by uas) added the 'u' flag to the quirks module
parameter for usb-storage, but neglected to update the
documentation. This patch adds the documentation.
Signed-off-by: Alan Stern
---
[as1764]
Documenta
On Tue, 2 Sep 2014, Felipe Balbi wrote:
> > You know, more and more it seems like this ought to be handled by the
> > UDC core. There are two conditions for turning on the pullup: Vbus
> > must be active, and the gadget's functions must all be activated. The
> > UDC driver knows about the first
On Tue, Sep 02, 2014 at 02:11:52PM -0400, Alan Stern wrote:
> On Tue, 2 Sep 2014, Felipe Balbi wrote:
>
> > > > alright, but we need to do this in steps to avoid regressions or a
> > > > non-bisectable tree. So maybe we add ->reset as an optional method,
> > > > implement support for it to all UDC
On Tue, 2 Sep 2014, Felipe Balbi wrote:
> > > alright, but we need to do this in steps to avoid regressions or a
> > > non-bisectable tree. So maybe we add ->reset as an optional method,
> > > implement support for it to all UDC drivers, patch all gadget drivers to
> > > implement reset, make rese
> From: Mark
>
> I have an Iomega SCSI-to-USB cable, model# SCSI USBA. Iomega called it the
> Jaz USB Adapter; see
> http://www.iomega.com/europe/support/english/manuals/jazusb/home.html
You might be screwed. The manual says
NOTE: The Jaz USB Adapter can be used to connect any model of the
Hi,
On Mon, Sep 01, 2014 at 01:25:31PM +0200, Ricardo Ribalda Delgado wrote:
> Hello Felipe
>
> I think that you have forgotten about this patch :). It is needed by
> usb3380 in usb3.0 mode. Otherwise the device keeps reseting.
it's in my testing/fixes. I'm pretty much done with testing, just wa
Hi,
On Tue, Sep 02, 2014 at 01:15:18PM -0400, Alan Stern wrote:
> On Tue, 2 Sep 2014, Felipe Balbi wrote:
>
> > > That needn't be a problem. If Peter updates the four gadget drivers,
> > > adding reset callbacks, then we can remove the parts of our patches
> > > that invoke the disconnect callba
On Tue, 2 Sep 2014, Mark wrote:
> On Tue, 2 Sep 2014 10:42:59 -0400 (EDT)
> Alan Stern wrote:
>
> > On Tue, 2 Sep 2014, Mark wrote:
> > > I have an Iomega SCSI-to-USB cable, model# SCSI USBA. Iomega called it the
> > > ...
> > > My cable has USB ID 059B:0040. It is identical in appearance to the
On Tue, 2 Sep 2014, Felipe Balbi wrote:
> > That needn't be a problem. If Peter updates the four gadget drivers,
> > adding reset callbacks, then we can remove the parts of our patches
> > that invoke the disconnect callback if there is no reset callback. In
> > other words, we can make reset c
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
Signed-off-by: Peter Griffin
Acked-by: Lee Jones
---
drivers/usb/dwc3/Kconfig | 9 +
This series adds support for the ST glue logic which wraps the DWC3 controller
on STiH407 SoC family chipsets.
Changes since v4
- Fix bug with setting bits in usb control register
- Remove superflous '\n'
- Change default Kconfig to make default same as other platforms
- Update dt doc example
This patch documents the device tree documentation required for
the ST usb3 controller glue layer found in STiH407 devices.
Signed-off-by: Giuseppe Cavallaro
Signed-off-by: Peter Griffin
Acked-by: Lee Jones
---
Documentation/devicetree/bindings/usb/dwc3-st.txt | 68 +++
1 f
This patch adds the new dwc3-st.c glue driver found on
STMicroelectronics stih407 consumer electronics SoC's into the STI
arch section of the maintainers file.
Signed-off-by: Peter Griffin
Acked-by: Lee Jones
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAIN
On Tue, 2 Sep 2014 10:42:59 -0400 (EDT)
Alan Stern wrote:
> On Tue, 2 Sep 2014, Mark wrote:
> > I have an Iomega SCSI-to-USB cable, model# SCSI USBA. Iomega called it the
> > ...
> > My cable has USB ID 059B:0040. It is identical in appearance to the
> > Microtech XpressSCSI, which does work with
Hi,
On Tue, Sep 02, 2014 at 12:02:03PM -0400, Alan Stern wrote:
> On Tue, 2 Sep 2014, Felipe Balbi wrote:
>
> > On Tue, Sep 02, 2014 at 11:32:52AM -0400, Alan Stern wrote:
> > > On Fri, 29 Aug 2014, Felipe Balbi wrote:
> > >
> > > > > I still have some old patch files lying around, adding reset
On Tue, 2 Sep 2014, Felipe Balbi wrote:
> On Tue, Sep 02, 2014 at 11:32:52AM -0400, Alan Stern wrote:
> > On Fri, 29 Aug 2014, Felipe Balbi wrote:
> >
> > > > I still have some old patch files lying around, adding reset callback
> > > > support to dummy-hcd, net2280, and net2272. Would you like
On Tue, Sep 02, 2014 at 10:43:37AM -0500, Felipe Balbi wrote:
> On Tue, Sep 02, 2014 at 11:32:52AM -0400, Alan Stern wrote:
> > On Fri, 29 Aug 2014, Felipe Balbi wrote:
> >
> > > > I still have some old patch files lying around, adding reset callback
> > > > support to dummy-hcd, net2280, and net2
On Tue, Sep 02, 2014 at 11:32:52AM -0400, Alan Stern wrote:
> On Fri, 29 Aug 2014, Felipe Balbi wrote:
>
> > > I still have some old patch files lying around, adding reset callback
> > > support to dummy-hcd, net2280, and net2272. Would you like me to post
> > > them?
> >
> > Please do :-) let's
[ Please avoid top posting. ]
On Tue, Sep 02, 2014 at 09:29:49AM -0500, Sergio De León wrote:
> Sorry for my late reply,
>
> I still haven't tried the debug mode for cdc-acm since I still have to
> figure out the "proper way" to get and compile the source on Linux Mint
> (it seems some document
This patch changes the way usbhid carries out Clear-Halt and reset.
Currently, after a Clear-Halt on the interrupt-IN endpoint, the driver
immediately restarts the interrupt URB, even if the Clear-Halt failed.
This doesn't work out well when the reason for the failure was that
the device was disco
The SCSI specification requires that the second Command Data Byte
should contain the LUN value in its high-order bits if the recipient
device reports SCSI level 2 or below. Nevertheless, some USB
mass-storage devices use those bits for other purposes in
vendor-specific commands. Currently Linux h
This patch adds support for the new "reset" gadget callback to the
net2272 driver.
Signed-off-by: Alan Stern
---
[as1602]
drivers/usb/gadget/udc/net2272.c | 43 +--
1 file changed, 33 insertions(+), 10 deletions(-)
Index: usb-3.17/drivers/usb/gadget/ud
This patch adds support for the new "reset" gadget callback to the
net2280 driver.
Signed-off-by: Alan Stern
---
[as1601]
drivers/usb/gadget/udc/net2280.c | 43 +--
1 file changed, 33 insertions(+), 10 deletions(-)
Index: usb-3.17/drivers/usb/gadget/ud
This patch adds support for the new "reset" gadget callback to the
dummy-hcd driver.
Signed-off-by: Alan Stern
---
[as1600]
drivers/usb/gadget/udc/dummy_hcd.c | 21 -
1 file changed, 12 insertions(+), 9 deletions(-)
Index: usb-3.17/drivers/usb/gadget/udc/dummy_hcd.c
=
On Fri, 29 Aug 2014, Felipe Balbi wrote:
> > I still have some old patch files lying around, adding reset callback
> > support to dummy-hcd, net2280, and net2272. Would you like me to post
> > them?
>
> Please do :-) let's get all of that sorted out soon.
Patches coming up. These were written
On Tue, Sep 02, 2014 at 11:45:55AM +0300, Octavian Purdila wrote:
> On Tue, Sep 2, 2014 at 11:00 AM, Lee Jones wrote:
> > On Mon, 01 Sep 2014, Johan Hovold wrote:
> >> I haven't looked at the details of the protocol for the device in
> >> question, but it might even be possible to use regmap here
Hi,
On Tue, Sep 02, 2014 at 12:18:12PM +0100, Peter Griffin wrote:
> Hi Felipe,
>
> Sorry for the delay in replying to this mail, I've been trying to get
> answers to the suspend/resume questions you had.
np
> > > +config USB_DWC3_ST
> > > + tristate "STMicroelectronics Platforms"
> > > + depen
On Tue, Sep 02, 2014 at 09:00:10AM +0100, Lee Jones wrote:
> On Mon, 01 Sep 2014, Johan Hovold wrote:
> > No, no. USB is not a function of the MFD device, it's the transport.
> > Thus there should be no USB MFD-cell. No subdriver can work without it.
> >
> > And the USB id belongs in the MFD-driv
On Tue, Sep 2, 2014 at 7:59 PM, Felipe Balbi wrote:
> On Tue, Sep 02, 2014 at 04:04:14PM +0200, Daniel Mack wrote:
>> Hi Felipe,
>>
>> On 08/29/2014 10:46 PM, Felipe Balbi wrote:
>> > On Wed, Aug 27, 2014 at 07:09:03PM +0200, Daniel Mack wrote:
>> >> Restructure some code to make it easier to read
Hi,
On Tue, Sep 02, 2014 at 05:19:18PM +0530, Kiran Kumar Raparthy wrote:
> From: Todd Poynor
>
> usb: phy: Temporarily hold wakeupsource on charger connect and disconnect
> events
>
> Allow other parts of the system to react to the charger connect/disconnect
> event without allowing the system
On Tue, Sep 02, 2014 at 05:17:08PM +0530, Kiran Kumar Raparthy wrote:
> From: Todd Poynor
>
> usb: phy: Hold wakeupsource when USB is enumerated in peripheral mode
>
> Purpose of this is to prevent the system to enter into suspend state from USB
> peripheral traffic by hodling a wakeupsource whe
On Tue, 2 Sep 2014, Mark wrote:
> Hi,
>
> I have an Iomega SCSI-to-USB cable, model# SCSI USBA. Iomega called it the
> Jaz USB Adapter; see
> http://www.iomega.com/europe/support/english/manuals/jazusb/home.html
> Picture: http://ecx.images-amazon.com/images/I/31Q4Z3PMT5L.jpg
>
> My cable has US
I seem to recall that the Iomega-branded versions of these are limited
to only working with Iomega drives. You need the generic-branded
version to work with any drive.
Matt
On Tue, Sep 2, 2014 at 6:18 AM, Mark wrote:
> Hi,
>
> I have an Iomega SCSI-to-USB cable, model# SCSI USBA. Iomega called i
On Mon, Sep 01, 2014 at 01:30:21PM +0530, Vivek Gautam wrote:
> On Thu, Aug 28, 2014 at 8:36 PM, Daniele Forsi wrote:
> > 2014-08-28 10:02 GMT+02:00 Vivek Gautam:
> >
> >> This USB 3.0 PHY controller is also present on Exynos7
> >> platform, so adding the dependency on ARCH_EXYNOS7 for this driver
On Tue, Sep 02, 2014 at 04:09:08PM +0530, Vivek Gautam wrote:
> Hi,
>
>
> On Fri, Aug 29, 2014 at 12:18 AM, Mark Rutland wrote:
> > On Thu, Aug 28, 2014 at 09:01:56AM +0100, Vivek Gautam wrote:
> >> Exynos7 also has a separate special gate clock going to the IP
> >> apart from the usual AHB cloc
Hi,
On Tue, Sep 02, 2014 at 04:42:18PM +0530, Vivek Gautam wrote:
> Adding phy calibrate callback, which facilitates setting certain
> PHY settings post initialization of the PHY controller.
> Exynos5420 and Exynos5800 have 28nm USB 3.0 DRD PHY for which
> the Loss-of-Signal (LOS) Detector Thresho
Sorry for my late reply,
I still haven't tried the debug mode for cdc-acm since I still have to
figure out the "proper way" to get and compile the source on Linux Mint
(it seems some documentation is old... but mostly I've been a little
busy to dig deeper).
About the hardware flow control, I
On Tue, Sep 02, 2014 at 04:04:14PM +0200, Daniel Mack wrote:
> Hi Felipe,
>
> On 08/29/2014 10:46 PM, Felipe Balbi wrote:
> > On Wed, Aug 27, 2014 at 07:09:03PM +0200, Daniel Mack wrote:
> >> Restructure some code to make it easier to read.
> >>
> >> While at it, return -ENOMEM instead of -EINVAL
Hi Felipe,
On 08/29/2014 10:46 PM, Felipe Balbi wrote:
> On Wed, Aug 27, 2014 at 07:09:03PM +0200, Daniel Mack wrote:
>> Restructure some code to make it easier to read.
>>
>> While at it, return -ENOMEM instead of -EINVAL if
>> usb_ep_alloc_request() fails, and omit the logging in such cases
>> (
Hi,
I have an Iomega SCSI-to-USB cable, model# SCSI USBA. Iomega called it the
Jaz USB Adapter; see
http://www.iomega.com/europe/support/english/manuals/jazusb/home.html
Picture: http://ecx.images-amazon.com/images/I/31Q4Z3PMT5L.jpg
My cable has USB ID 059B:0040. It is identical in appearance to
Hi,
On 09/02/2014 02:41 PM, Jassi Brar wrote:
> On Sat, Aug 30, 2014 at 2:16 AM, Felipe Balbi wrote:
>> Hi,
>>
>> On Wed, Aug 27, 2014 at 07:09:03PM +0200, Daniel Mack wrote:
>>> Restructure some code to make it easier to read.
>>>
>>> While at it, return -ENOMEM instead of -EINVAL if
>>> usb_ep_
Hello.
On 9/2/2014 1:55 PM, Hayes Wang wrote:
If the hw doesn't have a valid MAC address, give a random one and
set it to the hw.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 39 ---
1 file changed, 24 insertions(+), 15 deletions(-)
diff
Hi Felipe
On Sat, Aug 30, 2014 at 2:16 AM, Felipe Balbi wrote:
> Hi,
>
> On Wed, Aug 27, 2014 at 07:09:03PM +0200, Daniel Mack wrote:
>> Restructure some code to make it easier to read.
>>
>> While at it, return -ENOMEM instead of -EINVAL if
>> usb_ep_alloc_request() fails, and omit the logging i
On 西元2014年09月02日 14:50, Hans de Goede wrote:
> Hi,
>
> On 09/02/2014 06:18 AM, Chunwei Chen wrote:
>> Dear all:
>>
>> The kernel version is 3.16.1-1-ARCH
>>
>> Today I keep getting this panic when booting up.
>> http://i.imgur.com/0Rx93Kr.jpg
>>
>> It might be that the UAS device was in some str
Entrega Technologies produced a USB to SCSI converter (model U1-SC25). Xircom
acquired Entrega and re-branded the product line PortGear. The PortGear USB to
SCSI Converter (model PGSCSI) is internally identical to the earlier Entrega
product.
It uses the Shuttle Technology EUSB-01/EUSB-S1 chips. A
From: Todd Poynor
usb: phy: Temporarily hold wakeupsource on charger connect and disconnect
events
Allow other parts of the system to react to the charger connect/disconnect
event without allowing the system to suspend before the other parts can process
the event. This wakeup_source times out af
From: Todd Poynor
usb: phy: Hold wakeupsource when USB is enumerated in peripheral mode
Purpose of this is to prevent the system to enter into suspend state from USB
peripheral traffic by hodling a wakeupsource when USB is connected and
enumerated in peripheral mode(say adb).
Disabled by defaul
Hi Felipe,
Sorry for the delay in replying to this mail, I've been trying to get answers
to the suspend/resume
questions you had.
> > +config USB_DWC3_ST
> > + tristate "STMicroelectronics Platforms"
> > + depends on ARCH_STI && OF
> > + default USB_DWC3_HOST
>
> this seems wrong as USB_D
Some PHY controllers may need to calibrate certain
PHY settings after initialization of the controller and
sometimes even after initializing the PHY-consumer too.
Add support for the same in order to let consumers do so in need.
Signed-off-by: vivek Gautam
---
drivers/phy/phy-core.c | 36
Some quirky PHYs may require to be calibrated post the
hcd initialization.
The USB 3.0 DRD PHY on Exynos5420/5800 systems, coming along
with Synopsys's DWC3 controller, is one such PHY which needs
to be calibrated post xhci's reset at initialization time and
at resume time, to get the controller wo
Adding phy calibrate callback, which facilitates setting certain
PHY settings post initialization of the PHY controller.
Exynos5420 and Exynos5800 have 28nm USB 3.0 DRD PHY for which
the Loss-of-Signal (LOS) Detector Threshold Level as well as
Tx-Vboost-Level should be controlled for Super-Speed op
The host controller by itself may sometimes need to handle PHY
and/or calibrate some of the PHY settings to get full support out
of the PHY controller. The PHY core provides a calibration
funtionality now to do so.
Therefore, facilitate getting the two possible PHYs, viz.
USB 2.0 type (UTMI+) and U
This series is based on Heikki's patches for simpliefied phy lookup table:
[PATCHv3 0/6] phy: simplified phy lookup [1], applied against 'usb-next' branch
alongwith Sergei's patch for adding generic phy support to usb hcd [2].
NOTE: We need to get above dependencies merged first in order to merge
On Tue, Sep 02, 2014 at 11:39:08AM +0100, Vivek Gautam wrote:
> Hi,
>
>
> On Fri, Aug 29, 2014 at 12:18 AM, Mark Rutland wrote:
> > On Thu, Aug 28, 2014 at 09:01:56AM +0100, Vivek Gautam wrote:
> >> Exynos7 also has a separate special gate clock going to the IP
> >> apart from the usual AHB cloc
Hi,
On Fri, Aug 29, 2014 at 12:18 AM, Mark Rutland wrote:
> On Thu, Aug 28, 2014 at 09:01:56AM +0100, Vivek Gautam wrote:
>> Exynos7 also has a separate special gate clock going to the IP
>> apart from the usual AHB clock. So add support for the same.
>>
>> Signed-off-by: Vivek Gautam
>> ---
>>
On Tue, Sep 02, 2014 at 11:08:32AM +0200, Antoine Tenart wrote:
> Hi,
>
> On Mon, Sep 01, 2014 at 09:13:43AM +0800, Peter Chen wrote:
> > On Fri, Aug 29, 2014 at 04:25:35PM +0200, Antoine Tenart wrote:
> > > On Tue, Aug 26, 2014 at 06:22:40PM +0800, Peter Chen wrote:
> > > > On Fri, Aug 22, 2014 a
If the hw doesn't have a valid MAC address, give a random one and
set it to the hw.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 39 ---
1 file changed, 24 insertions(+), 15 deletions(-)
diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/r8152.
If the interface has invalid MAC address, it couldn't
be used. In order to let it work normally, give a
random one.
Hayes Wang (2):
r8152: change the location of rtl8152_set_mac_address
r8152: use eth_hw_addr_random
drivers/net/usb/r8152.c | 65 ---
Exchange the location of rtl8152_set_mac_address() and
set_ethernet_addr(). Then, the set_ethernet_addr() could
set the MAC address by calling rtl8152_set_mac_address()
later.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 34 +-
1 file changed, 17 insert
Hi,
On Mon, Sep 01, 2014 at 09:13:43AM +0800, Peter Chen wrote:
> On Fri, Aug 29, 2014 at 04:25:35PM +0200, Antoine Tenart wrote:
> > On Tue, Aug 26, 2014 at 06:22:40PM +0800, Peter Chen wrote:
> > > On Fri, Aug 22, 2014 at 05:50:19PM +0200, Antoine Ténart wrote:
> > >
> > > If the common usb_otg
On Tue, Sep 2, 2014 at 11:00 AM, Lee Jones wrote:
> On Mon, 01 Sep 2014, Johan Hovold wrote:
>> On Mon, Sep 01, 2014 at 07:22:39PM +0300, Octavian Purdila wrote:
>> > On Mon, Sep 1, 2014 at 6:46 PM, Lee Jones wrote:
>> > > On Mon, 01 Sep 2014, Octavian Purdila wrote:
>> > >
>> > >> On Mon, Sep 1,
On Mon, 01 Sep 2014, Johan Hovold wrote:
> On Mon, Sep 01, 2014 at 07:22:39PM +0300, Octavian Purdila wrote:
> > On Mon, Sep 1, 2014 at 6:46 PM, Lee Jones wrote:
> > > On Mon, 01 Sep 2014, Octavian Purdila wrote:
> > >
> > >> On Mon, Sep 1, 2014 at 2:39 PM, Lee Jones wrote:
> > >> > On Mon, 01 Se
On Fri, Aug 29, 2014 at 04:15:25PM +0200, Johan Hovold wrote:
> On Sat, Aug 23, 2014 at 12:53:12PM -0500, Sergio De León wrote:
> > Hi, I've been trying to get this device work in linux Mint Qiana
> > (3.13.0-24-generic) without success.
> >
> > The XR21V1414 is a multiport USB-UART device. (0x04
[ Please do not top post. ]
On Tue, Sep 02, 2014 at 02:44:44PM +0800, 刘磊 wrote:
> Dear Johan & Greg:
> I can't find remove pid(0xfff6 to 0xfffd and 0xffec/0xffee) back
> to zte_ev.c or option.c in git.
> please make sure that pid had been added. thanks.
Those PIDs will be added back to z
Dear Johan & Greg:
I can't find remove pid(0xfff6 to 0xfffd and 0xffec/0xffee) back to
zte_ev.c or option.c in git.
please make sure that pid had been added. thanks.
lei.liu.
At 2014-08-28 06:46:54, "Johan Hovold" wrote:
>Add back some PIDs that were mistakingly remove when reverting c
92 matches
Mail list logo
