From: Philipp Zabel <p.zabel@pengutronix.de>
To: Magnus Hörlin <magnus@alefors.se>
Cc: dri-devel@lists.freedesktop.org, imx@lists.linux.dev
Subject: Re: [PATCH] drm/imx/ipuv3: do not adjust hactive for non-8-pixel-aligned modes
Date: Tue, 07 Apr 2026 09:02:00 +0200 [thread overview]
Message-ID: <7ae7cad05e1d0894772bc76d7de242d94ad356da.camel@pengutronix.de> (raw)
In-Reply-To: <20260406153654.2094908-1-magnus@alefors.se>
On Mo, 2026-04-06 at 17:36 +0200, Magnus Hörlin wrote:
> The IPUv3 display driver rounds up hactive to 8-pixel alignment in
> mode_set_nofb(), stealing pixels from the front porch.
> ipu_src_rect_width() applies the same rounding to the IDMAC read
> width. While this keeps the DC and IDMAC in sync, it causes the
> display to receive more active pixels than the mode specifies.
>
> On fixed-pixel displays whose native width is not 8-pixel aligned
> (e.g. 854x480), the extra pixels cause visible skewing: each
> scanline is offset, making vertical lines lean.
>
> Remove both alignment overrides. The IDMAC and DC now use the exact
> mode width.
This partially reverts 94dfec48fca7 ("drm/imx: Add 8 pixel alignment
fix") [1] without mentioning it, so I assume this patch breaks imx6dl-
b105pv2.
[1] https://lore.kernel.org/all/20210428222953.235280-6-sebastian.reichel@collabora.com/
> The DMA burst size is already adapted to arbitrary
> widths by ipu_calculate_bursts(), so no alignment is required at
> the pixel level.
The reference manual mentions burst size (NPB) has to be a multiple of
8 pixels at least for planar and semi-planar YUV formats. Without the
width alignment, ipu_calculate_bursts() doesn't guarantee this.
> Demote the DC warning about non-8-aligned hactive to dev_dbg, since
> it is informational rather than indicative of a problem.
>
> Signed-off-by: Magnus Hörlin <magnus@alefors.se>
I wonder why the 8-pixel alignment check in ipu_di_adjust_videomode()
which has not been removed, doesn't cause ipu_crtc_mode_fixup() to
fail.
regards
Philipp
next prev parent reply other threads:[~2026-04-07 7:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 15:36 [PATCH] drm/imx/ipuv3: do not adjust hactive for non-8-pixel-aligned modes Magnus Hörlin
2026-04-07 7:02 ` Philipp Zabel [this message]
2026-04-12 4:28 ` Claude review: " Claude Code Review Bot
2026-04-12 4:28 ` Claude Code Review Bot
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=7ae7cad05e1d0894772bc76d7de242d94ad356da.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=imx@lists.linux.dev \
--cc=magnus@alefors.se \
/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