Merge branch 'next' into for-linus

Juha Yrjola <juha.yrjola@solidboot.com>

Kay Sievers <kay.sievers@vrfy.org>

Kenneth W Chen <kenneth.w.chen@intel.com>

Konstantin Khlebnikov <koct9i@gmail.com> <k.khlebnikov@samsung.com>

Koushik <raghavendra.koushik@neterion.com>

Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>

Leonid I Ananiev <leonid.i.ananiev@intel.com>

		The /sys/class/mei/meiN directory is created for

		each probed mei device

What:		/sys/class/mei/meiN/fw_status

Date:		Nov 2014

KernelVersion:	3.19

Contact:	Tomas Winkler <tomas.winkler@intel.com>

Description:	Display fw status registers content

		The ME FW writes its status information into fw status

		registers for BIOS and OS to monitor fw health.

		The register contains running state, power management

		state, error codes, and others. The way the registers

		are decoded depends on PCH or SoC generation.

		Also number of registers varies between 1 and 6

		depending on generation.

What:		/sys/class/leds/dell::kbd_backlight/als_setting

Date:		December 2014

KernelVersion:	3.19

Contact:	Gabriele Mazzotta <gabriele.mzt@gmail.com>,

		Pali Rohár <pali.rohar@gmail.com>

Description:

		This file allows to control the automatic keyboard

		illumination mode on some systems that have an ambient

		light sensor. Write 1 to this file to enable the auto

		mode, 0 to disable it.

What:		/sys/class/leds/dell::kbd_backlight/start_triggers

Date:		December 2014

KernelVersion:	3.19

Contact:	Gabriele Mazzotta <gabriele.mzt@gmail.com>,

		Pali Rohár <pali.rohar@gmail.com>

Description:

		This file allows to control the input triggers that

		turn on the keyboard backlight illumination that is

		disabled because of inactivity.

		Read the file to see the triggers available. The ones

		enabled are preceded by '+', those disabled by '-'.

		To enable a trigger, write its name preceded by '+' to

		this file. To disable a trigger, write its name preceded

		by '-' instead.

		For example, to enable the keyboard as trigger run:

		    echo +keyboard > /sys/class/leds/dell::kbd_backlight/start_triggers

		To disable it:

		    echo -keyboard > /sys/class/leds/dell::kbd_backlight/start_triggers

		Note that not all the available triggers can be configured.

What:		/sys/class/leds/dell::kbd_backlight/stop_timeout

Date:		December 2014

KernelVersion:	3.19

Contact:	Gabriele Mazzotta <gabriele.mzt@gmail.com>,

		Pali Rohár <pali.rohar@gmail.com>

Description:

		This file allows to specify the interval after which the

		keyboard illumination is disabled because of inactivity.

		The timeouts are expressed in seconds, minutes, hours and

		days, for which the symbols are 's', 'm', 'h' and 'd'

		respectively.

		To configure the timeout, write to this file a value along

		with any the above units. If no unit is specified, the value

		is assumed to be expressed in seconds.

		For example, to set the timeout to 10 minutes run:

		    echo 10m > /sys/class/leds/dell::kbd_backlight/stop_timeout

		Note that when this file is read, the returned value might be

		expressed in a different unit than the one used when the timeout

		was set.

		Also note that only some timeouts are supported and that

		some systems might fall back to a specific timeout in case

		an invalid timeout is written to this file.

    range of 0x200 bytes.

- syscon: the root node of the Integrator platforms must have a

  system controller node pointong to the control registers,

  system controller node pointing to the control registers,

  with the compatible string

  "arm,integrator-ap-syscon"

  "arm,integrator-cp-syscon"

* QEMU Firmware Configuration bindings for ARM

QEMU's arm-softmmu and aarch64-softmmu emulation / virtualization targets

provide the following Firmware Configuration interface on the "virt" machine

type:

- A write-only, 16-bit wide selector (or control) register,

- a read-write, 64-bit wide data register.

QEMU exposes the control and data register to ARM guests as memory mapped

registers; their location is communicated to the guest's UEFI firmware in the

DTB that QEMU places at the bottom of the guest's DRAM.

The guest writes a selector value (a key) to the selector register, and then

can read the corresponding data (produced by QEMU) via the data register. If

the selected entry is writable, the guest can rewrite it through the data

register.

The selector register takes keys in big endian byte order.

The data register allows accesses with 8, 16, 32 and 64-bit width (only at

offset 0 of the register). Accesses larger than a byte are interpreted as

arrays, bundled together only for better performance. The bytes constituting

such a word, in increasing address order, correspond to the bytes that would

have been transferred by byte-wide accesses in chronological order.

The interface allows guest firmware to download various parameters and blobs

that affect how the firmware works and what tables it installs for the guest

OS. For example, boot order of devices, ACPI tables, SMBIOS tables, kernel and

initrd images for direct kernel booting, virtual machine UUID, SMP information,

virtual NUMA topology, and so on.

The authoritative registry of the valid selector values and their meanings is

the QEMU source code; the structure of the data blobs corresponding to the

individual key values is also defined in the QEMU source code.

The presence of the registers can be verified by selecting the "signature" blob

with key 0x0000, and reading four bytes from the data register. The returned

signature is "QEMU".

The outermost protocol (involving the write / read sequences of the control and

data registers) is expected to be versioned, and/or described by feature bits.

The interface revision / feature bitmap can be retrieved with key 0x0001. The

blob to be read from the data register has size 4, and it is to be interpreted

as a uint32_t value in little endian byte order. The current value

(corresponding to the above outer protocol) is zero.

The guest kernel is not expected to use these registers (although it is

certainly allowed to); the device tree bindings are documented here because

this is where device tree bindings reside in general.

Required properties:

- compatible: "qemu,fw-cfg-mmio".

- reg: the MMIO region used by the device.

  * Bytes 0x0 to 0x7 cover the data register.

  * Bytes 0x8 to 0x9 cover the selector register.

  * Further registers may be appended to the region in case of future interface

    revisions / feature bits.

Example:

/ {

	#size-cells = <0x2>;

	#address-cells = <0x2>;

	fw-cfg@9020000 {

		compatible = "qemu,fw-cfg-mmio";

		reg = <0x0 0x9020000 0x0 0xa>;

	};

};