devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: "Ricardo Cañuelo" <ricardo.canuelo@collabora.com>
Cc: <robh+dt@kernel.org>,
	Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
	<kernel@collabora.com>, <devicetree@vger.kernel.org>,
	<dri-devel@lists.freedesktop.org>,
	<linux-arm-kernel@lists.infradead.org>, <jason@lakedaemon.net>
Subject: Re: [RFC PATCH] dt-bindings: display: ti,tfp410.txt: convert to yaml
Date: Wed, 6 May 2020 11:01:07 +0300	[thread overview]
Message-ID: <1cee742a-c16a-fb32-5caa-c6ac71689ab9@ti.com> (raw)
In-Reply-To: <20200506072155.6dmj35zdnr3to5ib@rcn-XPS-13-9360>

Hi Ricardo,

On 06/05/2020 10:21, Ricardo Cañuelo wrote:
> Hi Tomi, thanks for reviewing the patch.
> 
> On mar 28-04-2020 12:49:28, Tomi Valkeinen wrote:
>> I don't quite understand this. We cannot have negative numbers in dts files?
>> Or we can, but dt_binding_check doesn't handle them correctly? Or that int32
>> is not supported in yaml bindings?
> 
> AFAICT, you can have negative numbers in dts files (see [1] and [2]) and

This is also my understanding after some googling. And there's even of_property_read_s32() in the 
kernel.

> the DT schema certainly supports signed integers, but dt_binding_check
> seems to interpret all cells as unsigned 32bit integers because that's
> what they are, really. In kernel code this is not a problem because you

Well, this is in the nitpick category, and maybe not even relevant, but I don't think that's 
correct. They're just bits. Some pieces of SW happen to use u32 containers to store the bits. But 
what the bits mean is not related to the container.

> can cast the value back to a signed int before you run your own sanity
> checks on them.

Doesn't all this just point to a bug or missing feature in dt_binding_check? That's not a reason to 
change the ABI.

  Tomi

-- 
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki

  reply	other threads:[~2020-05-06  8:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28  9:20 [RFC PATCH] dt-bindings: display: ti,tfp410.txt: convert to yaml Ricardo Cañuelo
2020-04-28  9:49 ` Tomi Valkeinen
2020-05-06  7:21   ` Ricardo Cañuelo
2020-05-06  8:01     ` Tomi Valkeinen [this message]
2020-05-06  8:28       ` Ricardo Cañuelo
2020-05-06  8:33         ` Tomi Valkeinen
2020-05-06 15:53   ` Laurent Pinchart
2020-05-11 14:59     ` Ricardo Cañuelo
2020-05-11 16:26       ` Sam Ravnborg
2020-05-12  2:09       ` Rob Herring
2020-05-13 11:09     ` Ricardo Cañuelo
2020-05-13 14:08       ` Laurent Pinchart
2020-05-13 14:20         ` Ricardo Cañuelo
2020-04-28 19:21 ` Sam Ravnborg
2020-04-29  8:54   ` Ricardo Cañuelo

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=1cee742a-c16a-fb32-5caa-c6ac71689ab9@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=Laurent.pinchart@ideasonboard.com \
    --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=ricardo.canuelo@collabora.com \
    --cc=robh+dt@kernel.org \
    /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).