All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikita Yushchenko <nikita.yoush@cogentembedded.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	Magnus Damm <magnus.damm@gmail.com>,
	Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
	David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
	Rob Herring <robh+dt@kernel.org>,
	dri-devel@lists.freedesktop.org,
	linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] arm64: dts: renesas: r8a77961: Add lvds0 device node
Date: Wed, 29 Dec 2021 20:19:10 +0300	[thread overview]
Message-ID: <39f70781-831e-c86a-ec5f-68f2b4bd3d62@cogentembedded.com> (raw)
In-Reply-To: <YcyXQxW3kRqQ2Yv0@pendragon.ideasonboard.com>

>> If this approach is not appropriate, then perhaps need to fix it in
>> files for all SoCs, to make it possible for extension board dtsi to be
>> compatible with all of them.
> 
> I'm writing a patch to drop those right now :-) I'll CC you.

Ok.

But, are you sure that empty nodes like these are that bad?

I was going to suggest a movement in opposite direction - adding more such nodes, so they could form a 
sort of API for dts plugins describing e.g. displays connectable to boards based on different SoCs.

Nikita

WARNING: multiple messages have this Message-ID (diff)
From: Nikita Yushchenko <nikita.yoush@cogentembedded.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: devicetree@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	David Airlie <airlied@linux.ie>,
	Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
	Magnus Damm <magnus.damm@gmail.com>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-renesas-soc@vger.kernel.org,
	Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH 2/3] arm64: dts: renesas: r8a77961: Add lvds0 device node
Date: Wed, 29 Dec 2021 20:19:10 +0300	[thread overview]
Message-ID: <39f70781-831e-c86a-ec5f-68f2b4bd3d62@cogentembedded.com> (raw)
In-Reply-To: <YcyXQxW3kRqQ2Yv0@pendragon.ideasonboard.com>

>> If this approach is not appropriate, then perhaps need to fix it in
>> files for all SoCs, to make it possible for extension board dtsi to be
>> compatible with all of them.
> 
> I'm writing a patch to drop those right now :-) I'll CC you.

Ok.

But, are you sure that empty nodes like these are that bad?

I was going to suggest a movement in opposite direction - adding more such nodes, so they could form a 
sort of API for dts plugins describing e.g. displays connectable to boards based on different SoCs.

Nikita

  reply	other threads:[~2021-12-29 17:19 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-24  5:23 [PATCH 0/3] add R-Car M3-W+ (r8a99761) LVDS encoder support Nikita Yushchenko
2021-12-24  5:23 ` Nikita Yushchenko
2021-12-24  5:23 ` [PATCH 1/3] drm: rcar-du: lvds: Add r8a77961 support Nikita Yushchenko
2021-12-24  5:23   ` Nikita Yushchenko
2021-12-29 16:53   ` Laurent Pinchart
2021-12-29 16:53     ` Laurent Pinchart
2021-12-24  5:23 ` [PATCH 2/3] arm64: dts: renesas: r8a77961: Add lvds0 device node Nikita Yushchenko
2021-12-24  5:23   ` Nikita Yushchenko
2021-12-29 16:56   ` Laurent Pinchart
2021-12-29 16:56     ` Laurent Pinchart
2021-12-29 17:04     ` Nikita Yushchenko
2021-12-29 17:04       ` Nikita Yushchenko
2021-12-29 17:13       ` Laurent Pinchart
2021-12-29 17:13         ` Laurent Pinchart
2021-12-29 17:19         ` Nikita Yushchenko [this message]
2021-12-29 17:19           ` Nikita Yushchenko
2021-12-29 19:33           ` Laurent Pinchart
2021-12-29 19:33             ` Laurent Pinchart
2021-12-29 21:12             ` Nikita Yushchenko
2021-12-29 21:12               ` Nikita Yushchenko
2021-12-29 22:19               ` Laurent Pinchart
2021-12-29 22:19                 ` Laurent Pinchart
2021-12-30  5:30                 ` Nikita Yushchenko
2021-12-30  5:30                   ` Nikita Yushchenko
2021-12-30 17:11                   ` Laurent Pinchart
2021-12-30 17:11                     ` Laurent Pinchart
2022-01-12 21:10         ` Nikita Yushchenko
2022-01-13  9:01           ` Geert Uytterhoeven
2022-01-10  8:43     ` Geert Uytterhoeven
2022-01-10  8:43       ` Geert Uytterhoeven
2022-01-10  8:51       ` Laurent Pinchart
2022-01-10  8:51         ` Laurent Pinchart
2022-01-10  8:52   ` Geert Uytterhoeven
2022-01-10  8:52     ` Geert Uytterhoeven
2022-01-10  9:51     ` Nikita Yushchenko
2022-01-10  9:51       ` Nikita Yushchenko
2022-01-10  9:55       ` Geert Uytterhoeven
2022-01-10  9:55         ` Geert Uytterhoeven
2021-12-24  5:23 ` [PATCH 3/3] dt-bindings: display: bridge: renesas,lvds: Document r8a77961 bindings Nikita Yushchenko
2021-12-24  5:23   ` [PATCH 3/3] dt-bindings: display: bridge: renesas, lvds: " Nikita Yushchenko
2021-12-29 16:46   ` [PATCH 3/3] dt-bindings: display: bridge: renesas,lvds: " Laurent Pinchart
2021-12-29 16:46     ` [PATCH 3/3] dt-bindings: display: bridge: renesas, lvds: " Laurent Pinchart
2022-03-02 17:00     ` [PATCH 3/3] dt-bindings: display: bridge: renesas,lvds: " Geert Uytterhoeven
2022-03-02 17:00       ` [PATCH 3/3] dt-bindings: display: bridge: renesas, lvds: " Geert Uytterhoeven
2022-03-03  9:14       ` [PATCH 3/3] dt-bindings: display: bridge: renesas,lvds: " Laurent Pinchart
2022-03-03  9:14         ` [PATCH 3/3] dt-bindings: display: bridge: renesas, lvds: " Laurent Pinchart
2022-03-04 12:20         ` [PATCH 3/3] dt-bindings: display: bridge: renesas,lvds: " Laurent Pinchart
2022-03-04 12:20           ` [PATCH 3/3] dt-bindings: display: bridge: renesas, lvds: " Laurent Pinchart
2022-01-04 20:19   ` [PATCH 3/3] dt-bindings: display: bridge: renesas,lvds: " Rob Herring
2022-01-04 20:19     ` [PATCH 3/3] dt-bindings: display: bridge: renesas, lvds: " Rob Herring

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=39f70781-831e-c86a-ec5f-68f2b4bd3d62@cogentembedded.com \
    --to=nikita.yoush@cogentembedded.com \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=geert+renesas@glider.be \
    --cc=kieran.bingham+renesas@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.