From: "José Expósito" <jose.exposito89@gmail.com>
To: emma@anholt.net
Cc: mripard@kernel.org, laurent.pinchart@ideasonboard.com,
airlied@linux.ie, daniel@ffwll.ch, p.zabel@pengutronix.de,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
"José Expósito" <jose.exposito89@gmail.com>
Subject: [PATCH v3 0/2] drm/vc4: hdmi: Replace drm_detect_hdmi_monitor() with drm_display_info.is_hdmi
Date: Wed, 20 Apr 2022 13:44:58 +0200 [thread overview]
Message-ID: <20220420114500.187664-1-jose.exposito89@gmail.com> (raw)
Hi everyone,
These patches replace the calls to drm_detect_hdmi_monitor() with the
more efficient drm_display_info.is_hdmi in the VC4 driver and, since
this makes the vc4_hdmi_encoder struct redundant, also removes it.
Thanks,
José Expósito
v1: https://lore.kernel.org/dri-devel/20220406165514.6106-1-jose.exposito89@gmail.com/
v2: https://lore.kernel.org/dri-devel/20220415154745.170597-1-jose.exposito89@gmail.com/T/
Add the ftrace command used in the first patch
Remove vc4_hdmi_encoder.hdmi_monitor
(Thanks to Maxime for suggesting these changes)
v3: Squash the patches present in v2
Remove vc4_hdmi_encoder
(Thanks to Maxime for suggesting these changes)
José Expósito (2):
drm/vc4: hdmi: Replace drm_detect_hdmi_monitor() with is_hdmi
drm/vc4: hdmi: Remove vc4_hdmi_encoder
drivers/gpu/drm/vc4/vc4_hdmi.c | 41 +++++++++++++++-------------------
drivers/gpu/drm/vc4/vc4_hdmi.h | 17 ++------------
2 files changed, 20 insertions(+), 38 deletions(-)
--
2.25.1
next reply other threads:[~2022-04-20 11:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 11:44 José Expósito [this message]
2022-04-20 11:44 ` [PATCH v3 1/2] drm/vc4: hdmi: Replace drm_detect_hdmi_monitor() with is_hdmi José Expósito
2022-04-21 7:07 ` (subset) " Maxime Ripard
2022-04-20 11:45 ` [PATCH v3 2/2] drm/vc4: hdmi: Remove vc4_hdmi_encoder José Expósito
2022-04-21 7:07 ` (subset) " 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=20220420114500.187664-1-jose.exposito89@gmail.com \
--to=jose.exposito89@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=emma@anholt.net \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=p.zabel@pengutronix.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®