make dtbs_check:
arch/arm64/boot/dts/qcom/sdm850-lenovo-yoga-c630.dt.yaml: bridge@2c: reg:0:0: 45 was expected
According to the datasheet, the I2C address can be either 0x2c or 0x2d, depending on the ADDR control input.
Fixes: e3896e6dddf0b821 ("dt-bindings: drm/bridge: Document sn65dsi86 bridge bindings") Signed-off-by: Geert Uytterhoeven geert+renesas@glider.be --- Also seen with the in-flight Falcon DSI display output patch:
arch/arm64/boot/dts/renesas/r8a779a0-falcon.dt.yaml: sn65dsi86@2c: reg:0:0: 45 was expected --- .../devicetree/bindings/display/bridge/ti,sn65dsi86.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.yaml b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.yaml index 1c2daf7c24cc0417..911564468c5e0f86 100644 --- a/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.yaml +++ b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.yaml @@ -18,7 +18,7 @@ properties: const: ti,sn65dsi86
reg: - const: 0x2d + enum: [ 0x2c, 0x2d ]
enable-gpios: maxItems: 1
On Fri, Sep 24, 2021 at 2:35 PM Geert Uytterhoeven geert+renesas@glider.be wrote:
make dtbs_check:
arch/arm64/boot/dts/qcom/sdm850-lenovo-yoga-c630.dt.yaml: bridge@2c: reg:0:0: 45 was expectedAccording to the datasheet, the I2C address can be either 0x2c or 0x2d, depending on the ADDR control input.
Fixes: e3896e6dddf0b821 ("dt-bindings: drm/bridge: Document sn65dsi86 bridge bindings") Signed-off-by: Geert Uytterhoeven geert+renesas@glider.be
Also seen with the in-flight Falcon DSI display output patch:
arch/arm64/boot/dts/renesas/r8a779a0-falcon.dt.yaml: sn65dsi86@2c: reg:0:0: 45 was expected
.../devicetree/bindings/display/bridge/ti,sn65dsi86.yaml | 2 +-
And the email address of this file's maintainer bounces.
Gr{oetje,eeting}s,
Geert
On 24/09/2021 13:35, Geert Uytterhoeven wrote:
make dtbs_check:
arch/arm64/boot/dts/qcom/sdm850-lenovo-yoga-c630.dt.yaml: bridge@2c: reg:0:0: 45 was expectedAccording to the datasheet, the I2C address can be either 0x2c or 0x2d, depending on the ADDR control input.
Fixes: e3896e6dddf0b821 ("dt-bindings: drm/bridge: Document sn65dsi86 bridge bindings") Signed-off-by: Geert Uytterhoeven geert+renesas@glider.be
Also seen with the in-flight Falcon DSI display output patch:
And having been running dtbs_check today on this branch I was going to tackle this same issue ...
But you've beaten me to it ;-)
Reviewed-by: Kieran Bingham kieran.bingham@ideasonboard.com
arch/arm64/boot/dts/renesas/r8a779a0-falcon.dt.yaml: sn65dsi86@2c: reg:0:0: 45 was expected
.../devicetree/bindings/display/bridge/ti,sn65dsi86.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.yaml b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.yaml index 1c2daf7c24cc0417..911564468c5e0f86 100644 --- a/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.yaml +++ b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.yaml @@ -18,7 +18,7 @@ properties: const: ti,sn65dsi86
reg:
- const: 0x2d
enum: [ 0x2c, 0x2d ]
enable-gpios: maxItems: 1
On Fri, 24 Sep 2021 14:35:12 +0200, Geert Uytterhoeven wrote:
make dtbs_check:
arch/arm64/boot/dts/qcom/sdm850-lenovo-yoga-c630.dt.yaml: bridge@2c: reg:0:0: 45 was expectedAccording to the datasheet, the I2C address can be either 0x2c or 0x2d, depending on the ADDR control input.
Fixes: e3896e6dddf0b821 ("dt-bindings: drm/bridge: Document sn65dsi86 bridge bindings") Signed-off-by: Geert Uytterhoeven geert+renesas@glider.be
Also seen with the in-flight Falcon DSI display output patch:
arch/arm64/boot/dts/renesas/r8a779a0-falcon.dt.yaml: sn65dsi86@2c: reg:0:0: 45 was expected
.../devicetree/bindings/display/bridge/ti,sn65dsi86.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Applied, thanks!
dri-devel@lists.freedesktop.org
-
Geert Uytterhoeven -
Geert Uytterhoeven -
Kieran Bingham -
Rob Herring