Merge branch 'for-next' into for-linus

	xirc2ps_cs=	[NET,PCMCIA]

			Format:

			<irq>,<irq_mask>,<io>,<full_duplex>,<do_sound>,<lockup_hack>[,<irq2>[,<irq3>[,<irq4>]]]

	xhci-hcd.quirks		[USB,KNL]

			A hex value specifying bitmask with supplemental xhci

			host controller quirks. Meaning of each bit can be

			consulted in header drivers/usb/host/xhci.h.

``intel_pstate`` exposes several global attributes (files) in ``sysfs`` to

control its functionality at the system level.  They are located in the

``/sys/devices/system/cpu/cpufreq/intel_pstate/`` directory and affect all

CPUs.

``/sys/devices/system/cpu/intel_pstate/`` directory and affect all CPUs.

Some of them are not present if the ``intel_pstate=per_cpu_perf_limits``

argument is passed to the kernel in the command line.

	but it affects the maximum possible value of per-policy P-state	limits

	(see `Interpretation of Policy Attributes`_ below for details).

``hwp_dynamic_boost``

	This attribute is only present if ``intel_pstate`` works in the

	`active mode with the HWP feature enabled <Active Mode With HWP_>`_ in

	the processor.  If set (equal to 1), it causes the minimum P-state limit

	to be increased dynamically for a short time whenever a task previously

	waiting on I/O is selected to run on a given logical CPU (the purpose

	of this mechanism is to improve performance).

	This setting has no effect on logical CPUs whose minimum P-state limit

	is directly set to the highest non-turbo P-state or above it.

.. _status_attr:

``status``

	That only is supported in some configurations, though (for example, if

	the `HWP feature is enabled in the processor <Active Mode With HWP_>`_,

	the operation mode of the driver cannot be changed), and if it is not

	supported in the current configuration, writes to this attribute with

	supported in the current configuration, writes to this attribute will

	fail with an appropriate error.

Interpretation of Policy Attributes

MTRR Handling

-------------

.. kernel-doc:: arch/x86/kernel/cpu/mtrr/main.c

.. kernel-doc:: arch/x86/kernel/cpu/mtrr/mtrr.c

   :export:

Security Framework

Spreadtrum SC27xx PMIC Vibrator

Required properties:

- compatible: should be "sprd,sc2731-vibrator".

- reg: address of vibrator control register.

Example :

	sc2731_pmic: pmic@0 {

		compatible = "sprd,sc2731";

		reg = <0>;

		spi-max-frequency = <26000000>;

		interrupts = <GIC_SPI 31 IRQ_TYPE_LEVEL_HIGH>;

		interrupt-controller;

		#interrupt-cells = <2>;

		#address-cells = <1>;

		#size-cells = <0>;

		vibrator@eb4 {

			compatible = "sprd,sc2731-vibrator";

			reg = <0xeb4>;

		};

	};

Generic AC97 Device Properties

This documents describes the devicetree bindings for an ac97 controller child

node describing ac97 codecs.

Required properties:

-compatible : Must be "ac97,vendor_id1,vendor_id2

	      The ids shall be the 4 characters hexadecimal encoding, such as

	      given by "%04x" formatting of printf

-reg	    : Must be the ac97 codec number, between 0 and 3

Example:

ac97: sound@40500000 {

	compatible = "marvell,pxa270-ac97";

	reg = < 0x40500000 0x1000 >;

	interrupts = <14>;

	reset-gpios = <&gpio 95 GPIO_ACTIVE_HIGH>;

	#sound-dai-cells = <1>;

	pinctrl-names = "default";

	pinctrl-0 = < &pinctrl_ac97_default >;

	clocks = <&clks CLK_AC97>, <&clks CLK_AC97CONF>;

	clock-names = "AC97CLK", "AC97CONFCLK";

	#address-cells = <1>;

	#size-cells = <0>;

	audio-codec@0 {

		reg = <0>;

		compatible = "ac97,574d,4c13";

		clocks = <&fixed_wm9713_clock>;

		clock-names = "ac97_clk";

	}

};