From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
To: Luca Ceresoli <luca.ceresoli@bootlin.com>,
Michael Walle <mwalle@kernel.org>, Jyri Sarha <jyri.sarha@iki.fi>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/tidss: encoder: convert to devm_drm_bridge_alloc()
Date: Fri, 18 Jul 2025 14:13:03 +0300 [thread overview]
Message-ID: <93ab2ae3-46f4-4245-8d2b-e87700372ba6@ideasonboard.com> (raw)
In-Reply-To: <20250717155659.000eb000@booty>
Hi,
On 17/07/2025 16:56, Luca Ceresoli wrote:
> Hello Jyri, Tomi, Michael,
>
> On Thu, 17 Jul 2025 09:49:44 +0200
> "Michael Walle" <mwalle@kernel.org> wrote:
>
>> Hi,
>>
>> thanks for taking a look!
>>
>>> However allocating an encoder using a bridge alloc function (while we
>>> used to call an encoder allocation function) looks counter-intuitive.
>>>
>>> We had discussed on IRC a different idea, adding a wrapper structure
>>> around the bridge. Quoting your proposal:
>>>
>>> struct tidss_encoder_bridge {
>>> struct drm_bridge bridge;
>>> struct tidss_encoder *encoder
>>> }
>>>
>>> and then in the bridge funcs go from drm_bridge to tidss_encoder_brigde
>>> and use the pointer to get the original private struct.
>>
>> I was doing that until I've realized that meson/meson_encoder_* is
>> doing it the way this patch does it.
>
> Which was done by, er, myself. O:-)
>
> To my excuse, meson was using *_encoder_alloc() but rather
> devm_kzalloc() + drm_simple_encoder_init(), and the change was
> semi-automated via a coccinelle script, so I didn't fully realize that.
>
>>> That would be cleaner and more intuitive, but use a bit more memory and
>>> have an additional pointer deref, thus I think we can live with the
>>> patch you just sent, at least for now.
>>
>> I'm fine with changing it to the wrapper struct. It's your/the
>> maintainers call :)
>
> I think the driver maintainers opinion is more relevant, but in lack of
> one I think we can take the patch as is, given it's already written.
>
> Jyri, Tomi?
I think this is fine, even though I do agree the tidss_encoder.c is very
confusing.
I'll pick this up. I think drm-misc-next-fixes is the correct branch here.
Tomi
next prev parent reply other threads:[~2025-07-18 11:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 13:41 Michael Walle
2025-07-17 7:41 ` Luca Ceresoli
2025-07-17 7:49 ` Michael Walle
2025-07-17 13:56 ` Luca Ceresoli
2025-07-18 11:13 ` Tomi Valkeinen [this message]
2025-07-18 14:44 ` Luca Ceresoli
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=93ab2ae3-46f4-4245-8d2b-e87700372ba6@ideasonboard.com \
--to=tomi.valkeinen@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jyri.sarha@iki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=mwalle@kernel.org \
--cc=simona@ffwll.ch \
--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®