From: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
To: Maxime Ripard <mripard@kernel.org>
Cc: "Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Dave Stevenson" <dave.stevenson@raspberrypi.com>,
"Maíra Canal" <mcanal@igalia.com>,
"Raspberry Pi Kernel Maintenance" <kernel-list@raspberrypi.com>,
"Andrzej Hajda" <andrzej.hajda@intel.com>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Robert Foss" <rfoss@kernel.org>,
"Laurent Pinchart" <Laurent.pinchart@ideasonboard.com>,
"Jonas Karlman" <jonas@kwiboo.se>,
"Jernej Skrabec" <jernej.skrabec@gmail.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
"Dmitry Baryshkov" <lumag@kernel.org>
Subject: Re: [PATCH v5 04/11] drm/connector: unregister CEC data
Date: Tue, 15 Apr 2025 12:03:23 +0300 [thread overview]
Message-ID: <f59c0ab6-2391-4712-a3d5-18e67f538d4f@oss.qualcomm.com> (raw)
In-Reply-To: <20250414-hissing-auspicious-goldfish-78b9dc@houat>
On 14/04/2025 17:47, Maxime Ripard wrote:
> Hi,
>
> On Mon, Apr 07, 2025 at 06:11:01PM +0300, Dmitry Baryshkov wrote:
>> In order to make sure that CEC adapters or notifiers are unregistered
>> and CEC-related data is properly destroyed make drm_connector_cleanup()
>> call CEC's unregister() callback.
>>
>> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
>> ---
>> drivers/gpu/drm/drm_connector.c | 9 +++++++++
>> 1 file changed, 9 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/drm_connector.c b/drivers/gpu/drm/drm_connector.c
>> index ba08fbd973829e49ea977251c4f0fb6d96ade631..ae9c02ef9ab102db03c2824683ece37cfbcd3300 100644
>> --- a/drivers/gpu/drm/drm_connector.c
>> +++ b/drivers/gpu/drm/drm_connector.c
>> @@ -743,6 +743,13 @@ void drm_connector_cec_phys_addr_set(struct drm_connector *connector)
>> }
>> EXPORT_SYMBOL(drm_connector_cec_phys_addr_set);
>>
>> +static void drm_connector_cec_unregister(struct drm_connector *connector)
>> +{
>> + if (connector->cec.funcs &&
>> + connector->cec.funcs->unregister)
>> + connector->cec.funcs->unregister(connector);
>> +}
>> +
>> /**
>> * drm_connector_cleanup - cleans up an initialised connector
>> * @connector: connector to cleanup
>> @@ -763,6 +770,8 @@ void drm_connector_cleanup(struct drm_connector *connector)
>>
>> platform_device_unregister(connector->hdmi_audio.codec_pdev);
>>
>> + drm_connector_cec_unregister(connector);
>> +
>
> Actually, since we know that the HDMI connector is drm-managed, why
> can't we make the call to connector->cec.funcs->unregister a drm-managed
> action registered by drm_connector_hdmi_cec_register?
I haven't settled yet in my mind whether we can/should also use this
infrastructure for drm_dp_cec management. So, at this point, I'd prefer
to keep a non-managed unregister function. Once we settle on something
for drm_dp_cec, we can switch to drmm.
--
With best wishes
Dmitry
next prev parent reply other threads:[~2025-04-15 9:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 15:10 [PATCH v5 00/11] drm/display: generic HDMI CEC helpers Dmitry Baryshkov
2025-04-07 15:10 ` [PATCH v5 01/11] drm/bridge: move private data to the end of the struct Dmitry Baryshkov
2025-04-07 15:10 ` [PATCH v5 02/11] drm/bridge: allow limiting I2S formats Dmitry Baryshkov
2025-04-07 15:11 ` [PATCH v5 03/11] drm/connector: add CEC-related fields Dmitry Baryshkov
2025-04-14 14:52 ` Maxime Ripard
2025-04-15 9:10 ` Dmitry Baryshkov
2025-04-28 16:42 ` Dmitry Baryshkov
2025-04-29 15:33 ` Maxime Ripard
2025-04-07 15:11 ` [PATCH v5 04/11] drm/connector: unregister CEC data Dmitry Baryshkov
2025-04-14 14:44 ` Maxime Ripard
2025-04-14 14:47 ` Maxime Ripard
2025-04-15 9:03 ` Dmitry Baryshkov [this message]
2025-04-29 15:35 ` Maxime Ripard
2025-04-29 16:46 ` Dmitry Baryshkov
2025-04-07 15:11 ` [PATCH v5 05/11] drm/display: move CEC_CORE selection to DRM_DISPLAY_HELPER Dmitry Baryshkov
2025-04-14 14:36 ` Maxime Ripard
2025-04-07 15:11 ` [PATCH v5 06/11] drm/display: add CEC helpers code Dmitry Baryshkov
2025-04-14 14:58 ` Maxime Ripard
2025-04-15 16:01 ` Dmitry Baryshkov
2025-04-29 15:40 ` Maxime Ripard
2025-04-30 11:25 ` Jani Nikula
2025-04-07 15:11 ` [PATCH v5 07/11] drm/display: hdmi-state-helper: handle CEC physical address Dmitry Baryshkov
2025-04-07 15:11 ` [PATCH v5 08/11] drm/vc4: hdmi: switch to generic CEC helpers Dmitry Baryshkov
2025-04-14 14:41 ` Maxime Ripard
2025-04-15 9:04 ` Dmitry Baryshkov
2025-04-07 15:11 ` [PATCH v5 09/11] drm/display: bridge-connector: hook in CEC notifier support Dmitry Baryshkov
2025-04-14 14:59 ` Maxime Ripard
2025-04-07 15:11 ` [PATCH v5 10/11] drm/display: bridge-connector: handle CEC adapters Dmitry Baryshkov
2025-04-14 15:05 ` Maxime Ripard
2025-04-07 15:11 ` [PATCH v5 11/11] drm/bridge: adv7511: switch to the HDMI connector helpers Dmitry Baryshkov
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=f59c0ab6-2391-4712-a3d5-18e67f538d4f@oss.qualcomm.com \
--to=dmitry.baryshkov@oss.qualcomm.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=kernel-list@raspberrypi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mcanal@igalia.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@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®