Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net

			use by PCI

			Format: <irq>,<irq>...

	acpi_mask_gpe=  [HW,ACPI]

			Due to the existence of _Lxx/_Exx, some GPEs triggered

			by unsupported hardware/firmware features can result in

                        GPE floodings that cannot be automatically disabled by

                        the GPE dispatcher.

			This facility can be used to prevent such uncontrolled

			GPE floodings.

			Format: <int>

			Support masking of GPEs numbered from 0x00 to 0x7f.

	acpi_no_auto_serialize	[HW,ACPI]

			Disable auto-serialization of AML methods

			AML control methods that contain the opcodes to create

			it if 0 is given (See Documentation/cgroup-v1/memory.txt)

	swiotlb=	[ARM,IA-64,PPC,MIPS,X86]

			Format: { <int> | force }

			Format: { <int> | force | noforce }

			<int> -- Number of I/O TLB slabs

			force -- force using of bounce buffers even if they

			         wouldn't be automatically used by the kernel

			noforce -- Never use bounce buffers (for debugging)

	switches=	[HW,M68k]

Required properties:

- compatible: should be "ti,tps65217-pwrbutton" or "ti,tps65218-pwrbutton"

Required properties for TPS65218:

Required properties:

- interrupts: should be one of the following

   - <2>: For controllers compatible with tps65217

   - <3 IRQ_TYPE_EDGE_BOTH>: For controllers compatible with tps65218

Examples:

&tps {

	tps65217-pwrbutton {

		compatible = "ti,tps65217-pwrbutton";

		interrupts = <2>;

	};

};

Required Properties:

-compatible: "ti,tps65217-charger"

-interrupts: TPS65217 interrupt numbers for the AC and USB charger input change.

             Should be <0> for the USB charger and <1> for the AC adapter.

-interrupt-names: Should be "USB" and "AC"

This node is a subnode of the tps65217 PMIC.

Example:

	tps65217-charger {

		compatible = "ti,tps65090-charger";

		compatible = "ti,tps65217-charger";

		interrupts = <0>, <1>;

		interrupt-names = "USB", "AC";

	};

.. kernel-doc:: drivers/base/dma-mapping.c

   :export:

Device Drivers Power Management

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

.. kernel-doc:: drivers/base/power/main.c

   :export:

Device Drivers ACPI Support

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

.. kernel-doc:: drivers/acpi/scan.c

   :export:

.. kernel-doc:: drivers/acpi/scan.c

   :internal:

Device drivers PnP support

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

Physical Device Driver Interface

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

The physical device driver interface provides the parent_ops[3] structure to

define the APIs to manage work in the mediated core driver that is related to

the physical device.

The physical device driver interface provides the mdev_parent_ops[3] structure

to define the APIs to manage work in the mediated core driver that is related

to the physical device.

The structures in the parent_ops structure are as follows:

The structures in the mdev_parent_ops structure are as follows:

* dev_attr_groups: attributes of the parent device

* mdev_attr_groups: attributes of the mediated device

* supported_config: attributes to define supported configurations

The functions in the parent_ops structure are as follows:

The functions in the mdev_parent_ops structure are as follows:

* create: allocate basic resources in a driver for a mediated device

* remove: free resources in a driver when a mediated device is destroyed

The callbacks in the parent_ops structure are as follows:

The callbacks in the mdev_parent_ops structure are as follows:

* open: open callback of mediated device

* close: close callback of mediated device

* write: write emulation callback

* mmap: mmap emulation callback

A driver should use the parent_ops structure in the function call to register

itself with the mdev core driver:

A driver should use the mdev_parent_ops structure in the function call to

register itself with the mdev core driver:

extern int  mdev_register_device(struct device *dev,

                                 const struct parent_ops *ops);

                                 const struct mdev_parent_ops *ops);

However, the parent_ops structure is not required in the function call that a

driver should use to unregister itself with the mdev core driver:

However, the mdev_parent_ops structure is not required in the function call

that a driver should use to unregister itself with the mdev core driver:

extern void mdev_unregister_device(struct device *dev);

	sprintf(buf, "%s-%s", dev_driver_string(parent->dev), group->name);

  (or using mdev_parent_dev(mdev) to arrive at the parent device outside

   of the core mdev code)

* device_api

  This attribute should show which device API is being created, for example,

[1] See Documentation/vfio.txt for more information on VFIO.

[2] struct mdev_driver in include/linux/mdev.h

[3] struct parent_ops in include/linux/mdev.h

[3] struct mdev_parent_ops in include/linux/mdev.h

[4] struct vfio_iommu_driver_ops in include/linux/vfio.h