public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sui Jingfeng <sui.jingfeng@linux.dev>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Andrzej Hajda <andrzej.hajda@intel.com>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Robert Foss <rfoss@kernel.org>,
	Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
	Jonas Karlman <jonas@kwiboo.se>,
	Jernej Skrabec <jernej.skrabec@gmail.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
	Phong LE <ple@baylibre.com>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/4] drm/bridge: Add fwnode based helpers to get the next bridge
Date: Fri, 8 Mar 2024 05:09:13 +0800	[thread overview]
Message-ID: <ce073b95-b8e9-4822-91a2-f2bd15997bc4@linux.dev> (raw)
In-Reply-To: <CAA8EJppTcPO3j7GpGcGbKPUjQ=3rTMMOrU1SYR3mtkWLztf2qQ@mail.gmail.com>

Hi,


On 2024/3/8 04:40, Dmitry Baryshkov wrote:
>>> But really, there is nothing so hard about it:
>>> - Change of_node to fw_node, apply an automatic patch changing this in
>>> bridge drivers.
>>> - Make drm_of_bridge functions convert passed of_node and comp
>>>
>>> After this we can start cleaning up bridge drivers to use fw_node API
>>> natively as you did in your patches 2-4.
>> Yes, it's not so hard. But I'm a little busy due to other downstream developing
>> tasks. Sorry, very sorry!
>>
>> During the talk with you, I observed that you are very good at fwnode domain.
>> Are you willing to help the community to do something? For example, currently
>> the modern drm bridge framework is corrupted by legacy implement, is it possible
>> for us to migrate them to modern? Instead of rotting there? such as the lontium-lt9611uxc.c
>> which create a drm connector manually, not modernized yet and it's DT dependent.
>> So, there are a lot things to do.
> Actually, lontium-lt9611uxc.c does both of that 😉 It supports
> creating a connector and it as well supports attaching to a chain
> without creating a connector. Pretty nice, isn't it?


I'm not very sure. But I remember a most experienced told me that
"Not having anything connector-related in the drm_bridge driver is a canonical design".
And I think he is right and I believed.


  reply	other threads:[~2024-03-07 21:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07 17:23 [PATCH v2 0/4] drm/bridge: Allow using fwnode API to get the next bridge Sui Jingfeng
2024-03-07 17:23 ` [PATCH v2 1/4] drm/bridge: Add fwnode based helpers " Sui Jingfeng
2024-03-07 18:43   ` Dmitry Baryshkov
2024-03-07 19:20     ` Sui Jingfeng
2024-03-07 19:30       ` Sui Jingfeng
2024-03-07 19:37       ` Dmitry Baryshkov
2024-03-07 20:32         ` Sui Jingfeng
2024-03-07 20:40           ` Dmitry Baryshkov
2024-03-07 21:09             ` Sui Jingfeng [this message]
2024-03-07 21:13               ` Sui Jingfeng
2024-03-09  9:33             ` Sui Jingfeng
2024-03-09 10:39               ` Dmitry Baryshkov
2024-03-09 11:25                 ` Sui Jingfeng
2024-03-09 12:50                   ` Dmitry Baryshkov
2024-03-09 12:03                 ` Sui Jingfeng
2024-03-09 13:29                   ` Dmitry Baryshkov
2024-03-07 17:23 ` [PATCH v2 2/4] drm/bridge: simple-bridge: Use fwnode API to acquire device properties Sui Jingfeng
2024-03-07 17:23 ` [PATCH v2 3/4] drm-bridge: display-connector: " Sui Jingfeng
2024-03-07 17:23 ` [PATCH v2 4/4] drm-bridge: it66121: " Sui Jingfeng
2024-03-07 19:31   ` Dmitry Baryshkov
2024-03-07 19:39     ` 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=ce073b95-b8e9-4822-91a2-f2bd15997bc4@linux.dev \
    --to=sui.jingfeng@linux.dev \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=airlied@gmail.com \
    --cc=andrzej.hajda@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=ple@baylibre.com \
    --cc=rfoss@kernel.org \
    --cc=tzimmermann@suse.de \
    /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