From: Jani Nikula <jani.nikula@linux.intel.com>
To: Maxime Ripard <mripard@kernel.org>
Cc: Anusha Srivatsa <asrivats@redhat.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Jessica Zhang <quic_jesszhan@quicinc.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
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,
Luca Ceresoli <luca.ceresoli@bootlin.com>
Subject: Re: [PATCH v4 2/4] drm/panel: Add refcount support
Date: Tue, 20 May 2025 13:09:47 +0300 [thread overview]
Message-ID: <87sekztwyc.fsf@intel.com> (raw)
In-Reply-To: <20250519-singing-silent-stingray-fe5c9b@houat>
Maxime -
I'm cutting a lot of context here. Not because I don't think it deserves
an answer, but because I seem to be failing at communication.
On Mon, 19 May 2025, Maxime Ripard <mripard@kernel.org> wrote:
> You still haven't explained why it would take anything more than
> registering a dumb device at probe time though.
With that, do you mean a dumb struct device, or any struct device with a
suitable lifetime, that we'd pass to devm_drm_panel_alloc()?
Is using devm_drm_panel_alloc() like that instead of our own allocation
with drm_panel_init() the main point of contention for you? If yes, we
can do that.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-05-20 10:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 15:15 [PATCH v4 0/4] drm/panel: Panel Refcounting infrastructure Anusha Srivatsa
2025-03-31 15:15 ` [PATCH v4 1/4] drm/panel: Add new helpers for refcounted panel allocatons Anusha Srivatsa
2025-03-31 15:15 ` [PATCH v4 2/4] drm/panel: Add refcount support Anusha Srivatsa
2025-04-28 16:31 ` Jani Nikula
2025-04-29 9:00 ` Maxime Ripard
2025-04-29 9:22 ` Jani Nikula
2025-05-05 6:53 ` Maxime Ripard
2025-05-05 18:52 ` Anusha Srivatsa
2025-05-08 14:27 ` Jani Nikula
2025-05-08 21:48 ` Anusha Srivatsa
2025-05-09 9:24 ` Jani Nikula
2025-05-09 11:41 ` Maxime Ripard
2025-05-09 12:45 ` Jani Nikula
2025-05-13 2:40 ` Anusha Srivatsa
2025-05-13 12:19 ` Jani Nikula
2025-05-13 13:06 ` Maxime Ripard
2025-05-14 9:22 ` Jani Nikula
2025-05-16 19:43 ` Anusha Srivatsa
2025-05-19 12:23 ` Jani Nikula
2025-05-19 16:05 ` Maxime Ripard
2025-05-20 10:09 ` Jani Nikula [this message]
2025-05-23 11:34 ` Jani Nikula
2025-05-27 15:04 ` Maxime Ripard
2025-05-27 19:24 ` Jani Nikula
2025-05-27 14:57 ` Maxime Ripard
2025-05-27 19:40 ` Jani Nikula
2025-06-06 7:33 ` Maxime Ripard
2025-06-06 9:11 ` Jani Nikula
2025-03-31 15:15 ` [PATCH v4 3/4] drm/panel: deprecate old-style panel allocation Anusha Srivatsa
2025-03-31 15:15 ` [PATCH v4 4/4] drm/panel/panel-simple: Use the new allocation in place of devm_kzalloc() Anusha Srivatsa
2025-04-01 15:05 ` [PATCH v4 0/4] drm/panel: Panel Refcounting infrastructure 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=87sekztwyc.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=asrivats@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_jesszhan@quicinc.com \
--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 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.