[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <368f8c24-5c25-4a96-9714-80f31a6661a4@kernel.org>
Date: Tue, 23 Apr 2024 12:49:59 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Sui Jingfeng <sui.jingfeng@...ux.dev>,
Neil Armstrong <neil.armstrong@...aro.org>
Cc: Robert Foss <rfoss@...nel.org>,
Laurent Pinchart <Laurent.pinchart@...asonboard.com>,
Andrzej Hajda <andrzej.hajda@...el.com>, Jonas Karlman <jonas@...boo.se>,
Jernej Skrabec <jernej.skrabec@...il.com>, Maxime Ripard
<mripard@...nel.org>, Thomas Zimmermann <tzimmermann@...e.de>,
David Airlie <airlied@...il.com>, Daniel Vetter <daniel@...ll.ch>,
Phong LE <ple@...libre.com>, dri-devel@...ts.freedesktop.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 9/9] drm/bridge: tfp410: Add platform module alias
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
Powered by blists - more mailing lists