From: Sui Jingfeng <sui.jingfeng@linux.dev>
To: Maxime Ripard <mripard@kernel.org>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] drm/bridge: Add 'struct device *' field to the drm_bridge structure
Date: Wed, 15 May 2024 00:53:33 +0800 [thread overview]
Message-ID: <c44480ab-8d6b-4334-8eba-83db9b30ff1a@linux.dev> (raw)
In-Reply-To: <20240514-scarlet-corgi-of-efficiency-faf2bb@penduick>
Hi,
On 2024/5/15 00:22, Maxime Ripard wrote:
> Hi,
>
> On Tue, May 14, 2024 at 11:40:43PM +0800, Sui Jingfeng wrote:
>> Because a lot of implementations has already added it into their drived
>> class, promote it into drm_bridge core may benifits a lot. drm bridge is
>> a driver, it should know the underlying hardware entity.
> Is there some actual benefits, or is it theoretical at this point?
I think, DRM bridge drivers could remove the 'struct device *dev'
member from their derived structure. Rely on the drm bridge core
when they need the 'struct device *' pointer.
> Maxime
--
Best regards,
Sui
next prev parent reply other threads:[~2024-05-14 16:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 15:40 [PATCH 0/2] drm/bridge: Add 'struct device *' field to the drm_bridge structure Sui Jingfeng
2024-05-14 15:40 ` [PATCH 1/2] drm/bridge: Support finding bridge with struct device Sui Jingfeng
2024-05-15 9:39 ` Jani Nikula
2024-05-15 10:17 ` Sui Jingfeng
2024-05-15 10:28 ` Jani Nikula
2024-05-15 10:34 ` Sui Jingfeng
2024-05-15 11:33 ` Jani Nikula
2024-05-14 15:40 ` [PATCH 2/2] drm/bridge: Switch to use drm_bridge_add_with_dev() Sui Jingfeng
2024-05-14 16:22 ` [PATCH 0/2] drm/bridge: Add 'struct device *' field to the drm_bridge structure Maxime Ripard
2024-05-14 16:53 ` Sui Jingfeng [this message]
2024-05-15 14:30 ` Maxime Ripard
2024-05-15 14:53 ` Sui Jingfeng
2024-05-15 14:58 ` Maxime Ripard
2024-05-15 15:19 ` Sui Jingfeng
2024-05-16 8:25 ` Maxime Ripard
2024-05-16 10:40 ` Sui Jingfeng
2024-05-16 12:04 ` Sui Jingfeng
2024-05-19 21:44 ` Dmitry Baryshkov
2024-05-21 8:37 ` Maxime Ripard
2024-05-21 8:34 ` Maxime Ripard
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=c44480ab-8d6b-4334-8eba-83db9b30ff1a@linux.dev \
--to=sui.jingfeng@linux.dev \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.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.