Revert Patch: Noise at DSD Playback start.

.gitignore

@@ -7,38 +7,40 @@
 # command after changing this file, to see if there are
 # any tracked files which get ignored after the change.
 #
-# Normal rules
+# Normal rules (sorted alphabetically)
 #
 .*
+*.a
+*.bin
+*.bz2
+*.c.[012]*.*
+*.dtb
+*.dtb.S
+*.dwo
+*.elf
+*.gcno
+*.gz
+*.i
+*.ko
+*.ll
+*.lst
+*.lz4
+*.lzma
+*.lzo
+*.mod.c
 *.o
 *.o.*
-*.a
+*.order
+*.patch
 *.s
-*.ko
 *.so
 *.so.dbg
-*.mod.c
-*.i
-*.lst
+*.su
 *.symtypes
-*.order
-*.elf
-*.bin
 *.tar
-*.gz
-*.bz2
-*.lzma
 *.xz
-*.lz4
-*.lzo
-*.patch
-*.gcno
-*.ll
-modules.builtin
 Module.symvers
-*.dwo
-*.su
-*.c.[012]*.*
+modules.builtin
 
 #
 # Top-level generic files
@@ -53,6 +55,11 @@ Module.symvers
 /System.map
 /Module.markers
 
+#
+# RPM spec file (make rpm-pkg)
+#
+/*.spec
+
 #
 # Debian directory (make deb-pkg)
 #
@@ -115,3 +122,6 @@ all.config
 
 # Kdevelop4
 *.kdev4
+
+# fetched Android config fragments
+kernel/configs/android-*.cfg

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

@@ -0,0 +1,9 @@
+What:		/config/usb-gadget/<gadget>/functions/dvctrace.<name>/source_dev
+Date:		Mar 2015
+KernelVersion:	4.0
+Contact:	Traian Schiau <traianx.schiau@intel.com>
+Description:	(R) The name of the source device paired with this function
+		instance, if upon creation of the instance a source device
+		named <name> exists and is free, the source device will be
+		associated with the current instance, otherwise the first free
+		source device will be used.

Documentation/ABI/testing/sysfs-bus-dvctrace

@@ -0,0 +1,68 @@
+What:		/sys/bus/dvctrace
+Date:		May 2015
+KernelVersion:	4.0
+Contact:	Traian Schiau <traianx.schiau@intel.com>
+Description:	Groups the devices and drivers registered to
+		to dvc-trace bus.
+
+What:		/sys/bus/dvctrace/devices/<device>/status
+Date:		May 2015
+KernelVersion:	4.0
+Contact:	Traian Schiau <traianx.schiau@intel.com>
+Description:	(R) The status of a dvc-trace source device with
+		respect to an USB function driver.
+		  Free - The device is free
+		  Reserved - The device is reserved by an USB
+			function but not in use.
+		  In use - The device is used by an USB function.
+
+What:		/sys/bus/dvctrace/devices/<device>/protocol
+Date:		May 2015
+KernelVersion:	4.0
+Contact:	Traian Schiau <traianx.schiau@intel.com>
+Description:	(RW) The protocol id of a dvc-trace source device,
+		this will used in function driver interface
+		descriptors (u8). According to USB debug class
+		specification the protocol id is vendor specific.
+
+What:		/sys/bus/dvctrace/devices/<device>/descriptors
+Date:		May 2015
+KernelVersion:	4.0
+Contact:	Traian Schiau <traianx.schiau@intel.com>
+Description:	(RW) Hex-dump of the descriptors provided by the
+		source device.
+		eg. A debug class output connection descriptor
+		09 24 02 04 03 00 00 00 00
+		ll tt ss xx xx xx xx xx ii
+		 |  |  |                 +- iConnection string id.
+		 |  |  +- Descriptor sub-type DC_OUTPUT_CONNECTION
+		 |  +- Descriptor type (USB_DT_CS_INTERFACE)
+		 +- Descriptor length
+		Writing:
+		  - is not allowed while the device is Reserved or In Use.
+		  - will replace all the descriptors currently present.
+		  - will remove any strings previously provided.
+		  - should use the same format.
+		  - accepts multiple descriptors separated by space or '\n'.
+
+What:		/sys/bus/dvctrace/devices/<device>/strings
+Date:		May 2015
+KernelVersion:	4.0
+Contact:	Traian Schiau <traianx.schiau@intel.com>
+Description:	(RW) Currently set usb descriptor strings in
+		<descriptor_index>.<offset>: string format.
+		<descriptor_index>.<offset> identifies the location where
+		the string id is needed.
+		eg. Having the same debug class output connection descriptor,
+		as the first descriptor.
+		09 24 02 04 03 00 00 00 00
+		ll tt ss xx xx xx xx xx ii
+		                         +- iConnection string id.
+		0.8: My output connection - will identify the string associated
+		with this descriptor.
+		Writing:
+		  - is not allowed while the device is Reserved or In Use.
+		  - will replace all the strings currently present.
+		  - should use the same format.
+		  - accepts multiple strings separated by ";" or '\n'.
+		    eg. "0.4: first string; 1.4: second string"

Documentation/ABI/testing/sysfs-bus-dvctrace-devices-dvcith

@@ -0,0 +1,68 @@
+What:		/sys/bus/dvctrace/devices/dvcith-<device>/msc
+Date:		Aug 2015
+KernelVersion:	4.0
+Contact:	Traian Schiau <traianx.schiau@intel.com>
+Description:	(R) Symbolic link to the Intel Trace Hub MSC
+		(Memory Storage Controller) sub-device used to get tracing data.
+
+What:		/sys/bus/dvctrace/devices/dvcith-<device>/mdd_min_transfer
+Date:		Aug 2015
+KernelVersion:	4.0
+Contact:	Traian Schiau <traianx.schiau@intel.com>
+Description:	(RW) Window transfer watermark, the driver will queue a
+		new transfer only if at least <mdd_min_transfer> bytes
+		of trace data is available. Since on every switch @48 bytes
+		of trace data is generated, this should not be set under this
+		threshold.
+		Default 2048
+
+What:		/sys/bus/dvctrace/devices/dvcith-<device>/mdd_retry_timeout
+Date:		Aug 2015
+KernelVersion:	4.0
+Contact:	Traian Schiau <traianx.schiau@intel.com>
+Description:	(RW) Read retry interval, If by the time the last usb transfer
+		is complete, there is no new data to be sent the driver will
+		sleep <mdd_retry_timeout> ms, before checking again.
+		Default: 2 ms
+
+What:		/sys/bus/dvctrace/devices/dvcith-<device>/mdd_max_retry
+Date:		Aug 2015
+KernelVersion:	4.0
+Contact:	Traian Schiau <traianx.schiau@intel.com>
+Description:	(RW) the maximum retries to be bone before triggering a switch
+		and sending the currently available data regardless of the
+		available size.
+		Default: 150
+
+What:		/sys/bus/dvctrace/devices/dvcith-<device>/mdd_proc_type
+Date:		Aug 2015
+KernelVersion:	4.0
+Contact:	Traian Schiau <traianx.schiau@intel.com>
+Description:	(RW) Data process type, during DvC tracing the MSC is set up in
+		Multi Window mode (check Intel Trace Hub Developer's Manual for
+		details), This attribute specifies what the dvc-trace data stream
+		should contain.
+		Available values are:
+		  - 1 - Full blocks,
+		  - 2 - Trimmed blocks (Block header + STP data)
+		  - 3 - STP data only.
+		Default 3.
+
+What:		/sys/bus/dvctrace/devices/dvcith-<device>/mdd_transfer_type
+Date:		Aug 2015
+KernelVersion:	4.0
+Contact:	Traian Schiau <traianx.schiau@intel.com>
+Description:	(RW) Data transfer type, This attribute specifies how the trace data
+		is queued in the USB requests.
+		Available values are:
+		  - 1 - Auto,
+		  - 2 - SG-List,
+		  - 3 - Linear buffer.
+		Default 1.
+
+What:		/sys/bus/dvctrace/devices/dvcith-<device>/mdd_stats
+Date:		Aug 2015
+KernelVersion:	4.0
+Contact:	Traian Schiau <traianx.schiau@intel.com>
+Description:	(R) Provides statistical information regarding the latest.
+		trace session. Available if (CONFIG_INTEL_TH_MSU_DVC_DEBUG).

Documentation/ABI/testing/sysfs-bus-iio

@@ -32,7 +32,7 @@ Description:
 		Description of the physical chip / device for device X.
 		Typically a part number.
 
-What:		/sys/bus/iio/devices/iio:deviceX/timestamp_clock
+What:		/sys/bus/iio/devices/iio:deviceX/current_timestamp_clock
 KernelVersion:	4.5
 Contact:	linux-iio@vger.kernel.org
 Description:

Documentation/ABI/testing/sysfs-class-dual-role-usb

@@ -0,0 +1,71 @@
+What:		/sys/class/dual_role_usb/.../
+Date:		June 2015
+Contact:	Badhri Jagan Sridharan<badhri@google.com>
+Description:
+		Provide a generic interface to monitor and change
+		the state of dual role usb ports. The name here
+		refers to the name mentioned in the
+		dual_role_phy_desc that is passed while registering
+		the dual_role_phy_intstance through
+		devm_dual_role_instance_register.
+
+What:           /sys/class/dual_role_usb/.../supported_modes
+Date:           June 2015
+Contact:        Badhri Jagan Sridharan<badhri@google.com>
+Description:
+		This is a static node, once initialized this
+		is not expected to change during runtime. "dfp"
+		refers to "downstream facing port" i.e. port can
+		only act as host. "ufp" refers to "upstream
+		facing port" i.e. port can only act as device.
+		"dfp ufp" refers to "dual role port" i.e. the port
+		can either be a host port or a device port.
+
+What:		/sys/class/dual_role_usb/.../mode
+Date:		June 2015
+Contact:	Badhri Jagan Sridharan<badhri@google.com>
+Description:
+		The mode node refers to the current mode in which the
+		port is operating. "dfp" for host ports. "ufp" for device
+		ports and "none" when cable is not connected.
+
+		On devices where the USB mode is software-controllable,
+		userspace can change the mode by writing "dfp" or "ufp".
+		On devices where the USB mode is fixed in hardware,
+		this attribute is read-only.
+
+What:		/sys/class/dual_role_usb/.../power_role
+Date:		June 2015
+Contact:	Badhri Jagan Sridharan<badhri@google.com>
+Description:
+		The power_role node mentions whether the port
+		is "sink"ing or "source"ing power. "none" if
+		they are not connected.
+
+		On devices implementing USB Power Delivery,
+		userspace can control the power role by writing "sink" or
+		"source". On devices without USB-PD, this attribute is
+		read-only.
+
+What:		/sys/class/dual_role_usb/.../data_role
+Date:		June 2015
+Contact:	Badhri Jagan Sridharan<badhri@google.com>
+Description:
+		The data_role node mentions whether the port
+		is acting as "host" or "device" for USB data connection.
+		"none" if there is no active data link.
+
+		On devices implementing USB Power Delivery, userspace
+		can control the data role by writing "host" or "device".
+		On devices without USB-PD, this attribute is read-only
+
+What:		/sys/class/dual_role_usb/.../powers_vconn
+Date:		June 2015
+Contact:	Badhri Jagan Sridharan<badhri@google.com>
+Description:
+		The powers_vconn node mentions whether the port
+		is supplying power for VCONN pin.
+
+		On devices with software control of VCONN,
+		userspace can disable the power supply to VCONN by writing "n",
+		or enable the power supply by writing "y".

Documentation/ABI/testing/sysfs-class-rpmb

@@ -0,0 +1,47 @@
+What:		/sys/class/rpmb/
+Date:		Jun 2017
+KernelVersion:	4.12
+Contact:	Tomas Winkler <tomas.winkler@intel.com>
+Description:
+		The rpmb/ class sub-directory belongs to RPMB device class.
+
+		Few storage technologies such is EMMC, UFS, and NVMe support
+		Replay Protected Memory Block (RPMB) hardware partition with
+		common protocol and frame layout.
+		Such a partition provides authenticated and replay protected access,
+		hence suitable as a secure storage.
+
+What:		/sys/class/rpmb/rpmbN/
+Date:		Jun 2017
+KernelVersion:	4.12
+Contact:	Tomas Winkler <tomas.winkler@intel.com>
+Description:
+		The /sys/class/rpmb/rpmbN directory is created for
+		each RPMB registered device.
+
+What:		/sys/class/rpmb/rpmbN/type
+Date:		Jun 2017
+KernelVersion:	4.12
+Contact:	Tomas Winkler <tomas.winkler@intel.com>
+Description:
+		The /sys/class/rpmb/rpmbN/type file contains device
+		underlaying storage type technology: EMMC, UFS, SIM.
+
+What:		/sys/class/rpmb/rpmbN/id
+Date:		Jun 2017
+KernelVersion:	4.12
+Contact:	Tomas Winkler <tomas.winkler@intel.com>
+Description:
+		The /sys/class/rpmb/rpmbN/id file contains unique device id
+		in a binary form as defined by underlying storage device.
+		In case of multiple RPMB devices a user can determine correct
+		device.
+		The content can be parsed according the storage device type.
+
+What:		/sys/class/rpmb/rpmbN/reliable_wr_cnt
+Date:		Jun 2017
+KernelVersion:	4.12
+Contact:	Tomas Winkler <tomas.winkler@intel.com>
+Description:
+		The /sys/class/rpmb/rpmbN/reliable_wr_cnt file contains
+		number of blocks that can be reliable written in a single request.

Documentation/ABI/testing/sysfs-devices-system-cpu

@@ -373,3 +373,19 @@ Contact:	Linux kernel mailing list <linux-kernel@vger.kernel.org>
 Description:	information about CPUs heterogeneity.
 
 		cpu_capacity: capacity of cpu#.
+
+What:		/sys/devices/system/cpu/vulnerabilities
+		/sys/devices/system/cpu/vulnerabilities/meltdown
+		/sys/devices/system/cpu/vulnerabilities/spectre_v1
+		/sys/devices/system/cpu/vulnerabilities/spectre_v2
+Date:		January 2018
+Contact:	Linux kernel mailing list <linux-kernel@vger.kernel.org>
+Description:	Information about CPU vulnerabilities
+
+		The files are named after the code names of CPU
+		vulnerabilities. The output of those files reflects the
+		state of the CPUs in the system. Possible output values:
+
+		"Not affected"	  CPU is not affected by the vulnerability
+		"Vulnerable"	  CPU is affected and no mitigation in effect
+		"Mitigation: $M"  CPU is affected and mitigation $M is in effect