On Fri, May 17, 2019 at 11:08:45AM +0200, Maxime Ripard wrote: > > > > So for all current practical purposes, we can assume the Teres-I panel > > to be powered properly and providing valid EDID; nothing to worry about > > in software. > > You're creating a generic binding for all the users of that bridge, > while considering only the specific case of the Teres-I. All I'm saying is that _this_ usage is also valid. Nothing keeps other users from defining the output panel; on the contrary: the driver at hand already considers an _optional_ panel and handles it, conditionally. So driver and binding spec are 100% in sync here. This is much more straightforward than requiring an output and making up some dummy code and params because it cannot reasonably be handled. (Remember, if there is an output, the driver will make calls to the "attached device" driver.) Torsten
