Promotion of kernel.lnx.4.4-160512.

* Battery Current Limit

This Battery Current Limit(BCL) device, provides an interface to detect and notify

interested applications when the SOC is drawing current in excess of the limits

specified.

The BCL driver has another operation mode, where it monitors the battery

current and voltage via ADC TM hardware called BTM. The newer devices support

a BTM hardware configuration, which can measure the battery current and voltage.

This ADC hardware is capable of sampling the sensor every 1 msec and interrupts

the BCL driver, which in turn mitigates the CPU frequency based on the

current load thresholds. The BCL drivers operation mode is decided based

on the parameters given in the device tree. In this BTM operation mode, BCL

driver provides sysfs entries to configure the thresholds, ADC polling

timer interval and other operational parameters.

The device tree parameters for bcl are:

Required parameters:

- compatible: Must be "qcom,bcl"

Optional parameters:

- qcom,bcl-enable : If this property is defined, BCL functionality will

		be enabled from boot. The mode of operation, will be based

		on the properties defined in the device tree.

- qcom,ibat-vadc = <&vadc_phandle>: A phandle to the VADC device. The BTM mode

		of operation requires this property to be defined if and only

		if qcom,ibat-threshold-adc_tm and qcom,ibat-monitor are defined.

		Error in any of these properties will disable BTM mode of operation

		and will fall back to the available current monitor mode.

- qcom,ibat-threshold-adc_tm = <&vadc_tm_phandle>: A phandle to the ADC TM

		device. BCL registers with the hardware monitor for this TM

		device to be able to set thresholds and get threshold

		notifications. The BTM mode of operation requires this property

		to be defined if and only if qcom,ibat-vadc and qcom,ibat-monitor

		are defined. Error in any of these properties will disable BTM

		mode of operation and will fall back to the available current

		monitor mode.

- qcom,bcl-framework-interface: If this property is defined, then the BCL uses

		the BCL framework for monitoring battery voltage and current.

		When this property is defined, the 'qcom,high-threshold-uamp',

		'qcom,low-threshold-uamp', 'qcom,mitigation-freq-khz',

		'qcom,vph-high-threshold-uv', 'qcom,vph-low-threshold-uv' and

		'qcom,thermal-handle' properties should be defined in the

		'qcom,ibat-monitor' node.

- qcom,bcl-hotplug-list = <hotplug-phandle-list>: List of phandles to the cores

		that are to be hotplugged, when battery current limit condition

		is reached.

- qcom,bcl-soc-hotplug-list: List of phandles to the cores that are to be hotplugged,

		when battery SOC limit condition is reached.

- qcom,bcl-freq-control-list: List of phandles to the cores that are to be frequency

                mitigated when BCL condition is reached.

- qcom,bcl-no-bms: This is an optional node for BCL IAVAIL monitor mode.

		If this property is defined, BCL IAVAIL monitor gets rbat value

		from power supply battery module instead of bms module.

Optional nodes:

- qcom,ibat-monitor: This optional node defines all the parameters for the

		battery current monitoring. The BTM mode of operation requires

		all the below properties to be defined with valid values. Also,

		this node should be defined if and only if qcom,ibat-vadc and

		qcom,ibat-threshold-adc_tm are defined. Error in any of these

		properties will disable BTM mode of operation and will fall

		back to the available current monitor mode.

	* qcom,high-threshold-uamp: The battery current, in microampere, after

		which the BCL driver should cap the maximum frequency.

	* qcom,low-threshold-uamp: The battery current, in microampere, below

		which the BCL driver should clear the CPU frequency mitigation.

	* qcom,mitigation-freq-khz: The maximum frequency value the BCL driver

		should mitigate the CPUS's with. This frequency shouldn't be

		less than the minimum frequency request that the kernel thermal

		monitor driver places during vdd restriction.

	* qcom,ibat-channel: The ADC hardware's Ibat channel number.

	* qcom,uv-to-ua-numerator: The conversion parameter required for converting

		the voltage measure from ADC hardware to current value.

	* qcom,uv-to-ua-denominator: The conversion parameter required for

		converting the voltage measure from ADC hardware to current.

		The microvolt to microampere (or vice-versa) conversion uses

		the below conversion formulae.

		ua = (uv * uv-to-ua-numerator) / uv-to-ua-denominator

	* qcom,adc-interval-usec: The polling interval, in microseconds, for the ADC

		hardware.

	* qcom,vph-channel: The ADC hardware's Vph channel number.

	* qcom,vph-high-threshold-uv: The battery voltage threshold above which the

		BCL driver clears the previously applied mitigation, disables

		the battery current monitoring, and starts monitoring for low

		battery voltage.

	* qcom,vph-low-threshold-uv: The battery voltage threshold below which the

		BCL driver starts monitoring the battery current thresholds and

		mitigates the CPU on the event of high load.

	* qcom,thermal-handle = <&phandle_to_vdd_apps>: phandle to the "qcom,msm_thermal"

		vdd restriction property, "qcom,vdd-apps-rstr". This phandle is

		used by BCL driver to get the minimum frequency request that the

		thermal driver places during vdd restriction. This frequency

		value will be the lowest max frequency value the BCL driver can

		request.

	* qcom,soc-low-threshold: The battery SOC percentage threshold below which

		mitigation needs to be applied.

Example:

	qcom,bcl {

		compatible = "qcom,bcl";

		qcom,ibat-vadc = <&pma8084_vadc>;

		qcom,ibat-threshold-adc_tm = <&pma8084_adc_tm>;

		qcom,bcl-no-bms;

		qcom,ibat-monitor {

			qcom,high-threshold-uamp = <1500>;

			qcom,low-threshold-uamp = <500>;

			qcom,mitigation-freq-khz = <1958400>;

			qcom,ibat-channel = <0x15>;

			qcom,adc-interval-usec = <3900>;

			qcom,uv-to-ua-numerator = <2>;

			qcom,uv-to-ua-denominator = <1>;

			qcom,vph-channel = <0x07>;

			qcom,vph-high-threshold-uv = <3700000>;

			qcom,vph-low-threshold-uv = <3500000>;

			qcom,thermal-handle = <&msm_thermal_freq>;

		};

	};

For Using BCL peripheral interface:

	qcom,bcl {

		compatible = "qcom,bcl";

		qcom,bcl-framework-interface;

		qcom,bcl-freq-mit-list = <&CPU4 &CPU5 &CPU6 &CPU7>;

		qcom,bcl-hotplug-list = <&CPU5 &CPU6 &CPU7>;

		qcom,bcl-soc-hotplug-list = <&CPU4 &CPU5 &CPU6 &CPU7>;

		qcom,ibat-monitor {

			qcom,high-threshold-uamp = <1500>;

			qcom,low-threshold-uamp = <500>;

			qcom,mitigation-freq-khz = <1958400>;

			qcom,vph-high-threshold-uv = <3700000>;

			qcom,vph-low-threshold-uv = <3500000>;

			qcom,thermal-handle = <&msm_thermal_freq>;

		};

	};

===============================================================================

BCL PMIC Peripheral driver:

===============================================================================

In newer targets from MSM8994, the PMIC has BCL monitoring capabilities

in the hardware. The PMIC exposes this BCL monitoring peripheral as a PMIC

peripheral. The BCL peripheral driver interacts with the PMIC peripheral using

the SPMI driver interfaces. The details and the configuration for the BCL

peripheral can be inputted using the device tree.

The units of the Vbat and Ibat values returned and read depends on the scaling

factor that is given as input for BCL peripheral driver through device tree. The

scaling factors should be configured to handle Vbat in micro-volt and Ibat in

micro-amps.

Required Parameters:

- compatible: must be either

	1. 'qcom,msm-bcl' for bcl peripheral without LMH DCVSh

  	   interface

	2. 'qcom,msm-bcl-lmh' for bcl peripheral with LMH DCVSh interface.

- reg: <a b> where 'a' is the starting register address of the PMIC

	peripheral and 'b' is the size of the peripheral address space.

	If the BCL inhibit current derating feature is enabled, this must also

	contain the PON spare registers as well. Example: <a b c d> where

	c is the first PON spare register that will be written and d is the

	size of the registers space needed to be written. Certain version

	of PMIC, can send interrupt to LMH hardware driver directly. In that

	case the shadow peripheral address space should be mentioned along

	with the bcl peripherals address.

- reg-names: a list of names of the registers corresponding to the reg

	property. The fuel gauge peripheral should be "fg_user_adc", the

	PON spare should be "pon_spare", and the bcl-lmh shadow peripheral

	should be "fg_lmh".

-interrupts: <a b c> Where 'a' is the SLAVE ID of the PMIC, 'b' is

		the peripheral ID and 'c' is the interrupt number in PMIC.

- interrupt-names: user defined names for the interrupts. These

		interrupt names will be used by the drivers to identify the

		interrupts, instead of specifying the ID's.

- qcom,ibat-polling-delay-ms: Software polling interval for monitoring ibat

		low threshold.

- qcom,vbat-polling-delay-ms: Software polling interval for monitoring vbat

		high threshold.

Optional parameters for peripheral with LMH DCVSh interface:

- qcom,vbat-scaling-factor: The scaling factor to be used for converting

		the raw vbat ADC value to milli-volt.

- qcom,vbat-gain-numerator: The numerator of the vbat gain correction factor.

- qcom,vbat-gain-denominator: The denominator of the vbat gain correction

		factor.

- qcom,ibat-scaling-factor: The scaling factor to be used for converting

		the raw ibat ADC value to micro-amps.

- qcom, ibat-gain-numerator: The numerator of the ibat gain correction factor.

- qcom, ibat-gain-denominator: The denominator of the ibat gain correction

		factor.

- qcom, ibat-offset-numerator: The numerator of the ibat offset correction

		factor.

- qcom, ibat-offset-denominator: The denominator of the ibat offset

		correction factor.

Optional Parameters:

- qcom,inhibit-derating-ua: The amount that the bcl current high trip threshold

		should be lowered by when the bcl peripheral is operating in a

		dead time.

                bcl@4200 {

                        compatible = "qcom,msm-bcl";

                        reg = <0x4200 0xFF 0x88e 0x2>;

			reg-names = "fg_user_adc", "pon_spare";

                        interrupts = <0x2 0x42 0x0>,

                                        <0x2 0x42 0x1>;

                        interrupt-names = "bcl-high-ibat-int",

                                        "bcl-low-vbat-int";

                        qcom,vbat-scaling-factor = <39>;

                        qcom,vbat-gain-numerator = <1>;

                        qcom,vbat-gain-denominator = <32>;

                        qcom,vbat-polling-delay-ms = <50>;

                        qcom,ibat-scaling-factor = <39>;

                        qcom,ibat-gain-numerator = <1>;

                        qcom,ibat-gain-denominator = <32>;

                        qcom,ibat-offset-numerator = <12>;

                        qcom,ibat-offset-denominator = <10>;

                        qcom,ibat-polling-delay-ms = <50>;

                };

  - iommus: SMMUs and corresponding Stream IDs needed by WLAN

  - qcom,wlan-smmu-iova-address: I/O virtual address range as <start length>

    format to be used for allocations associated between WLAN and SMMU

  - <supply-name>-supply: phandle to the regulator device tree node

                          Required "supply-name" is "vdd-io".

  - qcom,<supply>-voltage-level - specifies voltage levels for supply. Should be

                                  specified in pairs (min, max), units uV.

Optional properties:

  - qcom,skip-qmi: Boolean property to decide whether to use QMI or not

		   <0 141 0 /* CE11 */ >;

        qcom,wlan-msa-memory = <0x200000>;

        qcom,skip-qmi;

	vdd-io-supply = <&pmcobalt_l5>;

	qcom,vdd-io-voltage-level = <800000 800000>;

    };

Qualcomm Technologies Inc. PNP v2 Flash LED

QPNP (Qualcomm Technologies Inc. Plug N Play) Flash LED (Light

Emitting Diode) driver v2 is used to provide illumination to

camera sensor when background light is dim to capture good

picture. It can also be used for flashlight/torch application.

It is part of PMIC on Qualcomm Technologies Inc. reference platforms.

Required properties:

- compatible		: Should be "qcom,qpnp-flash-led-v2"

- reg			: Base address and size for flash LED modules

Optional properties:

- qcom,hdrm-auto-mode	: Boolean type to select headroom auto mode enabled or not

- qcom,isc-delay	: Integer type to specify short circuit delay. Valid values are 32, 64,

			  128, 192. Unit is us.

Required properties inside child node. Child node contains settings for each individual LED.

Each LED channel needs a flash node and torch node for itself, and an individual switch node to

serve as an overall switch.

- label			: Type of led that will be used, either "flash", "torch", or "switch.

- qcom,led-name		: Name of the LED.

- qcom,default-led-trigger	: Trigger for the camera flash and torch. Accepted values are

			  "flash0_trigger", "flash1_trigger", "flash2_trigger, "torch0_trigger",

			  "torch1_trigger", "torch2_trigger", and "switch_trigger".

- qcom,id		: ID for each physical LED equipped. In order to handle situation when

			  only 1 or 2 LEDs are installed, flash and torch nodes on LED channel 0

			  should be specified with ID 0; nodes on channel 1 be ID 1, etc. This is

			  not required for switch node.

- qcom,max-current	: Maximum current allowed on this LED. Valid values should be

			  integer from 0 to 1500 inclusive. Flash 2 should have maximum current of

			  750 per hardware requirement. Unit is mA. This is not required for switch

			  node.

- qcom,duration-ms	: Required property for flash nodes but not needed for torch. Integer

			  type specifying flash duration. Values are from 10ms to 1280ms with

			  10ms resolution. This is not required for switch node.

Optional properties inside child node:

- qcom,ires-ua		: Integer type to specify current resolution. Accepted values should be

			  12500, 10000, 7500, and 5000. Unit is uA.

- qcom,hdrm-voltage-mv	: Integer type specifying headroom voltage. Values are from 125mV to 500mV

			  with 25mV resolution. Default setting is 325mV

- qcom,hdrm-vol-hi-lo-win-mv	: Integer type to specify headroom voltage swing range. Values are

				  from 0mV to 375mV with 25mV resolution. Default setting is 100mV.

- pinctrl-names		: This should be defined if a target uses pinctrl framework and there is GPIO

			requirement for flash LEDs. See "pinctrl" in

			Documentation/devicetree/bindings/pinctrl/msm-pinctrl.txt. It should specify

			the names of the configs that pinctrl can install in driver.

                        Following are the pinctrl configs that can be installed:

                        "led_enable" : Enablement configuration of pins. This should specify active

                        config defined in each pin or pin group.

                        "led_disable" : Disablement configuration of pins. This should specify inactive

                        config defined in each pin or pin groups.

Example:

	qcom,leds@d300 {

		compatible = "qcom,qpnp-flash-led-v2";

		status = "okay";

		reg = <0xd300 0x100>;

		label = "flash";

		qcom,hdrm-auto-mode;

		qcom,isc-delay = <192>;

		pmi8998_flash0: qcom,flash_0 {

			label = "flash";

			qcom,led-name = "led:flash_0";

			qcom,max-current = <1500>;

			qcom,default-led-trigger =

						"flash0_trigger";

			qcom,id = <0>;

			qcom,duration-ms = <1280>;

			qcom,ires-ua = <12500>;

			qcom,hdrm-voltage-mv = <325>;

			qcom,hdrm-vol-hi-lo-win-mv = <100>;

		};

		pmi8998_flash1: qcom,flash_1 {

			label = "flash";

			qcom,led-name = "led:flash_1";

			qcom,max-current = <1500>;

			qcom,default-led-trigger =

						"flash1_trigger";

			qcom,id = <1>;

			qcom,duration-ms = <1280>;

			qcom,ires-ua = <12500>;

			qcom,hdrm-voltage-mv = <325>;

			qcom,hdrm-vol-hi-lo-win-mv = <100>;

		};

		pmi8998_flash2: qcom,flash_2 {

			label = "flash";

			qcom,led-name = "led:flash_2";

			qcom,max-current = <750>;

			qcom,default-led-trigger =

						"flash2_trigger";

			qcom,id = <2>;

			qcom,duration-ms = <1280>;

			qcom,ires-ua = <12500>;

			qcom,hdrm-voltage-mv = <325>;

			qcom,hdrm-vol-hi-lo-win-mv = <100>;

			pinctrl-names = "led_enable","led_disable";

			pinctrl-0 = <&led_enable>;

			pinctrl-1 = <&led_disable>;

		};

		pmi8998_torch0: qcom,torch_0 {

			label = "torch";

			qcom,led-name = "led:torch_0";

			qcom,max-current = <200>;

			qcom,default-led-trigger =

						"torch0_trigger";

			qcom,id = <0>;

			qcom,ires-ua = <12500>;

			qcom,hdrm-voltage-mv = <325>;

			qcom,hdrm-vol-hi-lo-win-mv = <100>;

		};

		pmi8998_torch1: qcom,torch_1 {

			label = "torch";

			qcom,led-name = "led:torch_1";

			qcom,max-current = <200>;

			qcom,default-led-trigger =

						"torch1_trigger";

			qcom,id = <1>;

			qcom,ires-ua = <12500>;

			qcom,hdrm-voltage-mv = <325>;

			qcom,hdrm-vol-hi-lo-win-mv = <100>;

		};

		pmi8998_torch2: qcom,torch_2 {

			label = "torch";

			qcom,led-name = "led:torch_2";

			qcom,max-current = <200>;

			qcom,default-led-trigger =

						"torch2_trigger";

			qcom,id = <2>;

			qcom,ires-ua = <12500>;

			qcom,hdrm-voltage-mv = <325>;

			qcom,hdrm-vol-hi-lo-win-mv = <100>;

			pinctrl-names = "led_enable","led_disable";

			pinctrl-0 = <&led_enable>;

			pinctrl-1 = <&led_disable>;

		};

		pmi8998_switch: qcom,led_switch {

			label = "switch";

			qcom,led-name = "led:switch";

			qcom,default-led-trigger =

						"switch_trigger";

		};

	};

			qcom,msm-dai-q6-dev-id = <16394>;

		};

		sb_6_rx: qcom,msm-dai-q6-sb-6-rx {

			compatible = "qcom,msm-dai-q6-dev";

			qcom,msm-dai-q6-dev-id = <16396>;

		};

		sb_7_rx: qcom,msm-dai-q6-sb-7-rx {

			compatible = "qcom,msm-dai-q6-dev";

			qcom,msm-dai-q6-dev-id = <16398>;

			compatible = "qcom,msm-dai-q6-dev";

			qcom,msm-dai-q6-dev-id = <32770>;

		};

		usb_audio_rx: qcom,msm-dai-q6-usb-audio-rx {

			compatible = "qcom,msm-dai-q6-dev";

			qcom,msm-dai-q6-dev-id = <28672>;

		};

		usb_audio_tx: qcom,msm-dai-q6-usb-audio-tx {

			compatible = "qcom,msm-dai-q6-dev";

			qcom,msm-dai-q6-dev-id = <28673>;

		};

	};

	hostless: qcom,msm-pcm-hostless {

					  "msg-tx-discarded",

					  "msg-rx-discarded";

		};

		bcl@4200 {

			compatible = "qcom,msm-bcl-lmh";

			reg = <0x4200 0xff>,

				<0x4300 0xff>;

			reg-names = "fg_user_adc",

					"fg_lmh";

			interrupts = <0x2 0x42 0x0 IRQ_TYPE_NONE>,

					<0x2 0x42 0x2 IRQ_TYPE_NONE>;

			interrupt-names = "bcl-high-ibat-int",

					"bcl-low-vbat-int";

			qcom,vbat-polling-delay-ms = <100>;

			qcom,ibat-polling-delay-ms = <100>;

		};

	};

	qcom,pmicobalt@3 {