Merge tag 'usb-4.13-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb (362f6729) · Commits · 戴 / test

Documentation/ABI/stable/sysfs-class-udc

+8 −8

Original line number	Diff line number	Diff line
		@@ -55,14 +55,6 @@ Description:
		Indicates the maximum USB speed supported by this port.
		Users:

		What: /sys/class/udc/<udc>/maximum_speed
		Date: June 2011
		KernelVersion: 3.1
		Contact: Felipe Balbi <balbi@kernel.org>
		Description:
		Indicates the maximum USB speed supported by this port.
		Users:

		What: /sys/class/udc/<udc>/soft_connect
		Date: June 2011
		KernelVersion: 3.1
		@@ -91,3 +83,11 @@ Description:
		'configured', and 'suspended'; however not all USB Device
		Controllers support reporting all states.
		Users:

		What: /sys/class/udc/<udc>/function
		Date: June 2017
		KernelVersion: 4.13
		Contact: Felipe Balbi <balbi@kernel.org>
		Description:
		Prints out name of currently running USB Gadget Driver.
		Users:

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

+10 −8

Original line number	Diff line number	Diff line
		What: /config/usb-gadget/gadget/functions/uac1.name
		Date: Sep 2014
		KernelVersion: 3.18
		Date: June 2017
		KernelVersion: 4.14
		Description:
		The attributes:

		audio_buf_size - audio buffer size
		fn_cap - capture pcm device file name
		fn_cntl - control device file name
		fn_play - playback pcm device file name
		req_buf_size - ISO OUT endpoint request buffer size
		req_count - ISO OUT endpoint request count
		c_chmask - capture channel mask
		c_srate - capture sampling rate
		c_ssize - capture sample size (bytes)
		p_chmask - playback channel mask
		p_srate - playback sampling rate
		p_ssize - playback sample size (bytes)
		req_number - the number of pre-allocated request
		for both capture and playback

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

0 → 100644

+12 −0

Original line number	Diff line number	Diff line
		What: /config/usb-gadget/gadget/functions/uac1_legacy.name
		Date: Sep 2014
		KernelVersion: 3.18
		Description:
		The attributes:

		audio_buf_size - audio buffer size
		fn_cap - capture pcm device file name
		fn_cntl - control device file name
		fn_play - playback pcm device file name
		req_buf_size - ISO OUT endpoint request buffer size
		req_count - ISO OUT endpoint request count

Documentation/ABI/testing/sysfs-class-typec

+15 −0

Original line number	Diff line number	Diff line
		@@ -30,6 +30,21 @@ Description:

		Valid values: source, sink

		What: /sys/class/typec/<port>/port_type
		Date: May 2017
		Contact: Badhri Jagan Sridharan <Badhri@google.com>
		Description:
		Indicates the type of the port. This attribute can be used for
		requesting a change in the port type. Port type change is
		supported as a synchronous operation, so write(2) to the
		attribute will not return until the operation has finished.

		Valid values:
		- source (The port will behave as source only DFP port)
		- sink (The port will behave as sink only UFP port)
		- dual (The port will behave as dual-role-data and
		dual-role-power port)

		What: /sys/class/typec/<port>/vconn_source
		Date: April 2017
		Contact: Heikki Krogerus <heikki.krogerus@linux.intel.com>

Documentation/devicetree/bindings/leds/common.txt

+33 −2

Original line number	Diff line number	Diff line
		Common leds properties.
		* Common leds properties.

		LED and flash LED devices provide the same basic functionality as current
		regulators, but extended with LED and flash LED specific features like
		@@ -49,6 +49,22 @@ Optional properties for child nodes:
		- panic-indicator : This property specifies that the LED should be used,
		if at all possible, as a panic indicator.

		- trigger-sources : List of devices which should be used as a source triggering
		this LED activity. Some LEDs can be related to a specific
		device and should somehow indicate its state. E.g. USB 2.0
		LED may react to device(s) in a USB 2.0 port(s).
		Another common example is switch or router with multiple
		Ethernet ports each of them having its own LED assigned
		(assuming they are not hardwired). In such cases this
		property should contain phandle(s) of related source
		device(s).
		In many cases LED can be related to more than one device
		(e.g. one USB LED vs. multiple USB ports). Each source
		should be represented by a node in the device tree and be
		referenced by a phandle and a set of phandle arguments. A
		length of arguments should be specified by the
		#trigger-source-cells property in the source node.

		Required properties for flash LED child nodes:
		- flash-max-microamp : Maximum flash LED supply current in microamperes.
		- flash-max-timeout-us : Maximum timeout in microseconds after which the flash
		@@ -59,7 +75,17 @@ property can be omitted.
		For controllers that have no configurable timeout the flash-max-timeout-us
		property can be omitted.

		Examples:
		* Trigger source providers

		Each trigger source should be represented by a device tree node. It may be e.g.
		a USB port or an Ethernet device.

		Required properties for trigger source:
		- #trigger-source-cells : Number of cells in a source trigger. Typically 0 for
		nodes of simple trigger sources (e.g. a specific USB
		port).

		* Examples

		gpio-leds {
		compatible = "gpio-leds";
		@@ -69,6 +95,11 @@ gpio-leds {
		linux,default-trigger = "heartbeat";
		gpios = <&gpio0 0 GPIO_ACTIVE_HIGH>;
		};

		usb {
		gpios = <&gpio0 1 GPIO_ACTIVE_HIGH>;
		trigger-sources = <&ohci_port1>, <&ehci_port1>;
		};
		};

		max77693-led {

Admin message