1 .. SPDX-License-Identifier: GPL-2.0 1 .. SPDX-License-Identifier: GPL-2.0
2 2
3 ======== 3 ========
4 HDMI CEC 4 HDMI CEC
5 ======== 5 ========
6 6
7 Supported hardware in mainline 7 Supported hardware in mainline
8 ============================== 8 ==============================
9 9
10 HDMI Transmitters: 10 HDMI Transmitters:
11 11
12 - Exynos4 12 - Exynos4
13 - Exynos5 13 - Exynos5
14 - STIH4xx HDMI CEC 14 - STIH4xx HDMI CEC
15 - V4L2 adv7511 (same HW, but a different drive 15 - V4L2 adv7511 (same HW, but a different driver from the drm adv7511)
16 - stm32 16 - stm32
17 - Allwinner A10 (sun4i) 17 - Allwinner A10 (sun4i)
18 - Raspberry Pi 18 - Raspberry Pi
19 - dw-hdmi (Synopsis IP) 19 - dw-hdmi (Synopsis IP)
20 - amlogic (meson ao-cec and ao-cec-g12a) 20 - amlogic (meson ao-cec and ao-cec-g12a)
21 - drm adv7511/adv7533 21 - drm adv7511/adv7533
22 - omap4 22 - omap4
23 - tegra 23 - tegra
24 - rk3288, rk3399 24 - rk3288, rk3399
25 - tda998x 25 - tda998x
26 - DisplayPort CEC-Tunneling-over-AUX on i915, 26 - DisplayPort CEC-Tunneling-over-AUX on i915, nouveau and amdgpu
27 - ChromeOS EC CEC 27 - ChromeOS EC CEC
28 - CEC for SECO boards (UDOO x86). 28 - CEC for SECO boards (UDOO x86).
29 - Chrontel CH7322 29 - Chrontel CH7322
30 30
31 31
32 HDMI Receivers: 32 HDMI Receivers:
33 33
34 - adv7604/11/12 34 - adv7604/11/12
35 - adv7842 35 - adv7842
36 - tc358743 36 - tc358743
37 37
38 USB Dongles (see below for additional informat 38 USB Dongles (see below for additional information on how to use these
39 dongles): 39 dongles):
40 40
41 - Pulse-Eight: the pulse8-cec driver implement 41 - Pulse-Eight: the pulse8-cec driver implements the following module option:
42 ``persistent_config``: by default this is of 42 ``persistent_config``: by default this is off, but when set to 1 the driver
43 will store the current settings to the devic 43 will store the current settings to the device's internal eeprom and restore
44 it the next time the device is connected to 44 it the next time the device is connected to the USB port.
45 45
46 - RainShadow Tech. Note: this driver does not 46 - RainShadow Tech. Note: this driver does not support the persistent_config
47 module option of the Pulse-Eight driver. The 47 module option of the Pulse-Eight driver. The hardware supports it, but I
48 have no plans to add this feature. But I acc 48 have no plans to add this feature. But I accept patches :-)
49 49
50 - Extron DA HD 4K PLUS HDMI Distribution Ampli 50 - Extron DA HD 4K PLUS HDMI Distribution Amplifier. See
51 :ref:`extron_da_hd_4k_plus` for more informa 51 :ref:`extron_da_hd_4k_plus` for more information.
52 52
53 Miscellaneous: 53 Miscellaneous:
54 54
55 - vivid: emulates a CEC receiver and CEC trans 55 - vivid: emulates a CEC receiver and CEC transmitter.
56 Can be used to test CEC applications without 56 Can be used to test CEC applications without actual CEC hardware.
57 57
58 - cec-gpio. If the CEC pin is hooked up to a G 58 - cec-gpio. If the CEC pin is hooked up to a GPIO pin then
59 you can control the CEC line through this dr 59 you can control the CEC line through this driver. This supports error
60 injection as well. 60 injection as well.
61 61
62 - cec-gpio and Allwinner A10 (or any other dri 62 - cec-gpio and Allwinner A10 (or any other driver that uses the CEC pin
63 framework to drive the CEC pin directly): th 63 framework to drive the CEC pin directly): the CEC pin framework uses
64 high-resolution timers. These timers are aff 64 high-resolution timers. These timers are affected by NTP daemons that
65 speed up or slow down the clock to sync with 65 speed up or slow down the clock to sync with the official time. The
66 chronyd server will by default increase or d 66 chronyd server will by default increase or decrease the clock by
67 1/12th. This will cause the CEC timings to g 67 1/12th. This will cause the CEC timings to go out of spec. To fix this,
68 add a 'maxslewrate 40000' line to chronyd.co 68 add a 'maxslewrate 40000' line to chronyd.conf. This limits the clock
69 frequency change to 1/25th, which keeps the 69 frequency change to 1/25th, which keeps the CEC timings within spec.
70 70
71 71
72 Utilities 72 Utilities
73 ========= 73 =========
74 74
75 Utilities are available here: https://git.linu 75 Utilities are available here: https://git.linuxtv.org/v4l-utils.git
76 76
77 ``utils/cec-ctl``: control a CEC device 77 ``utils/cec-ctl``: control a CEC device
78 78
79 ``utils/cec-compliance``: test compliance of a 79 ``utils/cec-compliance``: test compliance of a remote CEC device
80 80
81 ``utils/cec-follower``: emulate a CEC follower 81 ``utils/cec-follower``: emulate a CEC follower device
82 82
83 Note that ``cec-ctl`` has support for the CEC 83 Note that ``cec-ctl`` has support for the CEC Hospitality Profile as is
84 used in some hotel displays. See http://www.ht 84 used in some hotel displays. See http://www.htng.org.
85 85
86 Note that the libcec library (https://github.c 86 Note that the libcec library (https://github.com/Pulse-Eight/libcec) supports
87 the linux CEC framework. 87 the linux CEC framework.
88 88
89 If you want to get the CEC specification, then 89 If you want to get the CEC specification, then look at the References of
90 the HDMI wikipedia page: https://en.wikipedia. 90 the HDMI wikipedia page: https://en.wikipedia.org/wiki/HDMI. CEC is part
91 of the HDMI specification. HDMI 1.3 is freely 91 of the HDMI specification. HDMI 1.3 is freely available (very similar to
92 HDMI 1.4 w.r.t. CEC) and should be good enough 92 HDMI 1.4 w.r.t. CEC) and should be good enough for most things.
93 93
94 94
95 DisplayPort to HDMI Adapters with working CEC 95 DisplayPort to HDMI Adapters with working CEC
96 ============================================= 96 =============================================
97 97
98 Background: most adapters do not support the C 98 Background: most adapters do not support the CEC Tunneling feature,
99 and of those that do many did not actually con 99 and of those that do many did not actually connect the CEC pin.
100 Unfortunately, this means that while a CEC dev 100 Unfortunately, this means that while a CEC device is created, it
101 is actually all alone in the world and will ne 101 is actually all alone in the world and will never be able to see other
102 CEC devices. 102 CEC devices.
103 103
104 This is a list of known working adapters that 104 This is a list of known working adapters that have CEC Tunneling AND
105 that properly connected the CEC pin. If you fi 105 that properly connected the CEC pin. If you find adapters that work
106 but are not in this list, then drop me a note. 106 but are not in this list, then drop me a note.
107 107
108 To test: hook up your DP-to-HDMI adapter to a 108 To test: hook up your DP-to-HDMI adapter to a CEC capable device
109 (typically a TV), then run:: 109 (typically a TV), then run::
110 110
111 cec-ctl --playback # Configure th 111 cec-ctl --playback # Configure the PC as a CEC Playback device
112 cec-ctl -S # Show the CEC 112 cec-ctl -S # Show the CEC topology
113 113
114 The ``cec-ctl -S`` command should show at leas 114 The ``cec-ctl -S`` command should show at least two CEC devices,
115 ourselves and the CEC device you are connected 115 ourselves and the CEC device you are connected to (i.e. typically the TV).
116 116
117 General note: I have only seen this work with 117 General note: I have only seen this work with the Parade PS175, PS176 and
118 PS186 chipsets and the MegaChips 2900. While M 118 PS186 chipsets and the MegaChips 2900. While MegaChips 28x0 claims CEC support,
119 I have never seen it work. 119 I have never seen it work.
120 120
121 USB-C to HDMI 121 USB-C to HDMI
122 ------------- 122 -------------
123 123
124 Samsung Multiport Adapter EE-PW700: https://ww 124 Samsung Multiport Adapter EE-PW700: https://www.samsung.com/ie/support/model/EE-PW700BBEGWW/
125 125
126 Kramer ADC-U31C/HF: https://www.kramerav.com/p 126 Kramer ADC-U31C/HF: https://www.kramerav.com/product/ADC-U31C/HF
127 127
128 Club3D CAC-2504: https://www.club-3d.com/en/de 128 Club3D CAC-2504: https://www.club-3d.com/en/detail/2449/usb_3.1_type_c_to_hdmi_2.0_uhd_4k_60hz_active_adapter/
129 129
130 DisplayPort to HDMI 130 DisplayPort to HDMI
131 ------------------- 131 -------------------
132 132
133 Club3D CAC-1080: https://www.club-3d.com/en/de 133 Club3D CAC-1080: https://www.club-3d.com/en/detail/2442/displayport_1.4_to_hdmi_2.0b_hdr/
134 134
135 CableCreation (SKU: CD0712): https://www.cable 135 CableCreation (SKU: CD0712): https://www.cablecreation.com/products/active-displayport-to-hdmi-adapter-4k-hdr
136 136
137 HP DisplayPort to HDMI True 4k Adapter (P/N 2J 137 HP DisplayPort to HDMI True 4k Adapter (P/N 2JA63AA): https://www.hp.com/us-en/shop/pdp/hp-displayport-to-hdmi-true-4k-adapter
138 138
139 Mini-DisplayPort to HDMI 139 Mini-DisplayPort to HDMI
140 ------------------------ 140 ------------------------
141 141
142 Club3D CAC-1180: https://www.club-3d.com/en/de 142 Club3D CAC-1180: https://www.club-3d.com/en/detail/2443/mini_displayport_1.4_to_hdmi_2.0b_hdr/
143 143
144 Note that passive adapters will never work, yo 144 Note that passive adapters will never work, you need an active adapter.
145 145
146 The Club3D adapters in this list are all MegaC 146 The Club3D adapters in this list are all MegaChips 2900 based. Other Club3D adapters
147 are PS176 based and do NOT have the CEC pin ho 147 are PS176 based and do NOT have the CEC pin hooked up, so only the three Club3D
148 adapters above are known to work. 148 adapters above are known to work.
149 149
150 I suspect that MegaChips 2900 based designs in 150 I suspect that MegaChips 2900 based designs in general are likely to work
151 whereas with the PS176 it is more hit-and-miss 151 whereas with the PS176 it is more hit-and-miss (mostly miss). The PS186 is
152 likely to have the CEC pin hooked up, it looks 152 likely to have the CEC pin hooked up, it looks like they changed the reference
153 design for that chipset. 153 design for that chipset.
154 154
155 155
156 USB CEC Dongles 156 USB CEC Dongles
157 =============== 157 ===============
158 158
159 These dongles appear as ``/dev/ttyACMX`` devic 159 These dongles appear as ``/dev/ttyACMX`` devices and need the ``inputattach``
160 utility to create the ``/dev/cecX`` devices. S 160 utility to create the ``/dev/cecX`` devices. Support for the Pulse-Eight
161 has been added to ``inputattach`` 1.6.0. Suppo 161 has been added to ``inputattach`` 1.6.0. Support for the Rainshadow Tech has
162 been added to ``inputattach`` 1.6.1. 162 been added to ``inputattach`` 1.6.1.
163 163
164 You also need udev rules to automatically star 164 You also need udev rules to automatically start systemd services::
165 165
166 SUBSYSTEM=="tty", KERNEL=="ttyACM[0-9] 166 SUBSYSTEM=="tty", KERNEL=="ttyACM[0-9]*", ATTRS{idVendor}=="2548", ATTRS{idProduct}=="1002", ACTION=="add", TAG+="systemd", ENV{SYSTEMD_WANTS}+="pulse8-cec-inputattach@%k.service"
167 SUBSYSTEM=="tty", KERNEL=="ttyACM[0-9] 167 SUBSYSTEM=="tty", KERNEL=="ttyACM[0-9]*", ATTRS{idVendor}=="2548", ATTRS{idProduct}=="1001", ACTION=="add", TAG+="systemd", ENV{SYSTEMD_WANTS}+="pulse8-cec-inputattach@%k.service"
168 SUBSYSTEM=="tty", KERNEL=="ttyACM[0-9] 168 SUBSYSTEM=="tty", KERNEL=="ttyACM[0-9]*", ATTRS{idVendor}=="04d8", ATTRS{idProduct}=="ff59", ACTION=="add", TAG+="systemd", ENV{SYSTEMD_WANTS}+="rainshadow-cec-inputattach@%k.service"
169 169
170 and these systemd services: 170 and these systemd services:
171 171
172 For Pulse-Eight make /lib/systemd/system/pulse 172 For Pulse-Eight make /lib/systemd/system/pulse8-cec-inputattach@.service::
173 173
174 [Unit] 174 [Unit]
175 Description=inputattach for pulse8-cec 175 Description=inputattach for pulse8-cec device on %I
176 176
177 [Service] 177 [Service]
178 Type=simple 178 Type=simple
179 ExecStart=/usr/bin/inputattach --pulse 179 ExecStart=/usr/bin/inputattach --pulse8-cec /dev/%I
180 180
181 For the RainShadow Tech make /lib/systemd/syst 181 For the RainShadow Tech make /lib/systemd/system/rainshadow-cec-inputattach@.service::
182 182
183 [Unit] 183 [Unit]
184 Description=inputattach for rainshadow 184 Description=inputattach for rainshadow-cec device on %I
185 185
186 [Service] 186 [Service]
187 Type=simple 187 Type=simple
188 ExecStart=/usr/bin/inputattach --rains 188 ExecStart=/usr/bin/inputattach --rainshadow-cec /dev/%I
189 189
190 190
191 For proper suspend/resume support create: /lib 191 For proper suspend/resume support create: /lib/systemd/system/restart-cec-inputattach.service::
192 192
193 [Unit] 193 [Unit]
194 Description=restart inputattach for ce 194 Description=restart inputattach for cec devices
195 After=suspend.target 195 After=suspend.target
196 196
197 [Service] 197 [Service]
198 Type=forking 198 Type=forking
199 ExecStart=/bin/bash -c 'for d in /dev/ 199 ExecStart=/bin/bash -c 'for d in /dev/serial/by-id/usb-Pulse-Eight*; do /usr/bin/inputattach --daemon --pulse8-cec $d; done; for d in /dev/serial/by-id/usb-RainShadow_Tech*; do /usr/bin/inputattach --daemon --rainshadow-cec $d; done'
200 200
201 [Install] 201 [Install]
202 WantedBy=suspend.target 202 WantedBy=suspend.target
203 203
204 And run ``systemctl enable restart-cec-inputat 204 And run ``systemctl enable restart-cec-inputattach``.
205 205
206 To automatically set the physical address of t 206 To automatically set the physical address of the CEC device whenever the
207 EDID changes, you can use ``cec-ctl`` with the 207 EDID changes, you can use ``cec-ctl`` with the ``-E`` option::
208 208
209 cec-ctl -E /sys/class/drm/card0-DP-1/e 209 cec-ctl -E /sys/class/drm/card0-DP-1/edid
210 210
211 This assumes the dongle is connected to the ca 211 This assumes the dongle is connected to the card0-DP-1 output (``xrandr`` will tell
212 you which output is used) and it will poll for 212 you which output is used) and it will poll for changes to the EDID and update
213 the Physical Address whenever they occur. 213 the Physical Address whenever they occur.
214 214
215 To automatically run this command you can use 215 To automatically run this command you can use cron. Edit crontab with
216 ``crontab -e`` and add this line:: 216 ``crontab -e`` and add this line::
217 217
218 @reboot /usr/local/bin/cec-ctl -E /sys 218 @reboot /usr/local/bin/cec-ctl -E /sys/class/drm/card0-DP-1/edid
219 219
220 This only works for display drivers that expos 220 This only works for display drivers that expose the EDID in ``/sys/class/drm``,
221 such as the i915 driver. 221 such as the i915 driver.
222 222
223 223
224 CEC Without HPD 224 CEC Without HPD
225 =============== 225 ===============
226 226
227 Some displays when in standby mode have no HDM 227 Some displays when in standby mode have no HDMI Hotplug Detect signal, but
228 CEC is still enabled so connected devices can 228 CEC is still enabled so connected devices can send an <Image View On> CEC
229 message in order to wake up such displays. Unf 229 message in order to wake up such displays. Unfortunately, not all CEC
230 adapters can support this. An example is the O 230 adapters can support this. An example is the Odroid-U3 SBC that has a
231 level-shifter that is powered off when the HPD 231 level-shifter that is powered off when the HPD signal is low, thus
232 blocking the CEC pin. Even though the SoC can 232 blocking the CEC pin. Even though the SoC can use CEC without a HPD,
233 the level-shifter will prevent this from funct 233 the level-shifter will prevent this from functioning.
234 234
235 There is a CEC capability flag to signal this: 235 There is a CEC capability flag to signal this: ``CEC_CAP_NEEDS_HPD``.
236 If set, then the hardware cannot wake up displ 236 If set, then the hardware cannot wake up displays with this behavior.
237 237
238 Note for CEC application implementers: the <Im 238 Note for CEC application implementers: the <Image View On> message must
239 be the first message you send, don't send any 239 be the first message you send, don't send any other messages before.
240 Certain very bad but unfortunately not uncommo 240 Certain very bad but unfortunately not uncommon CEC implementations
241 get very confused if they receive anything els 241 get very confused if they receive anything else but this message and
242 they won't wake up. 242 they won't wake up.
243 243
244 When writing a driver it can be tricky to test 244 When writing a driver it can be tricky to test this. There are two
245 ways to do this: 245 ways to do this:
246 246
247 1) Get a Pulse-Eight USB CEC dongle, connect a 247 1) Get a Pulse-Eight USB CEC dongle, connect an HDMI cable from your
248 device to the Pulse-Eight, but do not conne 248 device to the Pulse-Eight, but do not connect the Pulse-Eight to
249 the display. 249 the display.
250 250
251 Now configure the Pulse-Eight dongle:: 251 Now configure the Pulse-Eight dongle::
252 252
253 cec-ctl -p0.0.0.0 --tv 253 cec-ctl -p0.0.0.0 --tv
254 254
255 and start monitoring:: 255 and start monitoring::
256 256
257 sudo cec-ctl -M 257 sudo cec-ctl -M
258 258
259 On the device you are testing run:: 259 On the device you are testing run::
260 260
261 cec-ctl --playback 261 cec-ctl --playback
262 262
263 It should report a physical address of f.f. 263 It should report a physical address of f.f.f.f. Now run this
264 command:: 264 command::
265 265
266 cec-ctl -t0 --image-view-on 266 cec-ctl -t0 --image-view-on
267 267
268 The Pulse-Eight should see the <Image View 268 The Pulse-Eight should see the <Image View On> message. If not,
269 then something (hardware and/or software) i 269 then something (hardware and/or software) is preventing the CEC
270 message from going out. 270 message from going out.
271 271
272 To make sure you have the wiring correct ju 272 To make sure you have the wiring correct just connect the
273 Pulse-Eight to a CEC-enabled display and ru 273 Pulse-Eight to a CEC-enabled display and run the same command
274 on your device: now there is a HPD, so you 274 on your device: now there is a HPD, so you should see the command
275 arriving at the Pulse-Eight. 275 arriving at the Pulse-Eight.
276 276
277 2) If you have another linux device supporting 277 2) If you have another linux device supporting CEC without HPD, then
278 you can just connect your device to that de 278 you can just connect your device to that device. Yes, you can connect
279 two HDMI outputs together. You won't have a 279 two HDMI outputs together. You won't have a HPD (which is what we
280 want for this test), but the second device 280 want for this test), but the second device can monitor the CEC pin.
281 281
282 Otherwise use the same commands as in 1. 282 Otherwise use the same commands as in 1.
283 283
284 If CEC messages do not come through when there 284 If CEC messages do not come through when there is no HPD, then you
285 need to figure out why. Typically it is either 285 need to figure out why. Typically it is either a hardware restriction
286 or the software powers off the CEC core when t 286 or the software powers off the CEC core when the HPD goes low. The
287 first cannot be corrected of course, the secon 287 first cannot be corrected of course, the second will likely required
288 driver changes. 288 driver changes.
289 289
290 290
291 Microcontrollers & CEC 291 Microcontrollers & CEC
292 ====================== 292 ======================
293 293
294 We have seen some CEC implementations in displ 294 We have seen some CEC implementations in displays that use a microcontroller
295 to sample the bus. This does not have to be a 295 to sample the bus. This does not have to be a problem, but some implementations
296 have timing issues. This is hard to discover u 296 have timing issues. This is hard to discover unless you can hook up a low-level
297 CEC debugger (see the next section). 297 CEC debugger (see the next section).
298 298
299 You will see cases where the CEC transmitter h 299 You will see cases where the CEC transmitter holds the CEC line high or low for
300 a longer time than is allowed. For directed me 300 a longer time than is allowed. For directed messages this is not a problem since
301 if that happens the message will not be Acked 301 if that happens the message will not be Acked and it will be retransmitted.
302 For broadcast messages no such mechanism exist 302 For broadcast messages no such mechanism exists.
303 303
304 It's not clear what to do about this. It is pr 304 It's not clear what to do about this. It is probably wise to transmit some
305 broadcast messages twice to reduce the chance 305 broadcast messages twice to reduce the chance of them being lost. Specifically
306 <Standby> and <Active Source> are candidates f 306 <Standby> and <Active Source> are candidates for that.
307 307
308 308
309 Making a CEC debugger 309 Making a CEC debugger
310 ===================== 310 =====================
311 311
312 By using a Raspberry Pi 4B and some cheap comp 312 By using a Raspberry Pi 4B and some cheap components you can make
313 your own low-level CEC debugger. 313 your own low-level CEC debugger.
314 314
315 The critical component is one of these HDMI fe 315 The critical component is one of these HDMI female-female passthrough connectors
316 (full soldering type 1): 316 (full soldering type 1):
317 317
318 https://elabbay.myshopify.com/collections/came 318 https://elabbay.myshopify.com/collections/camera/products/hdmi-af-af-v1a-hdmi-type-a-female-to-hdmi-type-a-female-pass-through-adapter-breakout-board?variant=45533926147
319 319
320 The video quality is variable and certainly no 320 The video quality is variable and certainly not enough to pass-through 4kp60
321 (594 MHz) video. You might be able to support 321 (594 MHz) video. You might be able to support 4kp30, but more likely you will
322 be limited to 1080p60 (148.5 MHz). But for CEC 322 be limited to 1080p60 (148.5 MHz). But for CEC testing that is fine.
323 323
324 You need a breadboard and some breadboard wire 324 You need a breadboard and some breadboard wires:
325 325
326 http://www.dx.com/p/diy-40p-male-to-female-mal 326 http://www.dx.com/p/diy-40p-male-to-female-male-to-male-female-to-female-dupont-line-wire-3pcs-356089#.WYLOOXWGN7I
327 327
328 If you want to monitor the HPD and/or 5V lines 328 If you want to monitor the HPD and/or 5V lines as well, then you need one of
329 these 5V to 3.3V level shifters: 329 these 5V to 3.3V level shifters:
330 330
331 https://www.adafruit.com/product/757 331 https://www.adafruit.com/product/757
332 332
333 (This is just where I got these components, th 333 (This is just where I got these components, there are many other places you
334 can get similar things). 334 can get similar things).
335 335
336 The ground pin of the HDMI connector needs to 336 The ground pin of the HDMI connector needs to be connected to a ground
337 pin of the Raspberry Pi, of course. 337 pin of the Raspberry Pi, of course.
338 338
339 The CEC pin of the HDMI connector needs to be 339 The CEC pin of the HDMI connector needs to be connected to these pins:
340 GPIO 6 and GPIO 7. The optional HPD pin of the 340 GPIO 6 and GPIO 7. The optional HPD pin of the HDMI connector should
341 be connected via the level shifter to these pi 341 be connected via the level shifter to these pins: GPIO 23 and GPIO 12.
342 The optional 5V pin of the HDMI connector shou 342 The optional 5V pin of the HDMI connector should be connected via the
343 level shifter to these pins: GPIO 25 and GPIO 343 level shifter to these pins: GPIO 25 and GPIO 22. Monitoring the HPD and
344 5V lines is not necessary, but it is helpful. 344 5V lines is not necessary, but it is helpful.
345 345
346 This device tree addition in ``arch/arm/boot/d 346 This device tree addition in ``arch/arm/boot/dts/bcm2711-rpi-4-b.dts``
347 will hook up the cec-gpio driver correctly:: 347 will hook up the cec-gpio driver correctly::
348 348
349 cec@6 { 349 cec@6 {
350 compatible = "cec-gpio"; 350 compatible = "cec-gpio";
351 cec-gpios = <&gpio 6 (GPIO_ACT 351 cec-gpios = <&gpio 6 (GPIO_ACTIVE_HIGH|GPIO_OPEN_DRAIN)>;
352 hpd-gpios = <&gpio 23 GPIO_ACT 352 hpd-gpios = <&gpio 23 GPIO_ACTIVE_HIGH>;
353 v5-gpios = <&gpio 25 GPIO_ACTI 353 v5-gpios = <&gpio 25 GPIO_ACTIVE_HIGH>;
354 }; 354 };
355 355
356 cec@7 { 356 cec@7 {
357 compatible = "cec-gpio"; 357 compatible = "cec-gpio";
358 cec-gpios = <&gpio 7 (GPIO_ACT 358 cec-gpios = <&gpio 7 (GPIO_ACTIVE_HIGH|GPIO_OPEN_DRAIN)>;
359 hpd-gpios = <&gpio 12 GPIO_ACT 359 hpd-gpios = <&gpio 12 GPIO_ACTIVE_HIGH>;
360 v5-gpios = <&gpio 22 GPIO_ACTI 360 v5-gpios = <&gpio 22 GPIO_ACTIVE_HIGH>;
361 }; 361 };
362 362
363 If you haven't hooked up the HPD and/or 5V lin 363 If you haven't hooked up the HPD and/or 5V lines, then just delete those
364 lines. 364 lines.
365 365
366 This dts change will enable two cec GPIO devic 366 This dts change will enable two cec GPIO devices: I typically use one to
367 send/receive CEC commands and the other to mon 367 send/receive CEC commands and the other to monitor. If you monitor using
368 an unconfigured CEC adapter then it will use G 368 an unconfigured CEC adapter then it will use GPIO interrupts which makes
369 monitoring very accurate. 369 monitoring very accurate.
370 370
371 If you just want to monitor traffic, then a si 371 If you just want to monitor traffic, then a single instance is sufficient.
372 The minimum configuration is one HDMI female-f 372 The minimum configuration is one HDMI female-female passthrough connector
373 and two female-female breadboard wires: one fo 373 and two female-female breadboard wires: one for connecting the HDMI ground
374 pin to a ground pin on the Raspberry Pi, and t 374 pin to a ground pin on the Raspberry Pi, and the other to connect the HDMI
375 CEC pin to GPIO 6 on the Raspberry Pi. 375 CEC pin to GPIO 6 on the Raspberry Pi.
376 376
377 The documentation on how to use the error inje 377 The documentation on how to use the error injection is here: :ref:`cec_pin_error_inj`.
378 378
379 ``cec-ctl --monitor-pin`` will do low-level CE 379 ``cec-ctl --monitor-pin`` will do low-level CEC bus sniffing and analysis.
380 You can also store the CEC traffic to file usi 380 You can also store the CEC traffic to file using ``--store-pin`` and analyze
381 it later using ``--analyze-pin``. 381 it later using ``--analyze-pin``.
382 382
383 You can also use this as a full-fledged CEC de 383 You can also use this as a full-fledged CEC device by configuring it
384 using ``cec-ctl --tv -p0.0.0.0`` or ``cec-ctl 384 using ``cec-ctl --tv -p0.0.0.0`` or ``cec-ctl --playback -p1.0.0.0``.
385 385
386 .. _extron_da_hd_4k_plus: 386 .. _extron_da_hd_4k_plus:
387 387
388 Extron DA HD 4K PLUS CEC Adapter driver 388 Extron DA HD 4K PLUS CEC Adapter driver
389 ======================================= 389 =======================================
390 390
391 This driver is for the Extron DA HD 4K PLUS se 391 This driver is for the Extron DA HD 4K PLUS series of HDMI Distribution
392 Amplifiers: https://www.extron.com/product/dah 392 Amplifiers: https://www.extron.com/product/dahd4kplusseries
393 393
394 The 2, 4 and 6 port models are supported. 394 The 2, 4 and 6 port models are supported.
395 395
396 Firmware version 1.02.0001 or higher is requir 396 Firmware version 1.02.0001 or higher is required.
397 397
398 Note that older Extron hardware revisions have 398 Note that older Extron hardware revisions have a problem with the CEC voltage,
399 which may mean that CEC will not work. This is 399 which may mean that CEC will not work. This is fixed in hardware revisions
400 E34814 and up. 400 E34814 and up.
401 401
402 The CEC support has two modes: the first is a 402 The CEC support has two modes: the first is a manual mode where userspace has
403 to manually control CEC for the HDMI Input and 403 to manually control CEC for the HDMI Input and all HDMI Outputs. While this gives
404 full control, it is also complicated. 404 full control, it is also complicated.
405 405
406 The second mode is an automatic mode, which is 406 The second mode is an automatic mode, which is selected if the module option
407 ``vendor_id`` is set. In that case the driver 407 ``vendor_id`` is set. In that case the driver controls CEC and CEC messages
408 received in the input will be distributed to t 408 received in the input will be distributed to the outputs. It is still possible
409 to use the /dev/cecX devices to talk to the co 409 to use the /dev/cecX devices to talk to the connected devices directly, but it is
410 the driver that configures everything and deal 410 the driver that configures everything and deals with things like Hotplug Detect
411 changes. 411 changes.
412 412
413 The driver also takes care of the EDIDs: /dev/ 413 The driver also takes care of the EDIDs: /dev/videoX devices are created to
414 read the EDIDs and (for the HDMI Input port) t 414 read the EDIDs and (for the HDMI Input port) to set the EDID.
415 415
416 By default userspace is responsible to set the 416 By default userspace is responsible to set the EDID for the HDMI Input
417 according to the EDIDs of the connected displa 417 according to the EDIDs of the connected displays. But if the ``manufacturer_name``
418 module option is set, then the driver will tak 418 module option is set, then the driver will take care of setting the EDID
419 of the HDMI Input based on the supported resol 419 of the HDMI Input based on the supported resolutions of the connected displays.
420 Currently the driver only supports resolutions 420 Currently the driver only supports resolutions 1080p60 and 4kp60: if all connected
421 displays support 4kp60, then it will advertise 421 displays support 4kp60, then it will advertise 4kp60 on the HDMI input, otherwise
422 it will fall back to an EDID that just reports 422 it will fall back to an EDID that just reports 1080p60.
423 423
424 The status of the Extron is reported in ``/sys 424 The status of the Extron is reported in ``/sys/kernel/debug/cec/cecX/status``.
425 425
426 The extron-da-hd-4k-plus driver implements the 426 The extron-da-hd-4k-plus driver implements the following module options:
427 427
428 ``debug`` 428 ``debug``
429 --------- 429 ---------
430 430
431 If set to 1, then all serial port traffic is s 431 If set to 1, then all serial port traffic is shown.
432 432
433 ``vendor_id`` 433 ``vendor_id``
434 ------------- 434 -------------
435 435
436 The CEC Vendor ID to report to connected displ 436 The CEC Vendor ID to report to connected displays.
437 437
438 If set, then the driver will take care of dist 438 If set, then the driver will take care of distributing CEC messages received
439 on the input to the HDMI outputs. This is done 439 on the input to the HDMI outputs. This is done for the following CEC messages:
440 440
441 - <Standby> 441 - <Standby>
442 - <Image View On> and <Text View On> 442 - <Image View On> and <Text View On>
443 - <Give Device Power Status> 443 - <Give Device Power Status>
444 - <Set System Audio Mode> 444 - <Set System Audio Mode>
445 - <Request Current Latency> 445 - <Request Current Latency>
446 446
447 If not set, then userspace is responsible for 447 If not set, then userspace is responsible for this, and it will have to
448 configure the CEC devices for HDMI Input and t 448 configure the CEC devices for HDMI Input and the HDMI Outputs manually.
449 449
450 ``manufacturer_name`` 450 ``manufacturer_name``
451 --------------------- 451 ---------------------
452 452
453 A three character manufacturer name that is us 453 A three character manufacturer name that is used in the EDID for the HDMI
454 Input. If not set, then userspace is reponsibl 454 Input. If not set, then userspace is reponsible for configuring an EDID.
455 If set, then the driver will update the EDID a 455 If set, then the driver will update the EDID automatically based on the
456 resolutions supported by the connected display 456 resolutions supported by the connected displays, and it will not be possible
457 anymore to manually set the EDID for the HDMI 457 anymore to manually set the EDID for the HDMI Input.
458 458
459 ``hpd_never_low`` 459 ``hpd_never_low``
460 ----------------- 460 -----------------
461 461
462 If set, then the Hotplug Detect pin of the HDM 462 If set, then the Hotplug Detect pin of the HDMI Input will always be high,
463 even if nothing is connected to the HDMI Outpu 463 even if nothing is connected to the HDMI Outputs. If not set (the default)
464 then the Hotplug Detect pin of the HDMI input 464 then the Hotplug Detect pin of the HDMI input will go low if all the detected
465 Hotplug Detect pins of the HDMI Outputs are al 465 Hotplug Detect pins of the HDMI Outputs are also low.
466 466
467 This option may be changed dynamically. 467 This option may be changed dynamically.
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.