From: Maxime Ripard <mripard@kernel.org>
To: Icenowy Zheng <icenowy@aosc.io>
Cc: David Airlie <airlied@linux.ie>,
linux-sunxi@googlegroups.com, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, Chen-Yu Tsai <wens@csie.org>,
Jagan Teki <jagan@amarulasolutions.com>,
Daniel Vetter <daniel@ffwll.ch>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/3] drm/sun4i: dsi: fix the overhead of the horizontal front porch
Date: Mon, 7 Oct 2019 13:59:41 +0200 [thread overview]
Message-ID: <20191007115941.psgcn4dl5r5wz7eb@gilmour> (raw)
In-Reply-To: <20191006160303.24413-3-icenowy@aosc.io>
[-- Attachment #1.1: Type: text/plain, Size: 374 bytes --]
On Mon, Oct 07, 2019 at 12:03:01AM +0800, Icenowy Zheng wrote:
> The formula in the BSP kernel indicates that a 16-byte overhead is used
> when sending the HFP. However, this value is currently set to 6 in the
> sun6i_mipi_dsi driver, which makes some panels flashing.
>
> Fix this overhead value.
>
> Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
Applied, thanks
Maxime
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-10-07 11:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-06 16:02 [PATCH v2 0/3] drm/sun4i: dsi: misc fixes Icenowy Zheng
2019-10-06 16:03 ` [PATCH v2 1/3] drm/sun4i: dsi: Fix video start delay computation Icenowy Zheng
2019-10-07 11:51 ` Maxime Ripard
2019-10-08 3:06 ` Icenowy Zheng
2019-10-08 5:57 ` Maxime Ripard
2019-10-06 16:03 ` [PATCH v2 2/3] drm/sun4i: dsi: fix the overhead of the horizontal front porch Icenowy Zheng
2019-10-07 11:59 ` Maxime Ripard [this message]
2019-10-06 16:03 ` [PATCH v2 3/3] drm/sun4i: sun6i_mipi_dsi: fix DCS long write packet length Icenowy Zheng
2019-10-07 12:07 ` 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=20191007115941.psgcn4dl5r5wz7eb@gilmour \
--to=mripard@kernel.org \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=icenowy@aosc.io \
--cc=jagan@amarulasolutions.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=wens@csie.org \
/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