-
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/du/adv7511' of git://linuxtv.org/pinchartl/fbdev in…
…to drm-next The branch is based on a merge of drm-next and Simon's tags/renesas-dt-du-for- v3.19 available at git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git, the latter having been pulled in the ARM SoC tree for v3.19. Compared to v1, I've rebased my branch on a later drm-next, added Julia's error return code fix, and documented the "drm: Decouple EDID parsing from I2C adapter" patch properly. v1: Here's a pull request that adds HDMI support to the R-Car DU driver, including a new slave encoder driver for the adv7511. * 'drm/du/adv7511' of git://linuxtv.org/pinchartl/fbdev: drm: Add adv7511 encoder driver video: Add ADV751[13] DT bindings documentation drm: Decouple EDID parsing from I2C adapter drm: rcar-du: Add HDMI encoder and connector support drm: rcar-du: Replace drm_encoder with drm_slave_encoder drm: rcar-du: Replace direct DRM encoder access with cast macro drm: rcar-du: Pass the encoder DT node to rcar_du_encoder_init() drm: rcar-du: Remove platform data support drm: rcar-du: fix error return code ARM: shmobile: koelsch: Enable DU device in DT ARM: shmobile: koelsch-reference: Remove DU platform device ARM: shmobile: lager: Enable DU device in DT ARM: shmobile: lager-reference: Remove DU platform device ARM: shmobile: marzen: Enable DU device in DT ARM: shmobile: dts: Add common file for AA104XD12 panel ARM: shmobile: r8a7791: Add DU node to device tree ARM: shmobile: r8a7790: Add DU node to device tree ARM: shmobile: r8a7779: Add DU node to device tree ARM: shmobile: Remove FSF address from copyright headers
- Loading branch information
Showing
77 changed files
with
2,232 additions
and
524 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,88 @@ | ||
Analog Device ADV7511(W)/13 HDMI Encoders | ||
----------------------------------------- | ||
|
||
The ADV7511, ADV7511W and ADV7513 are HDMI audio and video transmitters | ||
compatible with HDMI 1.4 and DVI 1.0. They support color space conversion, | ||
S/PDIF, CEC and HDCP. | ||
|
||
Required properties: | ||
|
||
- compatible: Should be one of "adi,adv7511", "adi,adv7511w" or "adi,adv7513" | ||
- reg: I2C slave address | ||
|
||
The ADV7511 supports a large number of input data formats that differ by their | ||
color depth, color format, clock mode, bit justification and random | ||
arrangement of components on the data bus. The combination of the following | ||
properties describe the input and map directly to the video input tables of the | ||
ADV7511 datasheet that document all the supported combinations. | ||
|
||
- adi,input-depth: Number of bits per color component at the input (8, 10 or | ||
12). | ||
- adi,input-colorspace: The input color space, one of "rgb", "yuv422" or | ||
"yuv444". | ||
- adi,input-clock: The input clock type, one of "1x" (one clock cycle per | ||
pixel), "2x" (two clock cycles per pixel), "ddr" (one clock cycle per pixel, | ||
data driven on both edges). | ||
|
||
The following input format properties are required except in "rgb 1x" and | ||
"yuv444 1x" modes, in which case they must not be specified. | ||
|
||
- adi,input-style: The input components arrangement variant (1, 2 or 3), as | ||
listed in the input format tables in the datasheet. | ||
- adi,input-justification: The input bit justification ("left", "evenly", | ||
"right"). | ||
|
||
Optional properties: | ||
|
||
- interrupts: Specifier for the ADV7511 interrupt | ||
- pd-gpios: Specifier for the GPIO connected to the power down signal | ||
|
||
- adi,clock-delay: Video data clock delay relative to the pixel clock, in ps | ||
(-1200 ps .. 1600 ps). Defaults to no delay. | ||
- adi,embedded-sync: The input uses synchronization signals embedded in the | ||
data stream (similar to BT.656). Defaults to separate H/V synchronization | ||
signals. | ||
|
||
Required nodes: | ||
|
||
The ADV7511 has two video ports. Their connections are modelled using the OF | ||
graph bindings specified in Documentation/devicetree/bindings/graph.txt. | ||
|
||
- Video port 0 for the RGB or YUV input | ||
- Video port 1 for the HDMI output | ||
|
||
|
||
Example | ||
------- | ||
|
||
adv7511w: hdmi@39 { | ||
compatible = "adi,adv7511w"; | ||
reg = <39>; | ||
interrupt-parent = <&gpio3>; | ||
interrupts = <29 IRQ_TYPE_EDGE_FALLING>; | ||
|
||
adi,input-depth = <8>; | ||
adi,input-colorspace = "rgb"; | ||
adi,input-clock = "1x"; | ||
adi,input-style = <1>; | ||
adi,input-justification = "evenly"; | ||
|
||
ports { | ||
#address-cells = <1>; | ||
#size-cells = <0>; | ||
|
||
port@0 { | ||
reg = <0>; | ||
adv7511w_in: endpoint { | ||
remote-endpoint = <&dpi_out>; | ||
}; | ||
}; | ||
|
||
port@1 { | ||
reg = <1>; | ||
adv7511_out: endpoint { | ||
remote-endpoint = <&hdmi_connector_in>; | ||
}; | ||
}; | ||
}; | ||
}; |
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.