From: Igor Paunovic <royalnet026@gmail.com>
To: dri-devel@lists.freedesktop.org
Cc: Igor Paunovic <royalnet026@gmail.com>,
intel-gfx@lists.freedesktop.org,
linux-rockchip@lists.infradead.org,
Sebastian Reichel <sebastian.reichel@collabora.com>,
Cristian Ciocaltea <cristian.ciocaltea@collabora.com>,
Maxime Ripard <mripard@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Heiko Stuebner <heiko@sntech.de>,
Andy Yan <andy.yan@rock-chips.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Ville Syrjala <ville.syrjala@linux.intel.com>
Subject: Re: [PATCH v2 0/3] drm/dp: shared HDR metadata SDP helper, and max bpc for dw-dp
Date: Wed, 9 Sep 2026 18:37:40 +0200 [thread overview]
Message-ID: <20260909163742.37003-1-royalnet026@gmail.com> (raw)
In-Reply-To: <20260909163206.36409-1-royalnet026@gmail.com>
Following up on my own cover letter, where I said the series had not
been built.
It has now. On top of drm-misc-next bf63a72ea005, x86_64 allmodconfig,
building the five objects the series touches with W=1:
drivers/gpu/drm/display/drm_dp_helper.o
drivers/gpu/drm/display/drm_bridge_connector.o
drivers/gpu/drm/drm_connector.o
drivers/gpu/drm/i915/display/intel_dp.o
drivers/gpu/drm/rockchip/dw_dp-rockchip.o
All five build with no errors and no new warnings. intel_dp.o is the one
I most wanted to see, since 1/3 moves code out of it.
To be exact about what this is and is not: it is a compile test only. I
have still not booted this exact series, for the reason given in the
cover - the runtime testing behind v1 was done on a rockchip-devel
kernel carrying the v9 generation of the dw-dp series, and mainline's
dw_dp-rockchip.c is not the file that was exercised. If you want a boot
test on the Orange Pi 5 Plus before taking this, say so and I will do it.
Igor
WARNING: multiple messages have this Message-ID (diff)
From: Igor Paunovic <royalnet026@gmail.com>
To: dri-devel@lists.freedesktop.org
Cc: Igor Paunovic <royalnet026@gmail.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Heiko Stuebner <heiko@sntech.de>,
intel-gfx@lists.freedesktop.org,
Sebastian Reichel <sebastian.reichel@collabora.com>,
Maxime Ripard <mripard@kernel.org>,
linux-rockchip@lists.infradead.org,
Jani Nikula <jani.nikula@linux.intel.com>,
Andy Yan <andy.yan@rock-chips.com>,
Ville Syrjala <ville.syrjala@linux.intel.com>
Subject: Re: [PATCH v2 0/3] drm/dp: shared HDR metadata SDP helper, and max bpc for dw-dp
Date: Wed, 9 Sep 2026 18:37:40 +0200 [thread overview]
Message-ID: <20260909163742.37003-1-royalnet026@gmail.com> (raw)
In-Reply-To: <20260909163206.36409-1-royalnet026@gmail.com>
Following up on my own cover letter, where I said the series had not
been built.
It has now. On top of drm-misc-next bf63a72ea005, x86_64 allmodconfig,
building the five objects the series touches with W=1:
drivers/gpu/drm/display/drm_dp_helper.o
drivers/gpu/drm/display/drm_bridge_connector.o
drivers/gpu/drm/drm_connector.o
drivers/gpu/drm/i915/display/intel_dp.o
drivers/gpu/drm/rockchip/dw_dp-rockchip.o
All five build with no errors and no new warnings. intel_dp.o is the one
I most wanted to see, since 1/3 moves code out of it.
To be exact about what this is and is not: it is a compile test only. I
have still not booted this exact series, for the reason given in the
cover - the runtime testing behind v1 was done on a rockchip-devel
kernel carrying the v9 generation of the dw-dp series, and mainline's
dw_dp-rockchip.c is not the file that was exercised. If you want a boot
test on the Orange Pi 5 Plus before taking this, say so and I will do it.
Igor
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2026-09-09 16:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 16:31 [PATCH v2 0/3] drm/dp: shared HDR metadata SDP helper, and max bpc for dw-dp Igor Paunovic
2026-09-09 16:31 ` Igor Paunovic
2026-09-09 16:37 ` Igor Paunovic [this message]
2026-09-09 16:37 ` Igor Paunovic
2026-09-09 17:35 ` Igor Paunovic
2026-09-09 17:35 ` Igor Paunovic
2026-09-09 17:35 ` [PATCH v2 1/3] drm/dp: Add drm_dp_hdr_metadata_infoframe_sdp_pack() Igor Paunovic
2026-09-09 17:35 ` Igor Paunovic
2026-09-09 17:35 ` [PATCH v2 2/3] drm/display: bridge-connector: Preserve max bpc across connector reset Igor Paunovic
2026-09-09 17:35 ` Igor Paunovic
2026-09-09 17:35 ` [PATCH v2 3/3] drm/rockchip: dw_dp: Attach "max bpc" connector property Igor Paunovic
2026-09-09 17:35 ` Igor Paunovic
2026-09-09 17:50 ` sashiko-bot
2026-09-09 19:40 ` Igor Paunovic
2026-09-09 19:40 ` Igor Paunovic
2026-09-10 7:16 ` Chaoyi Chen
2026-09-10 7:16 ` Chaoyi Chen
2026-09-10 7:51 ` Igor Paunovic
2026-09-10 7:51 ` Igor Paunovic
2026-09-10 8:16 ` Chaoyi Chen
2026-09-10 8:16 ` Chaoyi Chen
2026-09-10 12:04 ` Igor Paunovic
2026-09-10 12:04 ` Igor Paunovic
2026-09-10 14:25 ` ✗ LGCI.VerificationFailed: failure for drm/dp: shared HDR metadata SDP helper, and max bpc for dw-dp Patchwork
2026-09-10 15:11 ` Patchwork
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=20260909163742.37003-1-royalnet026@gmail.com \
--to=royalnet026@gmail.com \
--cc=andy.yan@rock-chips.com \
--cc=cristian.ciocaltea@collabora.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-rockchip@lists.infradead.org \
--cc=mripard@kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=ville.syrjala@linux.intel.com \
/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.