2 * Copyright (c) 2014 Samsung Electronics Co., Ltd
4 * Permission is hereby granted, free of charge, to any person obtaining a
5 * copy of this software and associated documentation files (the "Software"),
6 * to deal in the Software without restriction, including without limitation
7 * the rights to use, copy, modify, merge, publish, distribute, sub license,
8 * and/or sell copies of the Software, and to permit persons to whom the
9 * Software is furnished to do so, subject to the following conditions:
11 * The above copyright notice and this permission notice (including the
12 * next paragraph) shall be included in all copies or substantial portions
15 * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16 * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17 * FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL
18 * THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19 * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
20 * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
21 * DEALINGS IN THE SOFTWARE.
24 #include <linux/err.h>
25 #include <linux/media-bus-format.h>
26 #include <linux/module.h>
27 #include <linux/mutex.h>
29 #include <drm/drm_atomic_state_helper.h>
30 #include <drm/drm_bridge.h>
31 #include <drm/drm_debugfs.h>
32 #include <drm/drm_edid.h>
33 #include <drm/drm_encoder.h>
34 #include <drm/drm_file.h>
35 #include <drm/drm_of.h>
36 #include <drm/drm_print.h>
38 #include "drm_crtc_internal.h"
43 * &struct drm_bridge represents a device that hangs on to an encoder. These are
44 * handy when a regular &drm_encoder entity isn't enough to represent the entire
47 * A bridge is always attached to a single &drm_encoder at a time, but can be
48 * either connected to it directly, or through a chain of bridges::
50 * [ CRTC ---> ] Encoder ---> Bridge A ---> Bridge B
52 * Here, the output of the encoder feeds to bridge A, and that furthers feeds to
53 * bridge B. Bridge chains can be arbitrarily long, and shall be fully linear:
54 * Chaining multiple bridges to the output of a bridge, or the same bridge to
55 * the output of different bridges, is not supported.
57 * &drm_bridge, like &drm_panel, aren't &drm_mode_object entities like planes,
58 * CRTCs, encoders or connectors and hence are not visible to userspace. They
59 * just provide additional hooks to get the desired output at the end of the
64 * DOC: display driver integration
66 * Display drivers are responsible for linking encoders with the first bridge
67 * in the chains. This is done by acquiring the appropriate bridge with
68 * devm_drm_of_get_bridge(). Once acquired, the bridge shall be attached to the
69 * encoder with a call to drm_bridge_attach().
71 * Bridges are responsible for linking themselves with the next bridge in the
72 * chain, if any. This is done the same way as for encoders, with the call to
73 * drm_bridge_attach() occurring in the &drm_bridge_funcs.attach operation.
75 * Once these links are created, the bridges can participate along with encoder
76 * functions to perform mode validation and fixup (through
77 * drm_bridge_chain_mode_valid() and drm_atomic_bridge_chain_check()), mode
78 * setting (through drm_bridge_chain_mode_set()), enable (through
79 * drm_atomic_bridge_chain_pre_enable() and drm_atomic_bridge_chain_enable())
80 * and disable (through drm_atomic_bridge_chain_disable() and
81 * drm_atomic_bridge_chain_post_disable()). Those functions call the
82 * corresponding operations provided in &drm_bridge_funcs in sequence for all
83 * bridges in the chain.
85 * For display drivers that use the atomic helpers
86 * drm_atomic_helper_check_modeset(),
87 * drm_atomic_helper_commit_modeset_enables() and
88 * drm_atomic_helper_commit_modeset_disables() (either directly in hand-rolled
89 * commit check and commit tail handlers, or through the higher-level
90 * drm_atomic_helper_check() and drm_atomic_helper_commit_tail() or
91 * drm_atomic_helper_commit_tail_rpm() helpers), this is done transparently and
92 * requires no intervention from the driver. For other drivers, the relevant
93 * DRM bridge chain functions shall be called manually.
95 * Bridges also participate in implementing the &drm_connector at the end of
96 * the bridge chain. Display drivers may use the drm_bridge_connector_init()
97 * helper to create the &drm_connector, or implement it manually on top of the
98 * connector-related operations exposed by the bridge (see the overview
99 * documentation of bridge operations for more details).
103 * DOC: special care dsi
105 * The interaction between the bridges and other frameworks involved in
106 * the probing of the upstream driver and the bridge driver can be
107 * challenging. Indeed, there's multiple cases that needs to be
110 * - The upstream driver doesn't use the component framework and isn't a
111 * MIPI-DSI host. In this case, the bridge driver will probe at some
112 * point and the upstream driver should try to probe again by returning
113 * EPROBE_DEFER as long as the bridge driver hasn't probed.
115 * - The upstream driver doesn't use the component framework, but is a
116 * MIPI-DSI host. The bridge device uses the MIPI-DCS commands to be
117 * controlled. In this case, the bridge device is a child of the
118 * display device and when it will probe it's assured that the display
119 * device (and MIPI-DSI host) is present. The upstream driver will be
120 * assured that the bridge driver is connected between the
121 * &mipi_dsi_host_ops.attach and &mipi_dsi_host_ops.detach operations.
122 * Therefore, it must run mipi_dsi_host_register() in its probe
123 * function, and then run drm_bridge_attach() in its
124 * &mipi_dsi_host_ops.attach hook.
126 * - The upstream driver uses the component framework and is a MIPI-DSI
127 * host. The bridge device uses the MIPI-DCS commands to be
128 * controlled. This is the same situation than above, and can run
129 * mipi_dsi_host_register() in either its probe or bind hooks.
131 * - The upstream driver uses the component framework and is a MIPI-DSI
132 * host. The bridge device uses a separate bus (such as I2C) to be
133 * controlled. In this case, there's no correlation between the probe
134 * of the bridge and upstream drivers, so care must be taken to avoid
135 * an endless EPROBE_DEFER loop, with each driver waiting for the
138 * The ideal pattern to cover the last item (and all the others in the
139 * MIPI-DSI host driver case) is to split the operations like this:
141 * - The MIPI-DSI host driver must run mipi_dsi_host_register() in its
142 * probe hook. It will make sure that the MIPI-DSI host sticks around,
143 * and that the driver's bind can be called.
145 * - In its probe hook, the bridge driver must try to find its MIPI-DSI
146 * host, register as a MIPI-DSI device and attach the MIPI-DSI device
147 * to its host. The bridge driver is now functional.
149 * - In its &struct mipi_dsi_host_ops.attach hook, the MIPI-DSI host can
150 * now add its component. Its bind hook will now be called and since
151 * the bridge driver is attached and registered, we can now look for
154 * At this point, we're now certain that both the upstream driver and
155 * the bridge driver are functional and we can't have a deadlock-like
156 * situation when probing.
160 * DOC: dsi bridge operations
162 * DSI host interfaces are expected to be implemented as bridges rather than
163 * encoders, however there are a few aspects of their operation that need to
164 * be defined in order to provide a consistent interface.
166 * A DSI host should keep the PHY powered down until the pre_enable operation is
167 * called. All lanes are in an undefined idle state up to this point, and it
168 * must not be assumed that it is LP-11.
169 * pre_enable should initialise the PHY, set the data lanes to LP-11, and the
170 * clock lane to either LP-11 or HS depending on the mode_flag
171 * %MIPI_DSI_CLOCK_NON_CONTINUOUS.
173 * Ordinarily the downstream bridge DSI peripheral pre_enable will have been
174 * called before the DSI host. If the DSI peripheral requires LP-11 and/or
175 * the clock lane to be in HS mode prior to pre_enable, then it can set the
176 * &pre_enable_prev_first flag to request the pre_enable (and
177 * post_disable) order to be altered to enable the DSI host first.
179 * Either the CRTC being enabled, or the DSI host enable operation should switch
180 * the host to actively transmitting video on the data lanes.
182 * The reverse also applies. The DSI host disable operation or stopping the CRTC
183 * should stop transmitting video, and the data lanes should return to the LP-11
184 * state. The DSI host &post_disable operation should disable the PHY.
185 * If the &pre_enable_prev_first flag is set, then the DSI peripheral's
186 * bridge &post_disable will be called before the DSI host's post_disable.
188 * Whilst it is valid to call &host_transfer prior to pre_enable or after
189 * post_disable, the exact state of the lanes is undefined at this point. The
190 * DSI host should initialise the interface, transmit the data, and then disable
191 * the interface again.
193 * Ultra Low Power State (ULPS) is not explicitly supported by DRM. If
194 * implemented, it therefore needs to be handled entirely within the DSI Host
198 static DEFINE_MUTEX(bridge_lock);
199 static LIST_HEAD(bridge_list);
202 * drm_bridge_add - add the given bridge to the global bridge list
204 * @bridge: bridge control structure
206 void drm_bridge_add(struct drm_bridge *bridge)
208 mutex_init(&bridge->hpd_mutex);
210 mutex_lock(&bridge_lock);
211 list_add_tail(&bridge->list, &bridge_list);
212 mutex_unlock(&bridge_lock);
214 EXPORT_SYMBOL(drm_bridge_add);
216 static void drm_bridge_remove_void(void *bridge)
218 drm_bridge_remove(bridge);
222 * devm_drm_bridge_add - devm managed version of drm_bridge_add()
224 * @dev: device to tie the bridge lifetime to
225 * @bridge: bridge control structure
227 * This is the managed version of drm_bridge_add() which automatically
228 * calls drm_bridge_remove() when @dev is unbound.
230 * Return: 0 if no error or negative error code.
232 int devm_drm_bridge_add(struct device *dev, struct drm_bridge *bridge)
234 drm_bridge_add(bridge);
235 return devm_add_action_or_reset(dev, drm_bridge_remove_void, bridge);
237 EXPORT_SYMBOL(devm_drm_bridge_add);
240 * drm_bridge_remove - remove the given bridge from the global bridge list
242 * @bridge: bridge control structure
244 void drm_bridge_remove(struct drm_bridge *bridge)
246 mutex_lock(&bridge_lock);
247 list_del_init(&bridge->list);
248 mutex_unlock(&bridge_lock);
250 mutex_destroy(&bridge->hpd_mutex);
252 EXPORT_SYMBOL(drm_bridge_remove);
254 static struct drm_private_state *
255 drm_bridge_atomic_duplicate_priv_state(struct drm_private_obj *obj)
257 struct drm_bridge *bridge = drm_priv_to_bridge(obj);
258 struct drm_bridge_state *state;
260 state = bridge->funcs->atomic_duplicate_state(bridge);
261 return state ? &state->base : NULL;
265 drm_bridge_atomic_destroy_priv_state(struct drm_private_obj *obj,
266 struct drm_private_state *s)
268 struct drm_bridge_state *state = drm_priv_to_bridge_state(s);
269 struct drm_bridge *bridge = drm_priv_to_bridge(obj);
271 bridge->funcs->atomic_destroy_state(bridge, state);
274 static const struct drm_private_state_funcs drm_bridge_priv_state_funcs = {
275 .atomic_duplicate_state = drm_bridge_atomic_duplicate_priv_state,
276 .atomic_destroy_state = drm_bridge_atomic_destroy_priv_state,
280 * drm_bridge_attach - attach the bridge to an encoder's chain
282 * @encoder: DRM encoder
283 * @bridge: bridge to attach
284 * @previous: previous bridge in the chain (optional)
285 * @flags: DRM_BRIDGE_ATTACH_* flags
287 * Called by a kms driver to link the bridge to an encoder's chain. The previous
288 * argument specifies the previous bridge in the chain. If NULL, the bridge is
289 * linked directly at the encoder's output. Otherwise it is linked at the
290 * previous bridge's output.
292 * If non-NULL the previous bridge must be already attached by a call to this
295 * Note that bridges attached to encoders are auto-detached during encoder
296 * cleanup in drm_encoder_cleanup(), so drm_bridge_attach() should generally
297 * *not* be balanced with a drm_bridge_detach() in driver code.
300 * Zero on success, error code on failure
302 int drm_bridge_attach(struct drm_encoder *encoder, struct drm_bridge *bridge,
303 struct drm_bridge *previous,
304 enum drm_bridge_attach_flags flags)
308 if (!encoder || !bridge)
311 if (previous && (!previous->dev || previous->encoder != encoder))
317 bridge->dev = encoder->dev;
318 bridge->encoder = encoder;
321 list_add(&bridge->chain_node, &previous->chain_node);
323 list_add(&bridge->chain_node, &encoder->bridge_chain);
325 if (bridge->funcs->attach) {
326 ret = bridge->funcs->attach(bridge, flags);
328 goto err_reset_bridge;
331 if (bridge->funcs->atomic_reset) {
332 struct drm_bridge_state *state;
334 state = bridge->funcs->atomic_reset(bridge);
336 ret = PTR_ERR(state);
337 goto err_detach_bridge;
340 drm_atomic_private_obj_init(bridge->dev, &bridge->base,
342 &drm_bridge_priv_state_funcs);
348 if (bridge->funcs->detach)
349 bridge->funcs->detach(bridge);
353 bridge->encoder = NULL;
354 list_del(&bridge->chain_node);
356 DRM_ERROR("failed to attach bridge %pOF to encoder %s: %d\n",
357 bridge->of_node, encoder->name, ret);
361 EXPORT_SYMBOL(drm_bridge_attach);
363 void drm_bridge_detach(struct drm_bridge *bridge)
365 if (WARN_ON(!bridge))
368 if (WARN_ON(!bridge->dev))
371 if (bridge->funcs->atomic_reset)
372 drm_atomic_private_obj_fini(&bridge->base);
374 if (bridge->funcs->detach)
375 bridge->funcs->detach(bridge);
377 list_del(&bridge->chain_node);
382 * DOC: bridge operations
384 * Bridge drivers expose operations through the &drm_bridge_funcs structure.
385 * The DRM internals (atomic and CRTC helpers) use the helpers defined in
386 * drm_bridge.c to call bridge operations. Those operations are divided in
387 * three big categories to support different parts of the bridge usage.
389 * - The encoder-related operations support control of the bridges in the
390 * chain, and are roughly counterparts to the &drm_encoder_helper_funcs
391 * operations. They are used by the legacy CRTC and the atomic modeset
392 * helpers to perform mode validation, fixup and setting, and enable and
393 * disable the bridge automatically.
395 * The enable and disable operations are split in
396 * &drm_bridge_funcs.pre_enable, &drm_bridge_funcs.enable,
397 * &drm_bridge_funcs.disable and &drm_bridge_funcs.post_disable to provide
398 * finer-grained control.
400 * Bridge drivers may implement the legacy version of those operations, or
401 * the atomic version (prefixed with atomic\_), in which case they shall also
402 * implement the atomic state bookkeeping operations
403 * (&drm_bridge_funcs.atomic_duplicate_state,
404 * &drm_bridge_funcs.atomic_destroy_state and &drm_bridge_funcs.reset).
405 * Mixing atomic and non-atomic versions of the operations is not supported.
407 * - The bus format negotiation operations
408 * &drm_bridge_funcs.atomic_get_output_bus_fmts and
409 * &drm_bridge_funcs.atomic_get_input_bus_fmts allow bridge drivers to
410 * negotiate the formats transmitted between bridges in the chain when
411 * multiple formats are supported. Negotiation for formats is performed
412 * transparently for display drivers by the atomic modeset helpers. Only
413 * atomic versions of those operations exist, bridge drivers that need to
414 * implement them shall thus also implement the atomic version of the
415 * encoder-related operations. This feature is not supported by the legacy
418 * - The connector-related operations support implementing a &drm_connector
419 * based on a chain of bridges. DRM bridges traditionally create a
420 * &drm_connector for bridges meant to be used at the end of the chain. This
421 * puts additional burden on bridge drivers, especially for bridges that may
422 * be used in the middle of a chain or at the end of it. Furthermore, it
423 * requires all operations of the &drm_connector to be handled by a single
424 * bridge, which doesn't always match the hardware architecture.
426 * To simplify bridge drivers and make the connector implementation more
427 * flexible, a new model allows bridges to unconditionally skip creation of
428 * &drm_connector and instead expose &drm_bridge_funcs operations to support
429 * an externally-implemented &drm_connector. Those operations are
430 * &drm_bridge_funcs.detect, &drm_bridge_funcs.get_modes,
431 * &drm_bridge_funcs.get_edid, &drm_bridge_funcs.hpd_notify,
432 * &drm_bridge_funcs.hpd_enable and &drm_bridge_funcs.hpd_disable. When
433 * implemented, display drivers shall create a &drm_connector instance for
434 * each chain of bridges, and implement those connector instances based on
435 * the bridge connector operations.
437 * Bridge drivers shall implement the connector-related operations for all
438 * the features that the bridge hardware support. For instance, if a bridge
439 * supports reading EDID, the &drm_bridge_funcs.get_edid shall be
440 * implemented. This however doesn't mean that the DDC lines are wired to the
441 * bridge on a particular platform, as they could also be connected to an I2C
442 * controller of the SoC. Support for the connector-related operations on the
443 * running platform is reported through the &drm_bridge.ops flags. Bridge
444 * drivers shall detect which operations they can support on the platform
445 * (usually this information is provided by ACPI or DT), and set the
446 * &drm_bridge.ops flags for all supported operations. A flag shall only be
447 * set if the corresponding &drm_bridge_funcs operation is implemented, but
448 * an implemented operation doesn't necessarily imply that the corresponding
449 * flag will be set. Display drivers shall use the &drm_bridge.ops flags to
450 * decide which bridge to delegate a connector operation to. This mechanism
451 * allows providing a single static const &drm_bridge_funcs instance in
452 * bridge drivers, improving security by storing function pointers in
455 * In order to ease transition, bridge drivers may support both the old and
456 * new models by making connector creation optional and implementing the
457 * connected-related bridge operations. Connector creation is then controlled
458 * by the flags argument to the drm_bridge_attach() function. Display drivers
459 * that support the new model and create connectors themselves shall set the
460 * %DRM_BRIDGE_ATTACH_NO_CONNECTOR flag, and bridge drivers shall then skip
461 * connector creation. For intermediate bridges in the chain, the flag shall
462 * be passed to the drm_bridge_attach() call for the downstream bridge.
463 * Bridge drivers that implement the new model only shall return an error
464 * from their &drm_bridge_funcs.attach handler when the
465 * %DRM_BRIDGE_ATTACH_NO_CONNECTOR flag is not set. New display drivers
466 * should use the new model, and convert the bridge drivers they use if
467 * needed, in order to gradually transition to the new model.
471 * drm_bridge_chain_mode_valid - validate the mode against all bridges in the
473 * @bridge: bridge control structure
474 * @info: display info against which the mode shall be validated
475 * @mode: desired mode to be validated
477 * Calls &drm_bridge_funcs.mode_valid for all the bridges in the encoder
478 * chain, starting from the first bridge to the last. If at least one bridge
479 * does not accept the mode the function returns the error code.
481 * Note: the bridge passed should be the one closest to the encoder.
484 * MODE_OK on success, drm_mode_status Enum error code on failure
487 drm_bridge_chain_mode_valid(struct drm_bridge *bridge,
488 const struct drm_display_info *info,
489 const struct drm_display_mode *mode)
491 struct drm_encoder *encoder;
496 encoder = bridge->encoder;
497 list_for_each_entry_from(bridge, &encoder->bridge_chain, chain_node) {
498 enum drm_mode_status ret;
500 if (!bridge->funcs->mode_valid)
503 ret = bridge->funcs->mode_valid(bridge, info, mode);
510 EXPORT_SYMBOL(drm_bridge_chain_mode_valid);
513 * drm_bridge_chain_mode_set - set proposed mode for all bridges in the
515 * @bridge: bridge control structure
516 * @mode: desired mode to be set for the encoder chain
517 * @adjusted_mode: updated mode that works for this encoder chain
519 * Calls &drm_bridge_funcs.mode_set op for all the bridges in the
520 * encoder chain, starting from the first bridge to the last.
522 * Note: the bridge passed should be the one closest to the encoder
524 void drm_bridge_chain_mode_set(struct drm_bridge *bridge,
525 const struct drm_display_mode *mode,
526 const struct drm_display_mode *adjusted_mode)
528 struct drm_encoder *encoder;
533 encoder = bridge->encoder;
534 list_for_each_entry_from(bridge, &encoder->bridge_chain, chain_node) {
535 if (bridge->funcs->mode_set)
536 bridge->funcs->mode_set(bridge, mode, adjusted_mode);
539 EXPORT_SYMBOL(drm_bridge_chain_mode_set);
542 * drm_atomic_bridge_chain_disable - disables all bridges in the encoder chain
543 * @bridge: bridge control structure
544 * @old_state: old atomic state
546 * Calls &drm_bridge_funcs.atomic_disable (falls back on
547 * &drm_bridge_funcs.disable) op for all the bridges in the encoder chain,
548 * starting from the last bridge to the first. These are called before calling
549 * &drm_encoder_helper_funcs.atomic_disable
551 * Note: the bridge passed should be the one closest to the encoder
553 void drm_atomic_bridge_chain_disable(struct drm_bridge *bridge,
554 struct drm_atomic_state *old_state)
556 struct drm_encoder *encoder;
557 struct drm_bridge *iter;
562 encoder = bridge->encoder;
563 list_for_each_entry_reverse(iter, &encoder->bridge_chain, chain_node) {
564 if (iter->funcs->atomic_disable) {
565 struct drm_bridge_state *old_bridge_state;
568 drm_atomic_get_old_bridge_state(old_state,
570 if (WARN_ON(!old_bridge_state))
573 iter->funcs->atomic_disable(iter, old_bridge_state);
574 } else if (iter->funcs->disable) {
575 iter->funcs->disable(iter);
582 EXPORT_SYMBOL(drm_atomic_bridge_chain_disable);
584 static void drm_atomic_bridge_call_post_disable(struct drm_bridge *bridge,
585 struct drm_atomic_state *old_state)
587 if (old_state && bridge->funcs->atomic_post_disable) {
588 struct drm_bridge_state *old_bridge_state;
591 drm_atomic_get_old_bridge_state(old_state,
593 if (WARN_ON(!old_bridge_state))
596 bridge->funcs->atomic_post_disable(bridge,
598 } else if (bridge->funcs->post_disable) {
599 bridge->funcs->post_disable(bridge);
604 * drm_atomic_bridge_chain_post_disable - cleans up after disabling all bridges
605 * in the encoder chain
606 * @bridge: bridge control structure
607 * @old_state: old atomic state
609 * Calls &drm_bridge_funcs.atomic_post_disable (falls back on
610 * &drm_bridge_funcs.post_disable) op for all the bridges in the encoder chain,
611 * starting from the first bridge to the last. These are called after completing
612 * &drm_encoder_helper_funcs.atomic_disable
614 * If a bridge sets @pre_enable_prev_first, then the @post_disable for that
615 * bridge will be called before the previous one to reverse the @pre_enable
619 * Bridge A ---> Bridge B ---> Bridge C ---> Bridge D ---> Bridge E
621 * With pre_enable_prev_first flag enable in Bridge B, D, E then the resulting
622 * @post_disable order would be,
623 * Bridge B, Bridge A, Bridge E, Bridge D, Bridge C.
625 * Note: the bridge passed should be the one closest to the encoder
627 void drm_atomic_bridge_chain_post_disable(struct drm_bridge *bridge,
628 struct drm_atomic_state *old_state)
630 struct drm_encoder *encoder;
631 struct drm_bridge *next, *limit;
636 encoder = bridge->encoder;
638 list_for_each_entry_from(bridge, &encoder->bridge_chain, chain_node) {
641 if (!list_is_last(&bridge->chain_node, &encoder->bridge_chain)) {
642 next = list_next_entry(bridge, chain_node);
644 if (next->pre_enable_prev_first) {
645 /* next bridge had requested that prev
646 * was enabled first, so disabled last
650 /* Find the next bridge that has NOT requested
651 * prev to be enabled first / disabled last
653 list_for_each_entry_from(next, &encoder->bridge_chain,
655 if (!next->pre_enable_prev_first) {
656 next = list_prev_entry(next, chain_node);
661 if (list_is_last(&next->chain_node,
662 &encoder->bridge_chain)) {
668 /* Call these bridges in reverse order */
669 list_for_each_entry_from_reverse(next, &encoder->bridge_chain,
674 drm_atomic_bridge_call_post_disable(next,
680 drm_atomic_bridge_call_post_disable(bridge, old_state);
683 /* Jump all bridges that we have already post_disabled */
687 EXPORT_SYMBOL(drm_atomic_bridge_chain_post_disable);
689 static void drm_atomic_bridge_call_pre_enable(struct drm_bridge *bridge,
690 struct drm_atomic_state *old_state)
692 if (old_state && bridge->funcs->atomic_pre_enable) {
693 struct drm_bridge_state *old_bridge_state;
696 drm_atomic_get_old_bridge_state(old_state,
698 if (WARN_ON(!old_bridge_state))
701 bridge->funcs->atomic_pre_enable(bridge, old_bridge_state);
702 } else if (bridge->funcs->pre_enable) {
703 bridge->funcs->pre_enable(bridge);
708 * drm_atomic_bridge_chain_pre_enable - prepares for enabling all bridges in
710 * @bridge: bridge control structure
711 * @old_state: old atomic state
713 * Calls &drm_bridge_funcs.atomic_pre_enable (falls back on
714 * &drm_bridge_funcs.pre_enable) op for all the bridges in the encoder chain,
715 * starting from the last bridge to the first. These are called before calling
716 * &drm_encoder_helper_funcs.atomic_enable
718 * If a bridge sets @pre_enable_prev_first, then the pre_enable for the
719 * prev bridge will be called before pre_enable of this bridge.
722 * Bridge A ---> Bridge B ---> Bridge C ---> Bridge D ---> Bridge E
724 * With pre_enable_prev_first flag enable in Bridge B, D, E then the resulting
725 * @pre_enable order would be,
726 * Bridge C, Bridge D, Bridge E, Bridge A, Bridge B.
728 * Note: the bridge passed should be the one closest to the encoder
730 void drm_atomic_bridge_chain_pre_enable(struct drm_bridge *bridge,
731 struct drm_atomic_state *old_state)
733 struct drm_encoder *encoder;
734 struct drm_bridge *iter, *next, *limit;
739 encoder = bridge->encoder;
741 list_for_each_entry_reverse(iter, &encoder->bridge_chain, chain_node) {
742 if (iter->pre_enable_prev_first) {
745 list_for_each_entry_from_reverse(next,
746 &encoder->bridge_chain,
751 if (!next->pre_enable_prev_first) {
752 /* Found first bridge that does NOT
753 * request prev to be enabled first
760 list_for_each_entry_from(next, &encoder->bridge_chain, chain_node) {
761 /* Call requested prev bridge pre_enable
765 /* At the first bridge to request prev
766 * bridges called first.
770 drm_atomic_bridge_call_pre_enable(next, old_state);
774 drm_atomic_bridge_call_pre_enable(iter, old_state);
776 if (iter->pre_enable_prev_first)
777 /* Jump all bridges that we have already pre_enabled */
784 EXPORT_SYMBOL(drm_atomic_bridge_chain_pre_enable);
787 * drm_atomic_bridge_chain_enable - enables all bridges in the encoder chain
788 * @bridge: bridge control structure
789 * @old_state: old atomic state
791 * Calls &drm_bridge_funcs.atomic_enable (falls back on
792 * &drm_bridge_funcs.enable) op for all the bridges in the encoder chain,
793 * starting from the first bridge to the last. These are called after completing
794 * &drm_encoder_helper_funcs.atomic_enable
796 * Note: the bridge passed should be the one closest to the encoder
798 void drm_atomic_bridge_chain_enable(struct drm_bridge *bridge,
799 struct drm_atomic_state *old_state)
801 struct drm_encoder *encoder;
806 encoder = bridge->encoder;
807 list_for_each_entry_from(bridge, &encoder->bridge_chain, chain_node) {
808 if (bridge->funcs->atomic_enable) {
809 struct drm_bridge_state *old_bridge_state;
812 drm_atomic_get_old_bridge_state(old_state,
814 if (WARN_ON(!old_bridge_state))
817 bridge->funcs->atomic_enable(bridge, old_bridge_state);
818 } else if (bridge->funcs->enable) {
819 bridge->funcs->enable(bridge);
823 EXPORT_SYMBOL(drm_atomic_bridge_chain_enable);
825 static int drm_atomic_bridge_check(struct drm_bridge *bridge,
826 struct drm_crtc_state *crtc_state,
827 struct drm_connector_state *conn_state)
829 if (bridge->funcs->atomic_check) {
830 struct drm_bridge_state *bridge_state;
833 bridge_state = drm_atomic_get_new_bridge_state(crtc_state->state,
835 if (WARN_ON(!bridge_state))
838 ret = bridge->funcs->atomic_check(bridge, bridge_state,
839 crtc_state, conn_state);
842 } else if (bridge->funcs->mode_fixup) {
843 if (!bridge->funcs->mode_fixup(bridge, &crtc_state->mode,
844 &crtc_state->adjusted_mode))
851 static int select_bus_fmt_recursive(struct drm_bridge *first_bridge,
852 struct drm_bridge *cur_bridge,
853 struct drm_crtc_state *crtc_state,
854 struct drm_connector_state *conn_state,
857 unsigned int i, num_in_bus_fmts = 0;
858 struct drm_bridge_state *cur_state;
859 struct drm_bridge *prev_bridge;
863 prev_bridge = drm_bridge_get_prev_bridge(cur_bridge);
864 cur_state = drm_atomic_get_new_bridge_state(crtc_state->state,
868 * If bus format negotiation is not supported by this bridge, let's
869 * pass MEDIA_BUS_FMT_FIXED to the previous bridge in the chain and
870 * hope that it can handle this situation gracefully (by providing
871 * appropriate default values).
873 if (!cur_bridge->funcs->atomic_get_input_bus_fmts) {
874 if (cur_bridge != first_bridge) {
875 ret = select_bus_fmt_recursive(first_bridge,
876 prev_bridge, crtc_state,
878 MEDIA_BUS_FMT_FIXED);
884 * Driver does not implement the atomic state hooks, but that's
885 * fine, as long as it does not access the bridge state.
888 cur_state->input_bus_cfg.format = MEDIA_BUS_FMT_FIXED;
889 cur_state->output_bus_cfg.format = out_bus_fmt;
896 * If the driver implements ->atomic_get_input_bus_fmts() it
897 * should also implement the atomic state hooks.
899 if (WARN_ON(!cur_state))
902 in_bus_fmts = cur_bridge->funcs->atomic_get_input_bus_fmts(cur_bridge,
908 if (!num_in_bus_fmts)
910 else if (!in_bus_fmts)
913 if (first_bridge == cur_bridge) {
914 cur_state->input_bus_cfg.format = in_bus_fmts[0];
915 cur_state->output_bus_cfg.format = out_bus_fmt;
920 for (i = 0; i < num_in_bus_fmts; i++) {
921 ret = select_bus_fmt_recursive(first_bridge, prev_bridge,
922 crtc_state, conn_state,
924 if (ret != -ENOTSUPP)
929 cur_state->input_bus_cfg.format = in_bus_fmts[i];
930 cur_state->output_bus_cfg.format = out_bus_fmt;
938 * This function is called by &drm_atomic_bridge_chain_check() just before
939 * calling &drm_bridge_funcs.atomic_check() on all elements of the chain.
940 * It performs bus format negotiation between bridge elements. The negotiation
941 * happens in reverse order, starting from the last element in the chain up to
944 * Negotiation starts by retrieving supported output bus formats on the last
945 * bridge element and testing them one by one. The test is recursive, meaning
946 * that for each tested output format, the whole chain will be walked backward,
947 * and each element will have to choose an input bus format that can be
948 * transcoded to the requested output format. When a bridge element does not
949 * support transcoding into a specific output format -ENOTSUPP is returned and
950 * the next bridge element will have to try a different format. If none of the
951 * combinations worked, -ENOTSUPP is returned and the atomic modeset will fail.
953 * This implementation is relying on
954 * &drm_bridge_funcs.atomic_get_output_bus_fmts() and
955 * &drm_bridge_funcs.atomic_get_input_bus_fmts() to gather supported
956 * input/output formats.
958 * When &drm_bridge_funcs.atomic_get_output_bus_fmts() is not implemented by
959 * the last element of the chain, &drm_atomic_bridge_chain_select_bus_fmts()
960 * tries a single format: &drm_connector.display_info.bus_formats[0] if
961 * available, MEDIA_BUS_FMT_FIXED otherwise.
963 * When &drm_bridge_funcs.atomic_get_input_bus_fmts() is not implemented,
964 * &drm_atomic_bridge_chain_select_bus_fmts() skips the negotiation on the
965 * bridge element that lacks this hook and asks the previous element in the
966 * chain to try MEDIA_BUS_FMT_FIXED. It's up to bridge drivers to decide what
967 * to do in that case (fail if they want to enforce bus format negotiation, or
968 * provide a reasonable default if they need to support pipelines where not
969 * all elements support bus format negotiation).
972 drm_atomic_bridge_chain_select_bus_fmts(struct drm_bridge *bridge,
973 struct drm_crtc_state *crtc_state,
974 struct drm_connector_state *conn_state)
976 struct drm_connector *conn = conn_state->connector;
977 struct drm_encoder *encoder = bridge->encoder;
978 struct drm_bridge_state *last_bridge_state;
979 unsigned int i, num_out_bus_fmts = 0;
980 struct drm_bridge *last_bridge;
984 last_bridge = list_last_entry(&encoder->bridge_chain,
985 struct drm_bridge, chain_node);
986 last_bridge_state = drm_atomic_get_new_bridge_state(crtc_state->state,
989 if (last_bridge->funcs->atomic_get_output_bus_fmts) {
990 const struct drm_bridge_funcs *funcs = last_bridge->funcs;
993 * If the driver implements ->atomic_get_output_bus_fmts() it
994 * should also implement the atomic state hooks.
996 if (WARN_ON(!last_bridge_state))
999 out_bus_fmts = funcs->atomic_get_output_bus_fmts(last_bridge,
1004 if (!num_out_bus_fmts)
1006 else if (!out_bus_fmts)
1009 num_out_bus_fmts = 1;
1010 out_bus_fmts = kmalloc(sizeof(*out_bus_fmts), GFP_KERNEL);
1014 if (conn->display_info.num_bus_formats &&
1015 conn->display_info.bus_formats)
1016 out_bus_fmts[0] = conn->display_info.bus_formats[0];
1018 out_bus_fmts[0] = MEDIA_BUS_FMT_FIXED;
1021 for (i = 0; i < num_out_bus_fmts; i++) {
1022 ret = select_bus_fmt_recursive(bridge, last_bridge, crtc_state,
1023 conn_state, out_bus_fmts[i]);
1024 if (ret != -ENOTSUPP)
1028 kfree(out_bus_fmts);
1034 drm_atomic_bridge_propagate_bus_flags(struct drm_bridge *bridge,
1035 struct drm_connector *conn,
1036 struct drm_atomic_state *state)
1038 struct drm_bridge_state *bridge_state, *next_bridge_state;
1039 struct drm_bridge *next_bridge;
1040 u32 output_flags = 0;
1042 bridge_state = drm_atomic_get_new_bridge_state(state, bridge);
1044 /* No bridge state attached to this bridge => nothing to propagate. */
1048 next_bridge = drm_bridge_get_next_bridge(bridge);
1051 * Let's try to apply the most common case here, that is, propagate
1052 * display_info flags for the last bridge, and propagate the input
1053 * flags of the next bridge element to the output end of the current
1054 * bridge when the bridge is not the last one.
1055 * There are exceptions to this rule, like when signal inversion is
1056 * happening at the board level, but that's something drivers can deal
1057 * with from their &drm_bridge_funcs.atomic_check() implementation by
1058 * simply overriding the flags value we've set here.
1061 output_flags = conn->display_info.bus_flags;
1063 next_bridge_state = drm_atomic_get_new_bridge_state(state,
1066 * No bridge state attached to the next bridge, just leave the
1069 if (next_bridge_state)
1070 output_flags = next_bridge_state->input_bus_cfg.flags;
1073 bridge_state->output_bus_cfg.flags = output_flags;
1076 * Propagate the output flags to the input end of the bridge. Again, it's
1077 * not necessarily what all bridges want, but that's what most of them
1078 * do, and by doing that by default we avoid forcing drivers to
1079 * duplicate the "dummy propagation" logic.
1081 bridge_state->input_bus_cfg.flags = output_flags;
1085 * drm_atomic_bridge_chain_check() - Do an atomic check on the bridge chain
1086 * @bridge: bridge control structure
1087 * @crtc_state: new CRTC state
1088 * @conn_state: new connector state
1090 * First trigger a bus format negotiation before calling
1091 * &drm_bridge_funcs.atomic_check() (falls back on
1092 * &drm_bridge_funcs.mode_fixup()) op for all the bridges in the encoder chain,
1093 * starting from the last bridge to the first. These are called before calling
1094 * &drm_encoder_helper_funcs.atomic_check()
1097 * 0 on success, a negative error code on failure
1099 int drm_atomic_bridge_chain_check(struct drm_bridge *bridge,
1100 struct drm_crtc_state *crtc_state,
1101 struct drm_connector_state *conn_state)
1103 struct drm_connector *conn = conn_state->connector;
1104 struct drm_encoder *encoder;
1105 struct drm_bridge *iter;
1111 ret = drm_atomic_bridge_chain_select_bus_fmts(bridge, crtc_state,
1116 encoder = bridge->encoder;
1117 list_for_each_entry_reverse(iter, &encoder->bridge_chain, chain_node) {
1121 * Bus flags are propagated by default. If a bridge needs to
1122 * tweak the input bus flags for any reason, it should happen
1123 * in its &drm_bridge_funcs.atomic_check() implementation such
1124 * that preceding bridges in the chain can propagate the new
1127 drm_atomic_bridge_propagate_bus_flags(iter, conn,
1130 ret = drm_atomic_bridge_check(iter, crtc_state, conn_state);
1140 EXPORT_SYMBOL(drm_atomic_bridge_chain_check);
1143 * drm_bridge_detect - check if anything is attached to the bridge output
1144 * @bridge: bridge control structure
1146 * If the bridge supports output detection, as reported by the
1147 * DRM_BRIDGE_OP_DETECT bridge ops flag, call &drm_bridge_funcs.detect for the
1148 * bridge and return the connection status. Otherwise return
1149 * connector_status_unknown.
1152 * The detection status on success, or connector_status_unknown if the bridge
1153 * doesn't support output detection.
1155 enum drm_connector_status drm_bridge_detect(struct drm_bridge *bridge)
1157 if (!(bridge->ops & DRM_BRIDGE_OP_DETECT))
1158 return connector_status_unknown;
1160 return bridge->funcs->detect(bridge);
1162 EXPORT_SYMBOL_GPL(drm_bridge_detect);
1165 * drm_bridge_get_modes - fill all modes currently valid for the sink into the
1167 * @bridge: bridge control structure
1168 * @connector: the connector to fill with modes
1170 * If the bridge supports output modes retrieval, as reported by the
1171 * DRM_BRIDGE_OP_MODES bridge ops flag, call &drm_bridge_funcs.get_modes to
1172 * fill the connector with all valid modes and return the number of modes
1173 * added. Otherwise return 0.
1176 * The number of modes added to the connector.
1178 int drm_bridge_get_modes(struct drm_bridge *bridge,
1179 struct drm_connector *connector)
1181 if (!(bridge->ops & DRM_BRIDGE_OP_MODES))
1184 return bridge->funcs->get_modes(bridge, connector);
1186 EXPORT_SYMBOL_GPL(drm_bridge_get_modes);
1189 * drm_bridge_edid_read - read the EDID data of the connected display
1190 * @bridge: bridge control structure
1191 * @connector: the connector to read EDID for
1193 * If the bridge supports output EDID retrieval, as reported by the
1194 * DRM_BRIDGE_OP_EDID bridge ops flag, call &drm_bridge_funcs.edid_read to get
1195 * the EDID and return it. Otherwise return NULL.
1198 * The retrieved EDID on success, or NULL otherwise.
1200 const struct drm_edid *drm_bridge_edid_read(struct drm_bridge *bridge,
1201 struct drm_connector *connector)
1203 if (!(bridge->ops & DRM_BRIDGE_OP_EDID))
1206 return bridge->funcs->edid_read(bridge, connector);
1208 EXPORT_SYMBOL_GPL(drm_bridge_edid_read);
1211 * drm_bridge_hpd_enable - enable hot plug detection for the bridge
1212 * @bridge: bridge control structure
1213 * @cb: hot-plug detection callback
1214 * @data: data to be passed to the hot-plug detection callback
1216 * Call &drm_bridge_funcs.hpd_enable if implemented and register the given @cb
1217 * and @data as hot plug notification callback. From now on the @cb will be
1218 * called with @data when an output status change is detected by the bridge,
1219 * until hot plug notification gets disabled with drm_bridge_hpd_disable().
1221 * Hot plug detection is supported only if the DRM_BRIDGE_OP_HPD flag is set in
1222 * bridge->ops. This function shall not be called when the flag is not set.
1224 * Only one hot plug detection callback can be registered at a time, it is an
1225 * error to call this function when hot plug detection is already enabled for
1228 void drm_bridge_hpd_enable(struct drm_bridge *bridge,
1229 void (*cb)(void *data,
1230 enum drm_connector_status status),
1233 if (!(bridge->ops & DRM_BRIDGE_OP_HPD))
1236 mutex_lock(&bridge->hpd_mutex);
1238 if (WARN(bridge->hpd_cb, "Hot plug detection already enabled\n"))
1241 bridge->hpd_cb = cb;
1242 bridge->hpd_data = data;
1244 if (bridge->funcs->hpd_enable)
1245 bridge->funcs->hpd_enable(bridge);
1248 mutex_unlock(&bridge->hpd_mutex);
1250 EXPORT_SYMBOL_GPL(drm_bridge_hpd_enable);
1253 * drm_bridge_hpd_disable - disable hot plug detection for the bridge
1254 * @bridge: bridge control structure
1256 * Call &drm_bridge_funcs.hpd_disable if implemented and unregister the hot
1257 * plug detection callback previously registered with drm_bridge_hpd_enable().
1258 * Once this function returns the callback will not be called by the bridge
1259 * when an output status change occurs.
1261 * Hot plug detection is supported only if the DRM_BRIDGE_OP_HPD flag is set in
1262 * bridge->ops. This function shall not be called when the flag is not set.
1264 void drm_bridge_hpd_disable(struct drm_bridge *bridge)
1266 if (!(bridge->ops & DRM_BRIDGE_OP_HPD))
1269 mutex_lock(&bridge->hpd_mutex);
1270 if (bridge->funcs->hpd_disable)
1271 bridge->funcs->hpd_disable(bridge);
1273 bridge->hpd_cb = NULL;
1274 bridge->hpd_data = NULL;
1275 mutex_unlock(&bridge->hpd_mutex);
1277 EXPORT_SYMBOL_GPL(drm_bridge_hpd_disable);
1280 * drm_bridge_hpd_notify - notify hot plug detection events
1281 * @bridge: bridge control structure
1282 * @status: output connection status
1284 * Bridge drivers shall call this function to report hot plug events when they
1285 * detect a change in the output status, when hot plug detection has been
1286 * enabled by drm_bridge_hpd_enable().
1288 * This function shall be called in a context that can sleep.
1290 void drm_bridge_hpd_notify(struct drm_bridge *bridge,
1291 enum drm_connector_status status)
1293 mutex_lock(&bridge->hpd_mutex);
1295 bridge->hpd_cb(bridge->hpd_data, status);
1296 mutex_unlock(&bridge->hpd_mutex);
1298 EXPORT_SYMBOL_GPL(drm_bridge_hpd_notify);
1302 * of_drm_find_bridge - find the bridge corresponding to the device node in
1303 * the global bridge list
1308 * drm_bridge control struct on success, NULL on failure
1310 struct drm_bridge *of_drm_find_bridge(struct device_node *np)
1312 struct drm_bridge *bridge;
1314 mutex_lock(&bridge_lock);
1316 list_for_each_entry(bridge, &bridge_list, list) {
1317 if (bridge->of_node == np) {
1318 mutex_unlock(&bridge_lock);
1323 mutex_unlock(&bridge_lock);
1326 EXPORT_SYMBOL(of_drm_find_bridge);
1330 MODULE_DESCRIPTION("DRM bridge infrastructure");
1331 MODULE_LICENSE("GPL and additional rights");