cm13 - cm14.1 cyanogen kernel

Documentation/devicetree/bindings/fb/mdss-mdp.txt

@@ -402,8 +402,36 @@ Fudge Factors:			Fudge factors are used to boost demand for
 				applied in scenarios where panel interface can
 				be more tolerant to memory latency such as
 				command mode panels.
-- qcom,max-bandwidth-per-pipe-kbps: This value indicates the max bandwidth in KB
-				that a single pipe can support without underflow.
+- qcom,max-bandwidth-per-pipe-kbps: A two dimensional array indicating the max
+				bandwidth in KB that a single pipe can support
+				without underflow for various usecases. The
+				first parameter indicates the usecase and the
+				second parameter gives the max bw allowed for
+				the usecase. Following are the enum values for
+				modes in different cases:
+				For default case, mode = 1
+				camera usecase, mode = 2
+				hflip usecase, mode = 4
+				vflip usecase, mode = 8
+				First parameter/mode value need to match enum,
+				mdss_mdp_max_bw_mode, present in
+				include/uapi/linux/msm_mdp.h.
+- qcom,max-bw-settings:         This two dimension array indicates the max bandwidth
+				in KB that has to be supported when particular
+				scenarios are involved such as camera, flip.
+				The first parameter indicate the
+				scenario/usecase and second paramter indicate
+				the maximum bandwidth for that usecase.
+				Following are the enum values for modes in different
+				cases:
+				For default case, mode = 1
+				camera usecase, mode = 2
+				hflip usecase, mode = 4
+				vflip usecase, mode = 8
+				First parameter/mode value need to match enum,
+				mdss_mdp_max_bw_mode, present in
+				include/uapi/linux/msm_mdp.h.
+
 - qcom,mdss-has-panic-ctrl: Boolean property to indicate if panic/robust signal
 				control feature is available or not.
 - qcom,mdss-pipe-vig-panic-ctrl-offsets: Array of panic/robust signal offsets
@@ -523,6 +551,13 @@ Example:
 
 		qcom,max-bandwidth-low-kbps = <2300000>;
 		qcom,max-bandwidth-high-kbps = <3000000>;
+		qcom,max-bandwidth-per-pipe-kbps = <4 2100000>,
+						   <8 1800000>;
+		qcom,max-bw-settings = <1 2300000>,
+				       <2 1700000>,
+				       <4 2300000>,
+				       <8 2000000>;
+
 		qcom,max-mixer-width = <2048>;
 		qcom,max-clk-rate = <320000000>;
 		qcom,vbif-settings = <0x0004 0x00000001>,

Documentation/devicetree/bindings/input/misc/bmi160.txt

@@ -0,0 +1,49 @@
+BOSCH 6-axis accelerometer and gyroscope sensor driver.
+
+Required properties:
+
+ - compatible		: Should be "bosch,bmi160".
+ - reg			: i2c slave address of the device.
+ - pinctrl-names	: Pinctrl configuration names of this sensor driver.
+				Should be "default".
+ - pinctrl-0		: The pinctrl node corresponding to "default",
+				should be <&bmi160_int1_default &bmi160_int2_default>.
+ - interrupt-parent	: Parent of interrupt.
+ - interrupts		: Accelerometer interrupts to indicate new data ready or events.
+ - vdd-supply		: Analog power supply needed to power device.
+ - vio-supply		: Digital IO power supply needed for IO and I2C.
+ - bosch,init-interval	: Initial data polling interval in millisecond.
+ - bosch,place		: The placing of the accelerometer on board. There are 8
+				patterns of placing described as below:
+				0: 1st pin is right down
+				1: 1st pin is left down
+				2: 1st pin is left top
+				3: 1st pin is right top
+				4: 1st pin is left down (from top view)
+				5: 1st pin is left top (from top view)
+				6: 1st pin is right top (from top view)
+				7: 1st pin is right down (from top view)
+
+Optional properties:
+
+ - bosch,gpio-int1	: 1st irq gpio which is to provide interrupts
+				to host, interrupt events can be route to any of
+				these two irq pins according device configuration.
+ - bosch,gpio-int2	: 2nd irq gpio which is to provide interrupts
+				to host.
+Example:
+&i2c_0 { /* BLSP1 QUP2 */
+	 bosch@68 { /* Accelerometer and Gyroscope sensor */
+		compatible = "bosch,bmi160";
+		reg = <0x68>;
+		pinctrl-names = "default";
+		pinctrl-0 = <&bmi160_int1_default>;
+		interrupt-parent = <&msm_gpio>;
+		interrupts = <96 0x2002>;
+		vdd-supply = <&pm8916_l17>;
+		vio-supply = <&pm8916_l6>;
+		bosch,init-interval = <200>;
+		bosch,place = <1>;
+		bosch,gpio-int1 = <&msm_gpio 96 0x2002>;
+	};
+};

Documentation/devicetree/bindings/input/misc/mmc3x30.txt

@@ -0,0 +1,58 @@
+MEMSIC MMC3x30 3-axis magnetic sensor
+
+The MEMSIC 3-axis magnetic sensor is a complete 3-axis magnetic sensor with
+on-chip signal processing and intergrated i2c bus. It can be connected to host
+processor via i2c. It can measure magnetic fields within the full scale range
+from -16 Gauss to +16 Gauss.
+
+Required properties:
+
+ - compatible		: Should be "memsic,mmc3x30".
+ - reg			: i2c address of the device.
+ - vdd-supply		: Analog power supply needed to power up the device.
+ - vio-supply		: Digital IO power supply needed for IO and I2C.
+ - memsic,dir		: String value of the direction of the ecompass sensor
+	chip. There are 8 patterns of direction:
+
+
+       x > 0 /___________o
+               /        /|
+              /        / |* 1st pin is here
+             /________/ /|
+             |_______/|/ |/ z > 0
+                    /
+                  |/ y > 0
+
+
+		The above graph shows the coordinate of the sensor chip. Specify the
+		following string to memsic,dir to convert it into Android coordinate.
+		Note the definition of sensor placement on target board is relative to
+		Android portrait mode.
+
+						left	right	up	down
+		obverse-x-axis-forward	Y+	Y-	X+	X-
+		obverse-x-axis-rightward	X-	X+	Y+	Y-
+		obverse-x-axis-backward	Y-	Y+	X-	X+
+		obverse-x-axis-leftward	X+	X-	Y-	Y+
+		reverse-x-axis-forward	Y-	Y+	X+	X-
+		reverse-x-axis-rightward	X-	X+	Y-	Y+
+		reverse-x-axis-backward	Y+	Y-	X-	X+
+		reverse-x-axis-leftward	X+	X-	Y+	Y-
+
+Optional properites:
+
+ - memsic,auto-report	: Boolean value to indicate if enable auto-report mode.
+
+ Example:
+	A chip on 8916 platform with the pattern as the above graph:
+	&i2c_0 { /* BLSP1 QUP2 */
+		memsic@30 {
+				compatible = "memsic,mmc3x30";
+				reg = <0x30>;
+				vdd-supply = <&pm8916_l17>;
+				vio-supply = <&pm8916_l6>;
+				memsic,dir = "obverse-x-axis-forward";
+				memsic,auto-report;
+		};
+	};
+

Documentation/networking/ip-sysctl.txt

@@ -1276,6 +1276,13 @@ router_solicitations - INTEGER
 	routers are present.
 	Default: 3
 
+use_oif_addrs_only - BOOLEAN
+	When enabled, the candidate source addresses for destinations
+	routed via this interface are restricted to the set of addresses
+	configured on this interface (vis. RFC 6724, section 4).
+
+	Default: false
+
 use_tempaddr - INTEGER
 	Preference for Privacy Extensions (RFC3041).
 	  <= 0 : disable Privacy Extensions
@@ -1357,6 +1364,19 @@ ndisc_notify - BOOLEAN
 	1 - Generate unsolicited neighbour advertisements when device is brought
 	    up or hardware address changes.
 
+optimistic_dad - BOOLEAN
+	Whether to perform Optimistic Duplicate Address Detection (RFC 4429).
+		0: disabled (default)
+		1: enabled
+
+use_optimistic - BOOLEAN
+	If enabled, do not classify optimistic addresses as deprecated during
+	source address selection.  Preferred addresses will still be chosen
+	before optimistic addresses, subject to other ranking in the source
+	address selection algorithm.
+		0: disabled (default)
+		1: enabled
+
 icmp/*:
 ratelimit - INTEGER
 	Limit the maximal rates for sending ICMPv6 packets.

Documentation/sysctl/kernel.txt

@@ -447,7 +447,6 @@ This file shows up if CONFIG_DEBUG_STACKOVERFLOW is enabled.
 
 0: try to continue operation.
 
-1: panic immediately.
 
 ==============================================================
 

Documentation/sysctl/vm.txt

@@ -42,6 +42,8 @@ Currently, these files are in /proc/sys/vm:
 - min_slab_ratio
 - min_unmapped_ratio
 - mmap_min_addr
+- mmap_rnd_bits
+- mmap_rnd_compat_bits
 - nr_hugepages
 - nr_overcommit_hugepages
 - nr_trim_pages         (only if CONFIG_MMU=n)
@@ -455,6 +457,33 @@ against future potential kernel bugs.
 
 ==============================================================
 
+mmap_rnd_bits:
+
+This value can be used to select the number of bits to use to
+determine the random offset to the base address of vma regions
+resulting from mmap allocations on architectures which support
+tuning address space randomization.  This value will be bounded
+by the architecture's minimum and maximum supported values.
+
+This value can be changed after boot using the
+/proc/sys/vm/mmap_rnd_bits tunable
+
+==============================================================
+
+mmap_rnd_compat_bits:
+
+This value can be used to select the number of bits to use to
+determine the random offset to the base address of vma regions
+resulting from mmap allocations for applications run in
+compatibility mode on architectures which support tuning address
+space randomization.  This value will be bounded by the
+architecture's minimum and maximum supported values.
+
+This value can be changed after boot using the
+/proc/sys/vm/mmap_rnd_compat_bits tunable
+
+==============================================================
+
 nr_hugepages
 
 Change the minimum size of the hugepage pool.