From: Liu Ying <victor.liu@nxp.com>
To: Paul Pu <hui.pu@gehealthcare.com>,
p.zabel@pengutronix.de,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Sasha Levin <sashal@kernel.org>,
Lucas Stach <l.stach@pengutronix.de>
Cc: HuanWang@gehealthcare.com, taowang@gehealthcare.com,
sebastian.reichel@collabora.com, ian.ray@gehealthcare.com,
stable@vger.kernel.org, dri-devel@lists.freedesktop.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm: imx: ipuv3-plane: fix HDMI cannot work for odd screen resolutions
Date: Wed, 4 Sep 2024 13:40:10 +0800 [thread overview]
Message-ID: <01b335a8-0802-453b-a792-ceb5c54a41aa@nxp.com> (raw)
In-Reply-To: <20240904024315.120-1-hui.pu@gehealthcare.com>
Hi Paul,
Thanks for your patch.
On 09/04/2024, Paul Pu wrote:
> This changes the judgement of if needing to round up the width or not,
> from using the `dp_flow` to the plane's type.
>
> The `dp_flow` can be -22(-EINVAL) even the plane is a PRIMARY one.
s/even/even if/
> See `client_reg[]` in `ipu-common.c`.
>
> [ 0.605141] [drm:ipu_plane_init] channel 28, dp flow -22, possible_crtcs=0x0
>
> Per the commit message in commit: 71f9fd5bcf09, using the plane type for
Commit 71f9fd5bcf09 is a commit that only exists in downstream kernel.
> judging if rounding up is needed is correct.
>
> Fixes: 71f9fd5bcf09 ("drm/imx: ipuv3-plane: Fix overlay plane width")
Commit 4333472f8d7b is the one to fix in upstream kernel.
s/71f9fd5bcf09/4333472f8d7b/
> Cc: stable@vger.kernel.org
Better to mark the versions for backporting the fix.
Cc: stable@vger.kernel.org # 6.3+
>
No blank line between tags.
> Signed-off-by: Paul Pu <hui.pu@gehealthcare.com>
> ---
> drivers/gpu/drm/imx/ipuv3/ipuv3-plane.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Maybe, the patch subject can be something like:
drm/imx/ipuv3: ipuv3-plane: Round up plane width for IPUV3_CHANNEL_MEM_DC_SYNC
You may find example patch subject prefixes by looking at previous commits
which touch the same file, like
commit 71e3657cb126 ("drm/imx/ipuv3: ipuv3-plane: reuse local variable height
in atomic_update")
You may specify those fixed odd screen resolutions of your "HDMI" case in commit
message.
>
> diff --git a/drivers/gpu/drm/imx/ipuv3/ipuv3-plane.c b/drivers/gpu/drm/imx/ipuv3/ipuv3-plane.c
> index 704c549750f9..cee83ac70ada 100644
> --- a/drivers/gpu/drm/imx/ipuv3/ipuv3-plane.c
> +++ b/drivers/gpu/drm/imx/ipuv3/ipuv3-plane.c
> @@ -614,7 +614,7 @@ static void ipu_plane_atomic_update(struct drm_plane *plane,
> break;
> }
>
> - if (ipu_plane->dp_flow == IPU_DP_FLOW_SYNC_BG)
> + if (ipu_plane->base.type == DRM_PLANE_TYPE_PRIMARY)
plane->type is more readable.
> width = ipu_src_rect_width(new_state);
> else
> width = drm_rect_width(&new_state->src) >> 16;
>
> base-commit: 431c1646e1f86b949fa3685efc50b660a364c2b6
--
Regards,
Liu Ying
next prev parent reply other threads:[~2024-09-04 5:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 2:43 [PATCH] drm: imx: ipuv3-plane: fix HDMI cannot work for odd screen resolutions Paul Pu
2024-09-04 5:40 ` Liu Ying [this message]
2024-09-04 7:44 ` Pu, Hui
2024-09-04 6:21 ` Greg KH
2024-09-04 7:47 ` Pu, Hui
2024-09-04 7:54 ` [PATCH v2] drm/imx/ipuv3: ipuv3-plane: Round up plane width for IPUV3_CHANNEL_MEM_DC_SYNC Paul Pu
2024-09-04 8:31 ` Philipp Zabel
2024-09-04 8:48 ` Liu Ying
2024-09-04 9:07 ` Pu, Hui
2024-09-04 9:13 ` Greg KH
2024-09-04 9:27 ` Liu Ying
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=01b335a8-0802-453b-a792-ceb5c54a41aa@nxp.com \
--to=victor.liu@nxp.com \
--cc=HuanWang@gehealthcare.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=hui.pu@gehealthcare.com \
--cc=ian.ray@gehealthcare.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=s.hauer@pengutronix.de \
--cc=sashal@kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=shawnguo@kernel.org \
--cc=stable@vger.kernel.org \
--cc=taowang@gehealthcare.com \
--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