linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime@cerno.tech>
To: Sui Jingfeng <15330273260@189.cn>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
	Lucas Stach <l.stach@pengutronix.de>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Roland Scheidegger <sroland@vmware.com>,
	Zack Rusin <zackr@vmware.com>,
	Christian Gmeiner <christian.gmeiner@gmail.com>,
	David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
	Rob Herring <robh+dt@kernel.org>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Andrey Zhizhikin <andrey.zhizhikin@leica-geosystems.com>,
	Sam Ravnborg <sam@ravnborg.org>,
	suijingfeng <suijingfeng@loongson.cn>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org,
	Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v6 1/3] drm/lsdc: add drm driver for loongson display controller
Date: Wed, 16 Feb 2022 15:11:27 +0100	[thread overview]
Message-ID: <20220216141127.2b7frii62w7xp3tu@houat> (raw)
In-Reply-To: <965ca520-229f-5729-bf06-ae64ed3af383@189.cn>

[-- Attachment #1: Type: text/plain, Size: 650 bytes --]



On Wed, Feb 16, 2022 at 09:34:47PM +0800, Sui Jingfeng wrote:
> On 2022/2/10 00:16, Maxime Ripard wrote:
> > And, to reinstate, we already have a mechanism to set an EDID, and if it
> > wasn't an option, the DT is not the place to store an EDID blob.
> 
> Hi,
> 
> 
> if DT is not the place to store EDID blob, why nvidia can do that ?
> 
> output->edid = of_get_property(output->of_node, "nvidia,edid", &size);
> [1][2]

Because that binding is 10 years old and never got reviewed by a DT maintainer.

Things change, some things we did in the past have been mistakes that we
don't want to repeat, can we move forward?

Maxime

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2022-02-16 14:11 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03  8:25 [PATCH v6 0/3] drm/lsdc: add drm driver for loongson display controller Sui Jingfeng
2022-02-03  8:25 ` [PATCH v6 1/3] " Sui Jingfeng
2022-02-03  8:53   ` Krzysztof Kozlowski
2022-02-03 11:07     ` Dan Carpenter
2022-02-03 11:29       ` Krzysztof Kozlowski
2022-02-03 13:34         ` Dan Carpenter
2022-02-03  8:58   ` Maxime Ripard
2022-02-03 15:47     ` Sui Jingfeng
2022-02-09  8:52       ` Maxime Ripard
2022-02-09 11:56         ` Jiaxun Yang
2022-02-09 14:04           ` Maxime Ripard
2022-02-09 14:14             ` Jiaxun Yang
2023-02-03  3:25             ` suijingfeng
2022-02-03 16:04     ` Sui Jingfeng
2022-02-09  8:49       ` Maxime Ripard
2022-02-09 14:38         ` Sui Jingfeng
2022-02-09 16:16           ` Maxime Ripard
2022-02-12 18:11             ` Sui Jingfeng
2022-02-16 14:08               ` Maxime Ripard
2022-02-12 20:52             ` Ilia Mirkin
2022-02-16 13:34             ` Sui Jingfeng
2022-02-16 14:11               ` Maxime Ripard [this message]
2022-02-03 16:29     ` Sui Jingfeng
2022-02-09  8:43       ` Maxime Ripard
2022-02-09 15:41         ` Sui Jingfeng
2022-02-09 16:19           ` Maxime Ripard
2022-02-16 13:46           ` Daniel Stone
2022-02-16 14:13             ` Sui Jingfeng
2022-02-16 14:43               ` Daniel Stone
2022-02-03 16:41     ` Sui Jingfeng
2022-02-09  8:36       ` Maxime Ripard
2023-02-02  2:58         ` suijingfeng
2022-02-03  8:25 ` [PATCH v6 2/3] dt-bindings: ls2k1000: add the display controller device node Sui Jingfeng
2022-02-03  8:50   ` Krzysztof Kozlowski
2022-02-16 14:01     ` Sui Jingfeng
2022-02-17  8:38       ` Krzysztof Kozlowski
2022-02-03  8:25 ` [PATCH v6 3/3] dt-bindings: mips: loongson: introduce board specific dts Sui Jingfeng
2022-02-03  8:49   ` Krzysztof Kozlowski
2022-02-09 12:00 ` [PATCH v6 0/3] drm/lsdc: add drm driver for loongson display controller Jiaxun Yang
2022-02-10  4:04   ` Sui Jingfeng

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=20220216141127.2b7frii62w7xp3tu@houat \
    --to=maxime@cerno.tech \
    --cc=15330273260@189.cn \
    --cc=airlied@linux.ie \
    --cc=andrey.zhizhikin@leica-geosystems.com \
    --cc=christian.gmeiner@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=krzk@kernel.org \
    --cc=l.stach@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=rdunlap@infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=sam@ravnborg.org \
    --cc=sroland@vmware.com \
    --cc=suijingfeng@loongson.cn \
    --cc=tsbogend@alpha.franken.de \
    --cc=zackr@vmware.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).