1*354d7675SEmmanuel Vadot# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 2*354d7675SEmmanuel Vadot%YAML 1.2 3*354d7675SEmmanuel Vadot--- 4*354d7675SEmmanuel Vadot$id: http://devicetree.org/schemas/display/dp-aux-bus.yaml# 5*354d7675SEmmanuel Vadot$schema: http://devicetree.org/meta-schemas/core.yaml# 6*354d7675SEmmanuel Vadot 7*354d7675SEmmanuel Vadottitle: DisplayPort AUX bus 8*354d7675SEmmanuel Vadot 9*354d7675SEmmanuel Vadotmaintainers: 10*354d7675SEmmanuel Vadot - Douglas Anderson <dianders@chromium.org> 11*354d7675SEmmanuel Vadot 12*354d7675SEmmanuel Vadotdescription: 13*354d7675SEmmanuel Vadot DisplayPort controllers provide a control channel to the sinks that 14*354d7675SEmmanuel Vadot are hooked up to them. This is the DP AUX bus. Over the DP AUX bus 15*354d7675SEmmanuel Vadot we can query properties about a sink and also configure it. In 16*354d7675SEmmanuel Vadot particular, DP sinks support DDC over DP AUX which allows tunneling 17*354d7675SEmmanuel Vadot a standard I2C DDC connection over the AUX channel. 18*354d7675SEmmanuel Vadot 19*354d7675SEmmanuel Vadot To model this relationship, DP sinks should be placed as children 20*354d7675SEmmanuel Vadot of the DP controller under the "aux-bus" node. 21*354d7675SEmmanuel Vadot 22*354d7675SEmmanuel Vadot At the moment, this binding only handles the eDP case. It is 23*354d7675SEmmanuel Vadot possible it will be extended in the future to handle the DP case. 24*354d7675SEmmanuel Vadot For DP, presumably a connector would be listed under the DP AUX 25*354d7675SEmmanuel Vadot bus instead of a panel. 26*354d7675SEmmanuel Vadot 27*354d7675SEmmanuel Vadotproperties: 28*354d7675SEmmanuel Vadot $nodename: 29*354d7675SEmmanuel Vadot const: "aux-bus" 30*354d7675SEmmanuel Vadot 31*354d7675SEmmanuel Vadot panel: 32*354d7675SEmmanuel Vadot $ref: panel/panel-common.yaml# 33*354d7675SEmmanuel Vadot 34*354d7675SEmmanuel VadotadditionalProperties: false 35*354d7675SEmmanuel Vadot 36*354d7675SEmmanuel Vadotrequired: 37*354d7675SEmmanuel Vadot - panel 38