Commit 5695d5d1 authored by Linus Torvalds's avatar Linus Torvalds
Browse files

Merge tag 'usb-4.19-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb 

Pull USB/PHY updates from Greg KH:
 "Here is the big USB and phy driver patch set for 4.19-rc1.

  Nothing huge but there was a lot of work that happened this
  development cycle:

   - lots of type-c work, with drivers graduating out of staging, and
     displayport support being added.

   - new PHY drivers

   - the normal collection of gadget driver updates and fixes

   - code churn to work on the urb handling path, using irqsave()
     everywhere in anticipation of making this codepath a lot simpler in
     the future.

   - usbserial driver fixes and reworks

   - other misc changes

  All of these have been in linux-next with no reported issues for a
  while"

* tag 'usb-4.19-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb: (159 commits)
  USB: serial: pl2303: add a new device id for ATEN
  usb: renesas_usbhs: Kconfig: convert to SPDX identifiers
  usb: dwc3: gadget: Check MaxPacketSize from descriptor
  usb: dwc2: Turn on uframe_sched on "stm32f4x9_fsotg" platforms
  usb: dwc2: Turn on uframe_sched on "amlogic" platforms
  usb: dwc2: Turn on uframe_sched on "his" platforms
  usb: dwc2: Turn on uframe_sched on "bcm" platforms
  usb: dwc2: gadget: ISOC's starting flow improvement
  usb: dwc2: Make dwc2_readl/writel functions endianness-agnostic.
  usb: dwc3: core: Enable AutoRetry feature in the controller
  usb: dwc3: Set default mode for dwc_usb31
  usb: gadget: udc: renesas_usb3: Add register of usb role switch
  usb: dwc2: replace ioread32/iowrite32_rep with dwc2_readl/writel_rep
  usb: dwc2: Modify dwc2_readl/writel functions prototype
  usb: dwc3: pci: Intel Merrifield can be host
  usb: dwc3: pci: Supply device properties via driver data
  arm64: dts: dwc3: description of incr burst type
  usb: dwc3: Enable undefined length INCR burst type
  usb: dwc3: add global soc bus configuration reg0
  usb: dwc3: Describe 'wakeup_work' field of struct dwc3_pci
  ...
parents 1f7a4c73 29c692c9

Documentation/ABI/obsolete/sysfs-class-typec

0 → 100644
+48 −0
Original line number Diff line number Diff line 
These files are deprecated and will be removed. The same files are available

under /sys/bus/typec (see Documentation/ABI/testing/sysfs-bus-typec).



What:		/sys/class/typec/<port|partner|cable>/<dev>/svid

Date:		April 2017

Contact:	Heikki Krogerus <heikki.krogerus@linux.intel.com>

Description:

		The SVID (Standard or Vendor ID) assigned by USB-IF for this

		alternate mode.



What:		/sys/class/typec/<port|partner|cable>/<dev>/mode<index>/

Date:		April 2017

Contact:	Heikki Krogerus <heikki.krogerus@linux.intel.com>

Description:

		Every supported mode will have its own directory. The name of

		a mode will be "mode<index>" (for example mode1), where <index>

		is the actual index to the mode VDO returned by Discover Modes

		USB power delivery command.



What:		/sys/class/typec/<port|partner|cable>/<dev>/mode<index>/description

Date:		April 2017

Contact:	Heikki Krogerus <heikki.krogerus@linux.intel.com>

Description:

		Shows description of the mode. The description is optional for

		the drivers, just like with the Billboard Devices.



What:		/sys/class/typec/<port|partner|cable>/<dev>/mode<index>/vdo

Date:		April 2017

Contact:	Heikki Krogerus <heikki.krogerus@linux.intel.com>

Description:

		Shows the VDO in hexadecimal returned by Discover Modes command

		for this mode.



What:		/sys/class/typec/<port|partner|cable>/<dev>/mode<index>/active

Date:		April 2017

Contact:	Heikki Krogerus <heikki.krogerus@linux.intel.com>

Description:

		Shows if the mode is active or not. The attribute can be used

		for entering/exiting the mode with partners and cable plugs, and

		with the port alternate modes it can be used for disabling

		support for specific alternate modes. Entering/exiting modes is

		supported as synchronous operation so write(2) to the attribute

		does not return until the enter/exit mode operation has

		finished. The attribute is notified when the mode is

		entered/exited so poll(2) on the attribute wakes up.

		Entering/exiting a mode will also generate uevent KOBJ_CHANGE.



		Valid values: yes, no

Documentation/ABI/testing/configfs-usb-gadget-uvc

+5 −0
Original line number Diff line number Diff line
@@ -263,3 +263,8 @@ Description: Specific streaming header descriptors 
					is connected

		bmInfo			- capabilities of this video streaming

					interface



What:		/sys/class/udc/udc.name/device/gadget/video4linux/video.name/function_name

Date:		May 2018

KernelVersion:	4.19

Description:	UVC configfs function instance name

Documentation/ABI/testing/sysfs-bus-typec

0 → 100644
+51 −0
Original line number Diff line number Diff line 
What:		/sys/bus/typec/devices/.../active

Date:		July 2018

Contact:	Heikki Krogerus <heikki.krogerus@linux.intel.com>

Description:

		Shows if the mode is active or not. The attribute can be used

		for entering/exiting the mode. Entering/exiting modes is

		supported as synchronous operation so write(2) to the attribute

		does not return until the enter/exit mode operation has

		finished. The attribute is notified when the mode is

		entered/exited so poll(2) on the attribute wakes up.

		Entering/exiting a mode will also generate uevent KOBJ_CHANGE.



		Valid values are boolean.



What:		/sys/bus/typec/devices/.../description

Date:		July 2018

Contact:	Heikki Krogerus <heikki.krogerus@linux.intel.com>

Description:

		Shows description of the mode. The description is optional for

		the drivers, just like with the Billboard Devices.



What:		/sys/bus/typec/devices/.../mode

Date:		July 2018

Contact:	Heikki Krogerus <heikki.krogerus@linux.intel.com>

Description:

		The index number of the mode returned by Discover Modes USB

		Power Delivery command. Depending on the alternate mode, the

		mode index may be significant.



		With some alternate modes (SVIDs), the mode index is assigned

		for specific functionality in the specification for that

		alternate mode.



		With other alternate modes, the mode index values are not

		assigned, and can not be therefore used for identification. When

		the mode index is not assigned, identifying the alternate mode

		must be done with either mode VDO or the description.



What:		/sys/bus/typec/devices/.../svid

Date:		July 2018

Contact:	Heikki Krogerus <heikki.krogerus@linux.intel.com>

Description:

		The Standard or Vendor ID (SVID) assigned by USB-IF for this

		alternate mode.



What:		/sys/bus/typec/devices/.../vdo

Date:		July 2018

Contact:	Heikki Krogerus <heikki.krogerus@linux.intel.com>

Description:

		Shows the VDO in hexadecimal returned by Discover Modes command

		for this mode.

Documentation/ABI/testing/sysfs-class-typec

+2 −60
Original line number Diff line number Diff line
@@ -222,70 +222,12 @@ Description: 
		available. The value can be polled.





Alternate Mode devices.

USB Type-C port alternate mode devices.



The alternate modes will have Standard or Vendor ID (SVID) assigned by USB-IF.

The ports, partners and cable plugs can have alternate modes. A supported SVID

will consist of a set of modes. Every SVID a port/partner/plug supports will

have a device created for it, and every supported mode for a supported SVID will

have its own directory under that device. Below <dev> refers to the device for

the alternate mode.



What:		/sys/class/typec/<port|partner|cable>/<dev>/svid

Date:		April 2017

Contact:	Heikki Krogerus <heikki.krogerus@linux.intel.com>

Description:

		The SVID (Standard or Vendor ID) assigned by USB-IF for this

		alternate mode.



What:		/sys/class/typec/<port|partner|cable>/<dev>/mode<index>/

Date:		April 2017

Contact:	Heikki Krogerus <heikki.krogerus@linux.intel.com>

Description:

		Every supported mode will have its own directory. The name of

		a mode will be "mode<index>" (for example mode1), where <index>

		is the actual index to the mode VDO returned by Discover Modes

		USB power delivery command.



What:		/sys/class/typec/<port|partner|cable>/<dev>/mode<index>/description

Date:		April 2017

Contact:	Heikki Krogerus <heikki.krogerus@linux.intel.com>

Description:

		Shows description of the mode. The description is optional for

		the drivers, just like with the Billboard Devices.



What:		/sys/class/typec/<port|partner|cable>/<dev>/mode<index>/vdo

Date:		April 2017

Contact:	Heikki Krogerus <heikki.krogerus@linux.intel.com>

Description:

		Shows the VDO in hexadecimal returned by Discover Modes command

		for this mode.



What:		/sys/class/typec/<port|partner|cable>/<dev>/mode<index>/active

Date:		April 2017

Contact:	Heikki Krogerus <heikki.krogerus@linux.intel.com>

Description:

		Shows if the mode is active or not. The attribute can be used

		for entering/exiting the mode with partners and cable plugs, and

		with the port alternate modes it can be used for disabling

		support for specific alternate modes. Entering/exiting modes is

		supported as synchronous operation so write(2) to the attribute

		does not return until the enter/exit mode operation has

		finished. The attribute is notified when the mode is

		entered/exited so poll(2) on the attribute wakes up.

		Entering/exiting a mode will also generate uevent KOBJ_CHANGE.



		Valid values: yes, no



What:		/sys/class/typec/<port>/<dev>/mode<index>/supported_roles

What:		/sys/class/typec/<port>/<alt mode>/supported_roles

Date:		April 2017

Contact:	Heikki Krogerus <heikki.krogerus@linux.intel.com>

Description:

		Space separated list of the supported roles.



		This attribute is available for the devices describing the

		alternate modes a port supports, and it will not be exposed with

		the devices presenting the alternate modes the partners or cable

		plugs support.



		Valid values: source, sink

Documentation/ABI/testing/sysfs-driver-typec-displayport

0 → 100644
+49 −0
Original line number Diff line number Diff line 
What:		/sys/bus/typec/devices/.../displayport/configuration

Date:		July 2018

Contact:	Heikki Krogerus <heikki.krogerus@linux.intel.com>

Description:

		Shows the current DisplayPort configuration for the connector.

		Valid values are USB, source and sink. Source means DisplayPort

		source, and sink means DisplayPort sink.



		All supported configurations are listed as space separated list

		with the active one wrapped in square brackets.



		Source example:



			USB [source] sink



		The configuration can be changed by writing to the file



		Note. USB configuration does not equal to Exit Mode. It is

		separate configuration defined in VESA DisplayPort Alt Mode on

		USB Type-C Standard. Functionally it equals to the situation

		where the mode has been exited (to exit the mode, see

		Documentation/ABI/testing/sysfs-bus-typec, and use file

		/sys/bus/typec/devices/.../active).



What:		/sys/bus/typec/devices/.../displayport/pin_assignment

Date:		July 2018

Contact:	Heikki Krogerus <heikki.krogerus@linux.intel.com>

Description:

		VESA DisplayPort Alt Mode on USB Type-C Standard defines six

		different pin assignments for USB Type-C connector that are

		labeled A, B, C, D, E, and F. The supported pin assignments are

		listed as space separated list with the active one wrapped in

		square brackets.



		Example:



			C [D]



		Pin assignment can be changed by writing to the file. It is

		possible to set pin assignment before configuration has been

		set, but the assignment will not be active before the

		connector is actually configured.



		Note. As of VESA DisplayPort Alt Mode on USB Type-C Standard

		version 1.0b, pin assignments A, B, and F are deprecated. Only

		pin assignment D can now carry simultaneously one channel of

		USB SuperSpeed protocol. From user perspective pin assignments C

		and E are equal, where all channels on the connector are used

		for carrying DisplayPort protocol (allowing higher resolutions).

CRA Git | Maintained and supported by SUSTech CRA and CCSE