The Mitsubishi AA140XD12 Device Tree Binding was requiring a data-mapping property value which was set to another value in the existing Device Trees. Fix this.
Cc: [email protected] Cc: Laurent Pinchart <[email protected]> Cc: Sam Ravnborg <[email protected]> Cc: Thierry Reding <[email protected]> Signed-off-by: Maxime Ripard <[email protected]> --- .../bindings/display/panel/mitsubishi,aa104xd12.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/devicetree/bindings/display/panel/mitsubishi,aa104xd12.yaml b/Documentation/devicetree/bindings/display/panel/mitsubishi,aa104xd12.yaml index b595edd58bbb..2d1c85e377cd 100644 --- a/Documentation/devicetree/bindings/display/panel/mitsubishi,aa104xd12.yaml +++ b/Documentation/devicetree/bindings/display/panel/mitsubishi,aa104xd12.yaml @@ -20,7 +20,7 @@ properties: - {} # panel-lvds, but not listed here to avoid false select data-mapping: - const: jeida-24 + const: jeida-18 width-mm: const: 210 @@ -45,7 +45,7 @@ examples: width-mm = <210>; height-mm = <158>; - data-mapping = "jeida-24"; + data-mapping = "jeida-18"; panel-timing { /* 1024x768 @65Hz */ -- 2.31.1
