Allow sunrisepoint lp for supporting usb role switch

.gitignore

@@ -132,3 +132,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-class-rpmb

@@ -0,0 +1,57 @@
+What:		/sys/class/rpmb/
+Date:		Jul 2018
+KernelVersion:	4.18
+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 similar frame layout.
+		Such a partition provides authenticated and replay protected access,
+		hence suitable as a secure storage.
+
+What:		/sys/class/rpmb/rpmbN/
+Date:		Jul 2018
+KernelVersion:	4.18
+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:		Jul 2018
+KernelVersion:	4.18
+Contact:	Tomas Winkler <tomas.winkler@intel.com>
+Description:
+		The /sys/class/rpmb/rpmbN/type file contains device
+		underlying storage type technology: EMMC, UFS, NVMe.
+		In case of simulated device it will have :SIM suffix
+		i.e EMMC:SIM.
+
+What:		/sys/class/rpmb/rpmbN/id
+Date:		Jul 2018
+KernelVersion:	4.18
+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/wr_cnt_max
+Date:		Jul 2018
+KernelVersion:	4.18
+Contact:	Tomas Winkler <tomas.winkler@intel.com>
+Description:
+		The /sys/class/rpmb/rpmbN/wr_cnt_max file contains
+		number of blocks that can be reliable written in a single request.
+
+What:		/sys/class/rpmb/rpmbN/rd_cnt_max
+Date:		Jul 2018
+KernelVersion:	4.18
+Contact:	Tomas Winkler <tomas.winkler@intel.com>
+Description:
+		The /sys/class/rpmb/rpmbN/rd_cnt_max file contains
+		number of blocks that can be read in a single request.

Documentation/ABI/testing/sysfs-kernel-wakeup_reasons

@@ -0,0 +1,16 @@
+What:		/sys/kernel/wakeup_reasons/last_resume_reason
+Date:		February 2014
+Contact:	Ruchi Kandoi <kandoiruchi@google.com>
+Description:
+		The /sys/kernel/wakeup_reasons/last_resume_reason is
+		used to report wakeup reasons after system exited suspend.
+
+What:		/sys/kernel/wakeup_reasons/last_suspend_time
+Date:		March 2015
+Contact:	jinqian <jinqian@google.com>
+Description:
+		The /sys/kernel/wakeup_reasons/last_suspend_time is
+		used to report time spent in last suspend cycle. It contains
+		two numbers (in seconds) separated by space. First number is
+		the time spent in suspend and resume processes. Second number
+		is the time spent in sleep state.

Documentation/admin-guide/kernel-parameters.txt

@@ -880,6 +880,9 @@
 
 	dis_ucode_ldr	[X86] Disable the microcode loader.
 
+	dm=		[DM] Allows early creation of a device-mapper device.
+			See Documentation/device-mapper/boot.txt.
+
 	dma_debug=off	If the kernel is compiled with DMA_API_DEBUG support,
 			this option disables the debugging code at boot.
 
@@ -3899,6 +3902,9 @@
 			      reboot_cpu is s[mp]#### with #### being the processor
 					to be used for rebooting.
 
+	reboot_panic=	[KNL]
+			Same as reboot parameter above but only in case of panic.
+
 	relax_domain_level=
 			[KNL, SMP] Set scheduler's default relax_domain_level.
 			See Documentation/cgroup-v1/cpusets.txt.

Documentation/conf.py

@@ -403,6 +403,8 @@
      'The kernel development community', 'manual'),
     ('userspace-api/index', 'userspace-api.tex', 'The Linux kernel user-space API guide',
      'The kernel development community', 'manual'),
+    ('rpmb/index', 'rpmb.tex', 'Linux RPMB Subsystem Documentation',
+     'The kernel development community', 'manual'),
 ]
 
 # The name of an image file (relative to this directory) to place at the top of

Documentation/device-mapper/boot.txt

@@ -0,0 +1,42 @@
+Boot time creation of mapped devices
+===================================
+
+It is possible to configure a device mapper device to act as the root
+device for your system in two ways.
+
+The first is to build an initial ramdisk which boots to a minimal
+userspace which configures the device, then pivot_root(8) in to it.
+
+For simple device mapper configurations, it is possible to boot directly
+using the following kernel command line:
+
+dm="<name> <uuid> <ro>,table line 1,...,table line n"
+
+name = the name to associate with the device
+	after boot, udev, if used, will use that name to label
+	the device node.
+uuid = may be 'none' or the UUID desired for the device.
+ro = may be "ro" or "rw".  If "ro", the device and device table will be
+	marked read-only.
+
+Each table line may be as normal when using the dmsetup tool except for
+two variations:
+1. Any use of commas will be interpreted as a newline
+2. Quotation marks cannot be escaped and cannot be used without
+   terminating the dm= argument.
+
+Unless renamed by udev, the device node created will be dm-0 as the
+first minor number for the device-mapper is used during early creation.
+
+Example
+=======
+
+- Booting to a linear array made up of user-mode linux block devices:
+
+  dm="lroot none 0, 0 4096 linear 98:16 0, 4096 4096 linear 98:32 0" \
+  root=/dev/dm-0
+
+Will boot to a rw dm-linear target of 8192 sectors split across two
+block devices identified by their major:minor numbers.  After boot, udev
+will rename this target to /dev/mapper/lroot (depending on the rules).
+No uuid was assigned.

Documentation/devicetree/bindings/misc/memory-state-time.txt

@@ -0,0 +1,8 @@
+Memory bandwidth and frequency state tracking
+
+Required properties:
+- compatible : should be:
+       "memory-state-time"
+- freq-tbl: Should contain entries with each frequency in Hz.
+- bw-buckets: Should contain upper-bound limits for each bandwidth bucket in Mbps.
+       Must match the framework power_profile.xml for the device.

Documentation/devicetree/bindings/trusty/trusty-fiq-debugger.txt

@@ -0,0 +1,8 @@
+Trusty fiq debugger interface
+
+Provides a single fiq for the fiq debugger.
+
+Required properties:
+- compatible: compatible = "android,trusty-fiq-v1-*"; where * is a serial port.
+
+Must be a child of the node that provides fiq support ("android,trusty-fiq-v1").

Documentation/devicetree/bindings/trusty/trusty-fiq.txt

@@ -0,0 +1,8 @@
+Trusty fiq interface
+
+Trusty provides fiq emulation.
+
+Required properties:
+- compatible: "android,trusty-fiq-v1"
+
+Must be a child of the node that provides the trusty std/fast call interface.

Documentation/devicetree/bindings/trusty/trusty-irq.txt

@@ -0,0 +1,67 @@
+Trusty irq interface
+
+Trusty requires non-secure irqs to be forwarded to the secure OS.
+
+Required properties:
+- compatible: "android,trusty-irq-v1"
+
+Optional properties:
+
+- interrupt-templates: is an optional property that works together
+  with "interrupt-ranges" to specify secure side to kernel IRQs mapping.
+
+  It is a list of entries, each one of which defines a group of interrupts
+  having common properties, and has the following format:
+    < phandle irq_id_pos [templ_data]>
+      phandle - phandle of interrupt controller this template is for
+      irq_id_pos - the position of irq id in interrupt specifier array
+                   for interrupt controller referenced by phandle.
+      templ_data - is an array of u32 values (could be empty) in the same
+                   format as interrupt specifier for interrupt controller
+                   referenced by phandle but with omitted irq id field.
+
+- interrupt-ranges: list of entries that specifies secure side to kernel
+  IRQs mapping.
+
+  Each entry in the "interrupt-ranges" list has the following format:
+    <beg end templ_idx>
+      beg - first entry in this range
+      end - last entry in this range
+      templ_idx  - index of entry in "interrupt-templates" property
+                   that must be used as a template for all interrupts
+                   in this range
+
+Example:
+{
+	gic: interrupt-controller@50041000 {
+		compatible = "arm,gic-400";
+		#interrupt-cells = <3>;
+		interrupt-controller;
+		...
+	};
+	...
+	IPI: interrupt-controller {
+		compatible = "android,CustomIPI";
+		#interrupt-cells = <1>;
+		interrupt-controller;
+	};
+	...
+	trusty {
+		compatible = "android,trusty-smc-v1";
+		ranges;
+		#address-cells = <2>;
+		#size-cells = <2>;
+
+		irq {
+			compatible = "android,trusty-irq-v1";
+			interrupt-templates = <&IPI 0>,
+					      <&gic 1 GIC_PPI 0>,
+					      <&gic 1 GIC_SPI 0>;
+			interrupt-ranges = < 0  15 0>,
+					   <16  31 1>,
+					   <32 223 2>;
+		};
+	}
+}
+
+Must be a child of the node that provides the trusty std/fast call interface.