- 28 Sep, 2018 12 commits
-
-
Adam Thomson authored
There's a typo in the enum name of the 'OFF' state for toggling (TOGGLINE instead of TOGGLING). This commit resolves that trivial spelling inconsistency. Signed-off-by:
Adam Thomson <Adam.Thomson.Opensource@diasemi.com> Reviewed-by:
Guenter Roeck <linux@roeck-us.net> Reviewed-by:
Heikki Krogerus <heikki.krogerus@linux.intel.com> Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
Anshuman Gupta authored
When USB bus host controller root hub resumes from autosuspend, it immediately tries to enter auto-suspend, but there can be a scenario when root hub is resuming its usb2 ports, in that particular case USB host controller auto suspend fails since it is busy to resuming its usb2 ports. This makes multiple failed cycles of auto-suspend until all usb2 ports of host controller root hub do not resume. This patch uses USB core framework usb_hcd_start_port_resume, usb_hcd_end_port_resume API's in order to autoresume/autosuspend root hub properly. Signed-off-by:
Anshuman Gupta <anshuman.gupta@intel.com> Signed-off-by:
Mathias Nyman <mathias.nyman@linux.intel.com> Signed-off-by:
-
Thierry Reding authored
The XUSB firmware header is in little endian byte order, so make the fields __le32 and __le16 instead of u32 and u16 to avoid warnings from sparse when the fields are used with the endian-aware __le32_to_cpu() and __le16_to_cpu() accessors, respectively. Signed-off-by:
Thierry Reding <treding@nvidia.com> Signed-off-by:
-
Mathias Nyman authored
The xhci controller on Alpine and Titan Ridge keeps the whole thunderbolt awake if the host controller is not allowed tp sleep. This is the case even if no USB devices are connected to the host. Because of this bigger impact, allow runtime pm as default for these xhci controllers in the driver. Signed-off-by:
-
Mathias Nyman authored
Use soft retry to recover from a USB Transaction Errors that are caused by temporary error conditions. The USB device is not aware that the xHC has halted the endpoint, and will be waiting for another retry A Soft Retry perform additional retries and recover from an error which has caused the xHC to halt an endpoint. Soft retry has some limitations: Soft Retry attempts shall not be performed on Isoch endpoints Soft Retry attempts shall not be performed if the device is behind a TT in a HS Hub Software shall limit the number of unsuccessful Soft Retry attempts to prevent an infinite loop. For more details on Soft retry see xhci specs 4.6.8.1 Signed-off-by:
-
Peter Chen authored
The TPL support is used to identify targeted devices during EH2.0 and EH3.0 certification test, the user can add "tpl-support" at dts to enable this feature. Signed-off-by:
Peter Chen <peter.chen@nxp.com> Signed-off-by:
-
Chunfeng Yun authored
Supports SSP scheduling only for SSP device directly connected to root hub but not through external USB3 gen2 hub which need use a new scheduling way. Signed-off-by:
Chunfeng Yun <chunfeng.yun@mediatek.com> Signed-off-by:
-
Chunfeng Yun authored
Supports LowSpeed and FullSpeed INT/ISOC bandwidth scheduling with USB multi-TT Signed-off-by:
-
Chunfeng Yun authored
Mainly improve SuperSpeed ISOC bandwidth in last microframe, and LowSpeed/FullSpeed IN INT/ISOC bandwidth in split and idle microframes by introduing a bandwidth budget table; Signed-off-by:
-
Chunfeng Yun authored
If the interval equal zero, needn't round up to power of two for the number of packets in each ESIT, so fix it. Signed-off-by:
-
Chunfeng Yun authored
Make use of maximum ESIT payload of endpoint context to calculate the number of packets to send in each ESIT Signed-off-by:
-
Corentin Labbe authored
It's dangerous to use empty code define. Furthermore it lead to the following warning: "suggest braces around empty body in an « else » statement" So let's replace emptyness by "do {} while(0)" Furthermore, as suggested by Joe Perches, rename the macro to INCR. Signed-off-by:Corentin Labbe <clabbe@baylibre.com> Acked-by:
Alan Stern <stern@rowland.harvard.edu> Signed-off-by:
-
- 20 Sep, 2018 28 commits
-
-
Jagdish Tirumala authored
Fixed errors spaces required around the for loop '=' , ';' and '<' in drivers/usb/storage/isd200.c Signed-off-by:
Jagdish Tirumala <t.jag587@gmail.com> Signed-off-by:
-
Heikki Krogerus authored
Moving all the drivers that depend on the Port Controller Manager under a new directory drivers/usb/typec/tcpm/ and making Guenter Roeck the designated reviewer of that code. Acked-by:
-
Heikki Krogerus authored
The debugfs needs to be initialized as the last step in probe in this case. The struct dentry *rootdir can't be pointing to anything unless driver probe really finishes successfully. It is also not necessary to clear the i2c clientdata if the probe fails, so removing the extra label used for that. Acked-by:
Hans de Goede <hdegoede@redhat.com> Tested-by:
-
Heikki Krogerus authored
USB Type-C class driver now expects the muxes to be always assigned to the ports and not controllers, so the connections for the mux and fusb302 can be removed. Acked-by:
Andy Shevchenko <andy.shevchenko@gmail.com> Acked-by:
-
Heikki Krogerus authored
It is not possible to use the parent of the port device when requesting mux handles as the parent may be a multiport USB Type-C or PD controller. The muxes must be assigned to the ports, not the controllers. This will also move the requesting of the muxes after the port device is initialized. Acked-by:
-
Heikki Krogerus authored
Assigning the mux to the USB Type-C port on top of fusb302. That will prepare this driver for the change in the USB Type-C class code, where the class driver will assume the muxes to be always assigned to the ports and not the controllers. Once the USB Type-C class driver has been updated, the connections between the mux and fusb302 can be dropped. Acked-by:
-
Heikki Krogerus authored
Adding a connection for the DisplayPort alternate mode. PI3USB30532 is used for muxing the port to DisplayPort on CHT platforms. The connection allows the alternate mode device to get handle to the mux, and therefore make it possible to use the USB Type-C connector as DisplayPort. Acked-by:
-
Heikki Krogerus authored
We can register all device connection descriptors with a single call to device_connections_add(). Acked-by:
-
Heikki Krogerus authored
Introducing helpers for adding and removing multiple device connection descriptions at once. Acked-by:
-
Heikki Krogerus authored
The connections create clear dependency on the muxes. fusb302 fails to probe unless we have the mux drivers available. Acked-by:
-
Colin Ian King authored
Trivial fix to spelling mistake in dev_dbg message Signed-off-by:
Colin Ian King <colin.king@canonical.com> Acked-by:
-
Linus Walleij authored
There is code in the .remove() hook to handle the drvdata being NULL, for good reasons: it is never set, so it will always be NULL. As I moved code around, static checkers start complaining. Instead of this, make sure to always set it on successful probe so we can always dereference it on the remove path. Use the platform_device_[set|get]_drvdata() since this is a platform device. Fixes: ffa8a31b ("usb: host: fotg2: add silicon clock handling") Reported-by:
Dan Carpenter <dan.carpenter@oracle.com> Cc: Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by:
Linus Walleij <linus.walleij@linaro.org> Signed-off-by:
-
Yoshihiro Shimoda authored
R-Car Gen3 needs to enable clocks of both host and peripheral. Since [eo]hci-platform disables the reset(s) when the drivers are removed, renesas_usbhs driver doesn't work correctly. To fix this issue, this patch adds multiple clocks management on this renesas_usbhs driver. Signed-off-by:
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com> Signed-off-by:
-
Yoshihiro Shimoda authored
R-Car Gen3 needs to enable clocks of both host and peripheral. Otherwise, other side device cannot work correctly. So, this patch adds a property of clock-names for R-Car Gen3 as an optional. Signed-off-by:
Rob Herring <robh@kernel.org> Signed-off-by:
-
Yoshihiro Shimoda authored
R-Car Gen3 needs to deassert resets of both host and peripheral. Since [eo]hci-platform is possible to assert the reset(s) when the probing failed, renesas_usbhs driver doesn't work correctly regardless of finished probing. To fix this issue, this patch adds reset_control on this renesas_usbhs driver. Signed-off-by:
-
Yoshihiro Shimoda authored
This patch adds detailed information of an optional property "clocks" description for R-Car Gen3. Signed-off-by:
Simon Horman <horms+renesas@verge.net.au> Reviewed-by:
-
Yoshihiro Shimoda authored
This patch adds detailed information of an optional property "clocks" description for R-Car Gen3. Signed-off-by:
-
Saranya Gopal authored
USB audio class 3.0 specification introduced many significant changes like - new power domains, support for LPM/L1 - new cluster descriptor - new high capability and class-specific string descriptors - BADD profiles - ... and many other things (check spec from link below: http://www.usb.org/developers/docs/devclass_docs/USB_Audio_v3.0.zip) Now that UAC3 is supported in linux, choose UAC3 configuration for audio if the device supports it. Selecting this configuration will enable the system to save power by leveraging the new power domains and LPM L1 capability and also support new codec types and data formats for consumer audio applications. Signed-off-by:
Saranya Gopal <saranya.gopal@intel.com> Reviewed-by:
Felipe Balbi <felipe.balbi@linux.intel.com> Signed-off-by:
-
Fabrizio Castro authored
Document RZ/G2M (R8A774A1) SoC bindings. Signed-off-by:
Fabrizio Castro <fabrizio.castro@bp.renesas.com> Reviewed-by:
Biju Das <biju.das@bp.renesas.com> Reviewed-by:
-
Fabrizio Castro authored
Document RZ/G2M (R8A774A1) SoC bindings. Signed-off-by:
-
Fabrizio Castro authored
Document RZ/G2M (R8A774A1) SoC bindings. Signed-off-by:
-
Lubomir Rintel authored
Signed-off-by:
Lubomir Rintel <lkundrak@v3.sk> Acked-by:
-
Lubomir Rintel authored
Add Device tree support. Signed-off-by:
-
Lubomir Rintel authored
Use a proper PHY driver, instead of hooks to a board support package. Signed-off-by:
-
Lubomir Rintel authored
It's unused. Signed-off-by:
-
Lubomir Rintel authored
This is done do that it could be enabled alongside other platform EHCI glue drivers on multiplatform kernels. Signed-off-by:
-
Guido Kiener authored
As all the properties of the usbtmc driver can now be controlled on a per file descriptor basis by ioctl functions the sysfs interface is of limited use. We are not aware about applications that are using the sysfs parameter TermChar, TermCharEnabled or auto_abort. Signed-off-by:
Guido Kiener <guido.kiener@rohde-schwarz.com> Reviewed-by:
Steve Bayless <steve_bayless@keysight.com> Signed-off-by:
-
Guido Kiener authored
Signed-off-by:
-
