1354d7675SEmmanuel Vadot# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 2354d7675SEmmanuel Vadot%YAML 1.2 3354d7675SEmmanuel Vadot--- 4354d7675SEmmanuel Vadot$id: http://devicetree.org/schemas/display/dp-aux-bus.yaml# 5354d7675SEmmanuel Vadot$schema: http://devicetree.org/meta-schemas/core.yaml# 6354d7675SEmmanuel Vadot 7354d7675SEmmanuel Vadottitle: DisplayPort AUX bus 8354d7675SEmmanuel Vadot 9354d7675SEmmanuel Vadotmaintainers: 10354d7675SEmmanuel Vadot - Douglas Anderson <dianders@chromium.org> 11354d7675SEmmanuel Vadot 12354d7675SEmmanuel Vadotdescription: 13354d7675SEmmanuel Vadot DisplayPort controllers provide a control channel to the sinks that 14354d7675SEmmanuel Vadot are hooked up to them. This is the DP AUX bus. Over the DP AUX bus 15354d7675SEmmanuel Vadot we can query properties about a sink and also configure it. In 16354d7675SEmmanuel Vadot particular, DP sinks support DDC over DP AUX which allows tunneling 17354d7675SEmmanuel Vadot a standard I2C DDC connection over the AUX channel. 18354d7675SEmmanuel Vadot 19354d7675SEmmanuel Vadot To model this relationship, DP sinks should be placed as children 20354d7675SEmmanuel Vadot of the DP controller under the "aux-bus" node. 21354d7675SEmmanuel Vadot 22354d7675SEmmanuel Vadot At the moment, this binding only handles the eDP case. It is 23354d7675SEmmanuel Vadot possible it will be extended in the future to handle the DP case. 24354d7675SEmmanuel Vadot For DP, presumably a connector would be listed under the DP AUX 25354d7675SEmmanuel Vadot bus instead of a panel. 26354d7675SEmmanuel Vadot 27354d7675SEmmanuel Vadotproperties: 28354d7675SEmmanuel Vadot $nodename: 29*fac71e4eSEmmanuel Vadot const: aux-bus 30354d7675SEmmanuel Vadot 31354d7675SEmmanuel Vadot panel: 32354d7675SEmmanuel Vadot $ref: panel/panel-common.yaml# 33354d7675SEmmanuel Vadot 34354d7675SEmmanuel VadotadditionalProperties: false 35354d7675SEmmanuel Vadot 36354d7675SEmmanuel Vadotrequired: 37354d7675SEmmanuel Vadot - panel 38