From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: "Ricardo Cañuelo" <ricardo.canuelo@collabora.com>
Cc: devicetree@vger.kernel.org, jason@lakedaemon.net,
dri-devel@lists.freedesktop.org, robh+dt@kernel.org,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
kernel@collabora.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH] dt-bindings: display: ti,tfp410.txt: convert to yaml
Date: Wed, 6 May 2020 11:33:12 +0300 [thread overview]
Message-ID: <a571c6a8-1b36-10fa-e0e1-c535563c62e9@ti.com> (raw)
In-Reply-To: <20200506082843.mkhip2n2uiimcf2z@rcn-XPS-13-9360>
On 06/05/2020 11:28, Ricardo Cañuelo wrote:
> Hi Tomi,
>
> On mié 06-05-2020 11:01:07, Tomi Valkeinen wrote:
>> 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.
>
> I agree and I'd vote for "missing feature", but seeing that there aren't
> any other examples of this use case in the whole kernel dts collection
> (at least I couldn't find any) I thought that maybe it's us who are
> going against the norm here.
A valid point. I'm not aware of anyone using the deskew property. My guess is that Laurent added it
just because it was in the spec, not because he had a need for it. So I don't think changing the
binding is totally out of the question.
Tomi
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-05-06 8:33 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
2020-05-06 8:28 ` Ricardo Cañuelo
2020-05-06 8:33 ` Tomi Valkeinen [this message]
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=a571c6a8-1b36-10fa-e0e1-c535563c62e9@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