Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Frank Li" <Frank.Li@nxp.com>
Cc: krzk+dt@kernel.org, Frank.Li@kernel.org, imx@lists.linux.dev,
	devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 2/4] ARM: dts: imx: add ti,deskew = <0> for ti,tfp410
Date: Wed, 13 May 2026 00:38:35 +0000	[thread overview]
Message-ID: <20260513003835.A8C00C2BCB0@smtp.kernel.org> (raw)
In-Reply-To: <20260511-b4-imx25_dts_simple_warning-v1-2-01b855a5ce25@nxp.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Hardcoding incorrect hardware description based on a software driver bug
--

commit e68637a2ada078494e7ee776597edfdccd03a72c
Author: Frank Li <Frank.Li@nxp.com>

ARM: dts: imx: add ti,deskew = <0> for ti,tfp410

This commit adds the required ti,deskew property to ti,tfp410 nodes
to fix dt_binding_check warnings. The value 0 is chosen based on the
default value found in the driver.

>     Add required proprety ti,deskew for ti,tfp410, which have not defined

This isn't a bug, but there's a typo (proprety) in the commit message.

>     default value in yaml. 0 is default value according to
>     drivers/gpu/drm/bridge/ti-tfp410.c.

Does this accurately describe the hardware, or is it mirroring a driver
bug?

Device Tree properties are intended to describe the physical hardware
configuration, rather than reflecting software driver fallbacks.

> diff --git a/arch/arm/boot/dts/nxp/imx/imx51-babbage.dts b/arch/arm/boot/dts/nxp/imx/imx51-babbage.dts
> index b17264e06e691..a02e9cd0b3fa0 100644
> --- a/arch/arm/boot/dts/nxp/imx/imx51-babbage.dts
> +++ b/arch/arm/boot/dts/nxp/imx/imx51-babbage.dts
> @@ -126,6 +126,7 @@ dvi_connector_in: endpoint {
>  
>  	dvi-encoder {
>  		compatible = "ti,tfp410";
> +		ti,deskew = <0>;

The driver fallback of 0 appears to be a bug introduced in 2020 by commit
"drm/bridge: tfp410: fix de-skew value retrieval from DT". That commit
changed the ti,deskew scale from -4..3 to 0..7 but did not update the
fallback value from 0 to 4.

As a result, missing properties inadvertently apply maximum negative skew
instead of neutral skew.

By copying this fallback into the device trees, does this permanently
enshrine maximum negative skew into the hardware description? 

If the driver is later fixed to use the correct neutral default, these
boards will still apply maximum negative skew.

Should the physical board schematics be consulted to determine the actual
DK[3:1] pin strapping instead? If the pins are strapped for neutral skew,
the value should likely be <4>.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260511-b4-imx25_dts_simple_warning-v1-0-01b855a5ce25@nxp.com?part=2

  reply	other threads:[~2026-05-13  0:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11 21:04 [PATCH 0/4] ARM: dts: DTB_CHECK warning cleanup Frank Li
2026-05-11 21:04 ` [PATCH 1/4] ARM: dts: imx6qdl-sabrelite: add mdio phy address 0 Frank Li
2026-05-11 22:15   ` Andrew Lunn
2026-05-12  7:52     ` Francesco Dolcini
2026-05-12 12:23     ` Fabio Estevam
2026-05-12 13:43       ` Fabio Estevam
2026-05-12 14:26     ` Frank Li
2026-05-12  7:51   ` Francesco Dolcini
2026-05-13  0:26   ` sashiko-bot
2026-05-11 21:04 ` [PATCH 2/4] ARM: dts: imx: add ti,deskew = <0> for ti,tfp410 Frank Li
2026-05-13  0:38   ` sashiko-bot [this message]
2026-05-11 21:04 ` [PATCH 3/4] ARM: dts: imx53-qsb: add dvdd and avdd supply for panel sii,43wvf1g Frank Li
2026-05-11 21:04 ` [PATCH 4/4] ARM: dts: imx53-ppd: add '#phy-cells' for usb-nop-xceiv Frank Li

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260513003835.A8C00C2BCB0@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=imx@lists.linux.dev \
    --cc=krzk+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox