mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sui Jingfeng <sui.jingfeng@linux.dev>,
	Neil Armstrong <neil.armstrong@linaro.org>
Cc: Robert Foss <rfoss@kernel.org>,
	Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
	Andrzej Hajda <andrzej.hajda@intel.com>,
	Jonas Karlman <jonas@kwiboo.se>,
	Jernej Skrabec <jernej.skrabec@gmail.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 v4 9/9] drm/bridge: tfp410: Add platform module alias
Date: Tue, 23 Apr 2024 12:49:59 +0200	[thread overview]
Message-ID: <368f8c24-5c25-4a96-9714-80f31a6661a4@kernel.org> (raw)
In-Reply-To: <648e60f1-780a-428c-93b3-89d9804d6686@linux.dev>

On 23/04/2024 12:44, Sui Jingfeng wrote:
>>>>    If you need platform one, for some reason, explain
>>>> what is your matching path and add appropriate ID table. With that
>>>> explanation, of course.
>>> When tfp410 works as a transparent bridge. The device itself is just a platform device.
>>> similar with the display-connector.c and simple-bridge.c.
>>>
>>> It is not discoverable by the system on non-DT environment, this is the root problem.
>>> I said the various display bridges drivers are fully DT dependent, Dimtry didn't agree!
>>>
>>> He said "I can not agree here. It doesn't depend on DT." and then asks me to developing
>>> some other solution witch could preserve code sharing. So here it is.
>>
>> You wrote long message without actually reading my answer early. I
>> already gave you the solution. Address that one.
> 
> Use MODULE_DEVICE_TABLE() instead? OK, I understand then. Thanks a lot 
> for the education.


Yes, at least for something which is real driver.

Best regards,
Krzysztof


      reply	other threads:[~2024-04-23 10:50 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-22 19:18 [PATCH v4 0/9] drm/bridge: Allow using fwnode API to get the next bridge Sui Jingfeng
2024-04-22 19:18 ` [PATCH v4 1/9] " Sui Jingfeng
2024-04-22 19:51   ` Dmitry Baryshkov
2024-04-23  6:21     ` Sui Jingfeng
2024-04-22 19:18 ` [PATCH v4 2/9] drm/bridge: simple-bridge: Use fwnode API to acquire device properties Sui Jingfeng
2024-04-22 19:56   ` Dmitry Baryshkov
2024-04-22 19:18 ` [PATCH v4 3/9] drm/bridge: simple-bridge: Add platform module alias Sui Jingfeng
2024-04-22 19:58   ` Dmitry Baryshkov
2024-04-22 19:18 ` [PATCH v4 4/9] drm-bridge: display-connector: Use fwnode API to acquire device properties Sui Jingfeng
2024-04-22 20:00   ` Dmitry Baryshkov
2024-04-22 19:18 ` [PATCH v4 5/9] drm/bridge: display-connector: Add platform module alias Sui Jingfeng
2024-04-22 20:01   ` Dmitry Baryshkov
2024-04-22 19:19 ` [PATCH v4 6/9] drm-bridge: sii902x: Use fwnode API to acquire device properties Sui Jingfeng
2024-04-22 20:02   ` Dmitry Baryshkov
2024-04-22 19:19 ` [PATCH v4 7/9] drm-bridge: it66121: " Sui Jingfeng
2024-04-22 20:06   ` Dmitry Baryshkov
2024-04-27 13:11     ` Sui Jingfeng
2024-04-22 19:19 ` [PATCH v4 8/9] drm/bridge: tfp410: " Sui Jingfeng
2024-04-22 20:08   ` Dmitry Baryshkov
2024-04-27 18:43     ` Sui Jingfeng
2024-04-27 19:17       ` Dmitry Baryshkov
2024-04-27 20:10         ` Sui Jingfeng
2024-04-22 19:19 ` [PATCH v4 9/9] drm/bridge: tfp410: Add platform module alias Sui Jingfeng
2024-04-23  8:05   ` Krzysztof Kozlowski
2024-04-23 10:12     ` Sui Jingfeng
2024-04-23 10:20       ` Krzysztof Kozlowski
2024-04-23 10:44         ` Sui Jingfeng
2024-04-23 10:49           ` Krzysztof Kozlowski [this message]

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=368f8c24-5c25-4a96-9714-80f31a6661a4@kernel.org \
    --to=krzk@kernel.org \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=airlied@gmail.com \
    --cc=andrzej.hajda@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mripard@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=ple@baylibre.com \
    --cc=rfoss@kernel.org \
    --cc=sui.jingfeng@linux.dev \
    --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

all inboxes | Powered by JetHome®