From: maxime.ripard@bootlin.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] drm/sun4i: Remove R40 display pipeline compatibles
Date: Thu, 30 Aug 2018 10:13:42 +0200 [thread overview]
Message-ID: <20180830081342.o6ovbkaumlzbhxwk@flea> (raw)
In-Reply-To: <20180827083950.602-1-wens@csie.org>
On Mon, Aug 27, 2018 at 04:39:50PM +0800, Chen-Yu Tsai wrote:
> Two patches from the R40 display pipeline support series weren't applied
> with the rest of the series. When they did get applied, the -rc6
> deadline for drm-misc-next had past, so they didn't get into 4.19-rc1
> with the rest of the series. However, the two patches are crucial in
> the parsing of the R40's display pipeline graph in the device tree.
> Without them, the driver crashes because it can't follow the odd graph
> structure.
>
> This patch removes the R40 compatibles from the sun4i-drm driver,
> effectively disabling DRM support for the R40 for one release cycle.
> This will prevent the driver from crashing upon probing.
>
> The compatibles should be reinstated for the next release.
>
> Signed-off-by: Chen-Yu Tsai <wens@csie.org>
> ---
>
> This is for 4.19-rc to fix the boot crash seen on the R40.
>
> This should go in drm-misc-fixes and into Linus' tree ASAP.
> Once merged, the branch should also be merged into drm-misc-next,
> and then we can revert it.
Applied, thanks!
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180830/c8ffe0df/attachment-0001.sig>
prev parent reply other threads:[~2018-08-30 8:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 8:39 [PATCH] drm/sun4i: Remove R40 display pipeline compatibles Chen-Yu Tsai
2018-08-30 8:13 ` Maxime Ripard [this message]
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=20180830081342.o6ovbkaumlzbhxwk@flea \
--to=maxime.ripard@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.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