Merge tag 'pci-v3.16-changes' of... (42555320) · Commits · e / devices / android_kernel_oneplus_sm7250

Documentation/ABI/testing/sysfs-bus-pci

+21 −0

Original line number	Diff line number	Diff line
		@@ -250,3 +250,24 @@ Description:
		valid. For example, writing a 2 to this file when sriov_numvfs
		is not 0 and not 2 already will return an error. Writing a 10
		when the value of sriov_totalvfs is 8 will return an error.

		What: /sys/bus/pci/devices/.../driver_override
		Date: April 2014
		Contact: Alex Williamson <alex.williamson@redhat.com>
		Description:
		This file allows the driver for a device to be specified which
		will override standard static and dynamic ID matching. When
		specified, only a driver with a name matching the value written
		to driver_override will have an opportunity to bind to the
		device. The override is specified by writing a string to the
		driver_override file (echo pci-stub > driver_override) and
		may be cleared with an empty string (echo > driver_override).
		This returns the device to standard matching rules binding.
		Writing to driver_override does not automatically unbind the
		device from its current driver or make any attempt to
		automatically load the specified driver. If no driver with a
		matching name is currently loaded in the kernel, the device
		will not bind to any driver. This also allows devices to
		opt-out of driver binding using a driver_override name such as
		"none". Only a single driver may be specified in the override,
		there is no support for parsing delimiters.

Documentation/DMA-API-HOWTO.txt

+132 −78

File changed.

Preview size limit exceeded, changes collapsed.

Documentation/DMA-API.txt

+77 −73

File changed.

Preview size limit exceeded, changes collapsed.

Documentation/DMA-ISA-LPC.txt

+2 −2

Original line number	Diff line number	Diff line
		@@ -16,7 +16,7 @@ To do ISA style DMA you need to include two headers:
		#include <asm/dma.h>

		The first is the generic DMA API used to convert virtual addresses to
		physical addresses (see Documentation/DMA-API.txt for details).
		bus addresses (see Documentation/DMA-API.txt for details).

		The second contains the routines specific to ISA DMA transfers. Since
		this is not present on all platforms make sure you construct your
		@@ -50,7 +50,7 @@ early as possible and not release it until the driver is unloaded.)
		Part III - Address translation
		------------------------------

		To translate the virtual address to a physical use the normal DMA
		To translate the virtual address to a bus address, use the normal DMA
		API. Do _not_ use isa_virt_to_phys() even though it does the same
		thing. The reason for this is that the function isa_virt_to_phys()
		will require a Kconfig dependency to ISA, not just ISA_DMA_API which

Documentation/devicetree/bindings/pci/host-generic-pci.txt

0 → 100644

+100 −0

Original line number	Diff line number	Diff line
		* Generic PCI host controller

		Firmware-initialised PCI host controllers and PCI emulations, such as the
		virtio-pci implementations found in kvmtool and other para-virtualised
		systems, do not require driver support for complexities such as regulator
		and clock management. In fact, the controller may not even require the
		configuration of a control interface by the operating system, instead
		presenting a set of fixed windows describing a subset of IO, Memory and
		Configuration Spaces.

		Such a controller can be described purely in terms of the standardized device
		tree bindings communicated in pci.txt:


		Properties of the host controller node:

		- compatible : Must be "pci-host-cam-generic" or "pci-host-ecam-generic"
		depending on the layout of configuration space (CAM vs
		ECAM respectively).

		- device_type : Must be "pci".

		- ranges : As described in IEEE Std 1275-1994, but must provide
		at least a definition of non-prefetchable memory. One
		or both of prefetchable Memory and IO Space may also
		be provided.

		- bus-range : Optional property (also described in IEEE Std 1275-1994)
		to indicate the range of bus numbers for this controller.
		If absent, defaults to <0 255> (i.e. all buses).

		- #address-cells : Must be 3.

		- #size-cells : Must be 2.

		- reg : The Configuration Space base address and size, as accessed
		from the parent bus.


		Properties of the /chosen node:

		- linux,pci-probe-only
		: Optional property which takes a single-cell argument.
		If '0', then Linux will assign devices in its usual manner,
		otherwise it will not try to assign devices and instead use
		them as they are configured already.

		Configuration Space is assumed to be memory-mapped (as opposed to being
		accessed via an ioport) and laid out with a direct correspondence to the
		geography of a PCI bus address by concatenating the various components to
		form an offset.

		For CAM, this 24-bit offset is:

		cfg_offset(bus, device, function, register) =
		bus << 16 \| device << 11 \| function << 8 \| register

		Whilst ECAM extends this by 4 bits to accomodate 4k of function space:

		cfg_offset(bus, device, function, register) =
		bus << 20 \| device << 15 \| function << 12 \| register

		Interrupt mapping is exactly as described in `Open Firmware Recommended
		Practice: Interrupt Mapping' and requires the following properties:

		- #interrupt-cells : Must be 1

		- interrupt-map : <see aforementioned specification>

		- interrupt-map-mask : <see aforementioned specification>


		Example:

		pci {
		compatible = "pci-host-cam-generic"
		device_type = "pci";
		#address-cells = <3>;
		#size-cells = <2>;
		bus-range = <0x0 0x1>;

		// CPU_PHYSICAL(2) SIZE(2)
		reg = <0x0 0x40000000 0x0 0x1000000>;

		// BUS_ADDRESS(3) CPU_PHYSICAL(2) SIZE(2)
		ranges = <0x01000000 0x0 0x01000000 0x0 0x01000000 0x0 0x00010000>,
		<0x02000000 0x0 0x41000000 0x0 0x41000000 0x0 0x3f000000>;


		#interrupt-cells = <0x1>;

		// PCI_DEVICE(3) INT#(1) CONTROLLER(PHANDLE) CONTROLLER_DATA(3)
		interrupt-map = < 0x0 0x0 0x0 0x1 &gic 0x0 0x4 0x1
		0x800 0x0 0x0 0x1 &gic 0x0 0x5 0x1
		0x1000 0x0 0x0 0x1 &gic 0x0 0x6 0x1
		0x1800 0x0 0x0 0x1 &gic 0x0 0x7 0x1>;

		// PCI_DEVICE(3) INT#(1)
		interrupt-map-mask = <0xf800 0x0 0x0 0x7>;
		}