-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'drm-next' of git://people.freedesktop.org/~airlied/linux
Pull drm updates from Dave Airlie: "Been a bit busy, first week of kids school, and waiting on other trees to go in before I could send this, so its a bit later than I'd normally like. Highlights: - core: timestamp fixes, lots of misc cleanups - new drivers: bochs virtual vga - vmwgfx: major overhaul for their nextgen virt gpu. - i915: runtime D3 on HSW, watermark fixes, power well work, fbc fixes, bdw is no longer prelim. - nouveau: gk110/208 acceleration, more pm groundwork, old overlay support - radeon: dpm rework and clockgating for CIK, pci config reset, big endian fixes - tegra: panel support and DSI support, build as module, prime. - armada, omap, gma500, rcar, exynos, mgag200, cirrus, ast: fixes - msm: hdmi support for mdp5" * 'drm-next' of git://people.freedesktop.org/~airlied/linux: (595 commits) drm/nouveau: resume display if any later suspend bits fail drm/nouveau: fix lock unbalance in nouveau_crtc_page_flip drm/nouveau: implement hooks for needed for drm vblank timestamping support drm/nouveau/disp: add a method to fetch info needed by drm vblank timestamping drm/nv50: fill in crtc mode struct members from crtc_mode_fixup drm/radeon/dce8: workaround for atom BlankCrtc table drm/radeon/DCE4+: clear bios scratch dpms bit (v2) drm/radeon: set si_notify_smc_display_change properly drm/radeon: fix DAC interrupt handling on DCE5+ drm/radeon: clean up active vram sizing drm/radeon: skip async dma init on r6xx drm/radeon/runpm: don't runtime suspend non-PX cards drm/radeon: add ring to fence trace functions drm/radeon: add missing trace point drm/radeon: fix VMID use tracking drm: ast,cirrus,mgag200: use drm_can_sleep drm/gma500: Lock struct_mutex around cursor updates drm/i915: Fix the offset issue for the stolen GEM objects DRM: armada: fix missing DRM_KMS_FB_HELPER select drm/i915: Decouple GPU error reporting from ring initialisation ...
- Loading branch information
Showing
512 changed files
with
35,539 additions
and
11,886 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
98 changes: 98 additions & 0 deletions
98
Documentation/devicetree/bindings/mipi/dsi/mipi-dsi-bus.txt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,98 @@ | ||
MIPI DSI (Display Serial Interface) busses | ||
========================================== | ||
|
||
The MIPI Display Serial Interface specifies a serial bus and a protocol for | ||
communication between a host and up to four peripherals. This document will | ||
define the syntax used to represent a DSI bus in a device tree. | ||
|
||
This document describes DSI bus-specific properties only or defines existing | ||
standard properties in the context of the DSI bus. | ||
|
||
Each DSI host provides a DSI bus. The DSI host controller's node contains a | ||
set of properties that characterize the bus. Child nodes describe individual | ||
peripherals on that bus. | ||
|
||
The following assumes that only a single peripheral is connected to a DSI | ||
host. Experience shows that this is true for the large majority of setups. | ||
|
||
DSI host | ||
-------- | ||
|
||
In addition to the standard properties and those defined by the parent bus of | ||
a DSI host, the following properties apply to a node representing a DSI host. | ||
|
||
Required properties: | ||
- #address-cells: The number of cells required to represent an address on the | ||
bus. DSI peripherals are addressed using a 2-bit virtual channel number, so | ||
a maximum of 4 devices can be addressed on a single bus. Hence the value of | ||
this property should be 1. | ||
- #size-cells: Should be 0. There are cases where it makes sense to use a | ||
different value here. See below. | ||
|
||
DSI peripheral | ||
-------------- | ||
|
||
Peripherals are represented as child nodes of the DSI host's node. Properties | ||
described here apply to all DSI peripherals, but individual bindings may want | ||
to define additional, device-specific properties. | ||
|
||
Required properties: | ||
- reg: The virtual channel number of a DSI peripheral. Must be in the range | ||
from 0 to 3. | ||
|
||
Some DSI peripherals respond to more than a single virtual channel. In that | ||
case two alternative representations can be chosen: | ||
- The reg property can take multiple entries, one for each virtual channel | ||
that the peripheral responds to. | ||
- If the virtual channels that a peripheral responds to are consecutive, the | ||
#size-cells can be set to 1. The first cell of each entry in the reg | ||
property is the number of the first virtual channel and the second cell is | ||
the number of consecutive virtual channels. | ||
|
||
Example | ||
------- | ||
|
||
dsi-host { | ||
... | ||
|
||
#address-cells = <1>; | ||
#size-cells = <0>; | ||
|
||
/* peripheral responds to virtual channel 0 */ | ||
peripheral@0 { | ||
compatible = "..."; | ||
reg = <0>; | ||
}; | ||
|
||
... | ||
}; | ||
|
||
dsi-host { | ||
... | ||
|
||
#address-cells = <1>; | ||
#size-cells = <0>; | ||
|
||
/* peripheral responds to virtual channels 0 and 2 */ | ||
peripheral@0 { | ||
compatible = "..."; | ||
reg = <0, 2>; | ||
}; | ||
|
||
... | ||
}; | ||
|
||
dsi-host { | ||
... | ||
|
||
#address-cells = <1>; | ||
#size-cells = <1>; | ||
|
||
/* peripheral responds to virtual channels 1, 2 and 3 */ | ||
peripheral@1 { | ||
compatible = "..."; | ||
reg = <1 3>; | ||
}; | ||
|
||
... | ||
}; |
41 changes: 41 additions & 0 deletions
41
Documentation/devicetree/bindings/mipi/nvidia,tegra114-mipi.txt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
NVIDIA Tegra MIPI pad calibration controller | ||
|
||
Required properties: | ||
- compatible: "nvidia,tegra<chip>-mipi" | ||
- reg: Physical base address and length of the controller's registers. | ||
- clocks: Must contain an entry for each entry in clock-names. | ||
See ../clocks/clock-bindings.txt for details. | ||
- clock-names: Must include the following entries: | ||
- mipi-cal | ||
- #nvidia,mipi-calibrate-cells: Should be 1. The cell is a bitmask of the pads | ||
that need to be calibrated for a given device. | ||
|
||
User nodes need to contain an nvidia,mipi-calibrate property that has a | ||
phandle to refer to the calibration controller node and a bitmask of the pads | ||
that need to be calibrated. | ||
|
||
Example: | ||
|
||
mipi: mipi@700e3000 { | ||
compatible = "nvidia,tegra114-mipi"; | ||
reg = <0x700e3000 0x100>; | ||
clocks = <&tegra_car TEGRA114_CLK_MIPI_CAL>; | ||
clock-names = "mipi-cal"; | ||
#nvidia,mipi-calibrate-cells = <1>; | ||
}; | ||
|
||
... | ||
|
||
host1x@50000000 { | ||
... | ||
|
||
dsi@54300000 { | ||
... | ||
|
||
nvidia,mipi-calibrate = <&mipi 0x060>; | ||
|
||
... | ||
}; | ||
|
||
... | ||
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
AU Optronics Corporation 10.1" WSVGA TFT LCD panel | ||
|
||
Required properties: | ||
- compatible: should be "auo,b101aw03" | ||
|
||
This binding is compatible with the simple-panel binding, which is specified | ||
in simple-panel.txt in this directory. |
7 changes: 7 additions & 0 deletions
7
Documentation/devicetree/bindings/panel/chunghwa,claa101wa01a.txt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
Chunghwa Picture Tubes Ltd. 10.1" WXGA TFT LCD panel | ||
|
||
Required properties: | ||
- compatible: should be "chunghwa,claa101wa01a" | ||
|
||
This binding is compatible with the simple-panel binding, which is specified | ||
in simple-panel.txt in this directory. |
7 changes: 7 additions & 0 deletions
7
Documentation/devicetree/bindings/panel/chunghwa,claa101wb03.txt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
Chunghwa Picture Tubes Ltd. 10.1" WXGA TFT LCD panel | ||
|
||
Required properties: | ||
- compatible: should be "chunghwa,claa101wb03" | ||
|
||
This binding is compatible with the simple-panel binding, which is specified | ||
in simple-panel.txt in this directory. |
7 changes: 7 additions & 0 deletions
7
Documentation/devicetree/bindings/panel/panasonic,vvx10f004b00.txt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
Panasonic Corporation 10.1" WUXGA TFT LCD panel | ||
|
||
Required properties: | ||
- compatible: should be "panasonic,vvx10f004b00" | ||
|
||
This binding is compatible with the simple-panel binding, which is specified | ||
in simple-panel.txt in this directory. |
7 changes: 7 additions & 0 deletions
7
Documentation/devicetree/bindings/panel/samsung,ltn101nt05.txt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
Samsung Electronics 10.1" WSVGA TFT LCD panel | ||
|
||
Required properties: | ||
- compatible: should be "samsung,ltn101nt05" | ||
|
||
This binding is compatible with the simple-panel binding, which is specified | ||
in simple-panel.txt in this directory. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
Simple display panel | ||
|
||
Required properties: | ||
- power-supply: regulator to provide the supply voltage | ||
|
||
Optional properties: | ||
- ddc-i2c-bus: phandle of an I2C controller used for DDC EDID probing | ||
- enable-gpios: GPIO pin to enable or disable the panel | ||
- backlight: phandle of the backlight device attached to the panel | ||
|
||
Example: | ||
|
||
panel: panel { | ||
compatible = "cptt,claa101wb01"; | ||
ddc-i2c-bus = <&panelddc>; | ||
|
||
power-supply = <&vdd_pnl_reg>; | ||
enable-gpios = <&gpio 90 0>; | ||
|
||
backlight = <&backlight>; | ||
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.