devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ricardo Cañuelo" <ricardo.canuelo@collabora.com>
To: Laurent.pinchart@ideasonboard.com
Cc: kernel@collabora.com, devicetree@vger.kernel.org,
	dri-devel@lists.freedesktop.org,
	linux-arm-kernel@lists.infradead.org, jason@lakedaemon.net,
	tomi.valkeinen@ti.com, robh+dt@kernel.org, airlied@linux.ie
Subject: [PATCH v3 2/5] dt-bindings: display: ti,tfp410.yaml: Redefine ti,deskew property
Date: Thu, 11 Jun 2020 12:23:53 +0200	[thread overview]
Message-ID: <20200611102356.31563-3-ricardo.canuelo@collabora.com> (raw)
In-Reply-To: <20200611102356.31563-1-ricardo.canuelo@collabora.com>

This changes how the 'ti,deskew' property is defined. It's now an
unsigned value from 0 to 7 instead of a signed value from -4 to 3.
Until the dtc carries the integer sign through to the yaml output it's
easier to define signed types as unsigned.

Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com>
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
---
 .../devicetree/bindings/display/bridge/ti,tfp410.yaml    | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/Documentation/devicetree/bindings/display/bridge/ti,tfp410.yaml b/Documentation/devicetree/bindings/display/bridge/ti,tfp410.yaml
index 5569a4907765..605831c1e836 100644
--- a/Documentation/devicetree/bindings/display/bridge/ti,tfp410.yaml
+++ b/Documentation/devicetree/bindings/display/bridge/ti,tfp410.yaml
@@ -23,11 +23,12 @@ properties:
 
   ti,deskew:
     description:
-      Data de-skew in 350ps increments, from -4 to +3, as configured
-      through th DK[3:1] pins. This property shall be present only if the TFP410
-      is not connected through I2C.
-    maxItems: 1
+      Data de-skew value in 350ps increments, from 0 to 7, as configured
+      through the DK[3:1] pins. The de-skew multiplier is computed as
+      (DK[3:1] - 4), so it ranges from -4 to 3.
     $ref: /schemas/types.yaml#/definitions/uint32
+    minimum: 0
+    maximum: 7
 
   ports:
     description:
-- 
2.18.0


  parent reply	other threads:[~2020-06-11 10:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11 10:23 [PATCH v3 0/5] dt-bindings: display: ti,tfp410.txt: convert to yaml Ricardo Cañuelo
2020-06-11 10:23 ` [PATCH v3 1/5] " Ricardo Cañuelo
2020-06-11 10:23 ` Ricardo Cañuelo [this message]
2020-06-11 10:23 ` [PATCH v3 3/5] drm/bridge: tfp410: fix de-skew value retrieval from DT Ricardo Cañuelo
2020-06-11 10:23 ` [PATCH v3 4/5] drm/bridge: tfp410: Fix setup and hold time calculation Ricardo Cañuelo
2020-06-11 10:23 ` [PATCH v3 5/5] dt-bindings: display: ti,tfp410.yaml: make the ports node optional Ricardo Cañuelo
2020-06-11 16:08   ` Laurent Pinchart
2020-06-15  9:38     ` Ricardo Cañuelo
2020-06-16  1:51       ` Laurent Pinchart
2020-06-16  6:42         ` Ricardo Cañuelo
2020-06-17 22:37       ` Rob Herring
2020-06-17 22:34   ` Rob Herring
2020-06-17 22:43     ` Laurent Pinchart

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=20200611102356.31563-3-ricardo.canuelo@collabora.com \
    --to=ricardo.canuelo@collabora.com \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=airlied@linux.ie \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jason@lakedaemon.net \
    --cc=kernel@collabora.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=tomi.valkeinen@ti.com \
    /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;
as well as URLs for NNTP newsgroup(s).