Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Boerge Struempfel" <bstruempfel@data-modul.com>
Cc: krzk+dt@kernel.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: display/bridge: lt9211: Add drive-strength-microamp property
Date: Thu, 14 May 2026 05:26:03 +0000	[thread overview]
Message-ID: <20260514052603.BE46FC2BCC6@smtp.kernel.org> (raw)
In-Reply-To: <20260513133127.376458-2-bstruempfel@data-modul.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] The values for `drive-strength-microamp` are scaled incorrectly by a factor of 100, violating the standard device tree unit suffix.
--

commit ab265d46e886455894986f313701d72a9407a58e
Author: Boerge Struempfel <bstruempfel@data-modul.com>

dt-bindings: display/bridge: lt9211: Add drive-strength-microamp property

This commit adds the drive-strength-microamp property to configure the
LT9211 LVDS TX output driver current. It specifies sixteen discrete levels
ranging from 12 to 36.

> diff --git a/Documentation/devicetree/bindings/display/bridge/lontium,lt9211.yaml b/Documentation/devicetree/bindings/display/bridge/lontium,lt9211.yaml
> --- a/Documentation/devicetree/bindings/display/bridge/lontium,lt9211.yaml
> +++ b/Documentation/devicetree/bindings/display/bridge/lontium,lt9211.yaml
[ ... ]
> +  drive-strength-microamp:
> +    description:
> +      LVDS TX output driver current. Sixteen discrete levels are supported,
> +      corresponding to the following nominal values in microamps.
> +    enum: [12, 14, 16, 17, 19, 20, 22, 23, 25, 27, 28, 30, 31, 33, 34, 36]

Are these values scaled incorrectly for a property ending in -microamp?

Properties with the -microamp suffix typically require values in true
microamperes. A standard LVDS driver requires differential currents in the
milliamp range, typically 1.25 mA to 3.59 mA, to generate a standard 350 mV
swing over a 100-ohm termination.

Values from 12 to 36 microamps appear to be physically insufficient for LVDS
signaling.

If the actual intended currents are 1.25 mA to 3.59 mA, shouldn't the enum
values be 1250, 1406, 1562, up to 3594 to accurately reflect true
microamperes?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260513133127.376458-1-bstruempfel@data-modul.com?part=1

  parent reply	other threads:[~2026-05-14  5:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-13 13:31 [PATCH v2 0/2] drm/bridge: lt9211: Add drive-strength-microamp DT property Boerge Struempfel
2026-05-13 13:31 ` [PATCH v2 1/2] dt-bindings: display/bridge: lt9211: Add drive-strength-microamp property Boerge Struempfel
2026-05-13 13:41   ` Marek Vasut
2026-05-14 10:56     ` Börge Strümpfel
2026-05-14  5:26   ` sashiko-bot [this message]
2026-05-14 10:53     ` Börge Strümpfel
2026-05-13 13:31 ` [PATCH v2 2/2] drm/bridge: lt9211: Add drive-strength-microamp DT property Boerge Struempfel
2026-05-13 13:45   ` Marek Vasut
2026-05-14 11:20     ` Börge Strümpfel
2026-05-14 12:42       ` Marek Vasut

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=20260514052603.BE46FC2BCC6@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=bstruempfel@data-modul.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --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