From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: claudiu.beznea@microchip.com, boris.brezillon@free-electrons.com,
sam@ravnborg.org, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] drm: atmel-hlcdc: enable clock before configuring timing" failed to apply to 4.19-stable tree
Date: Sun, 9 Feb 2020 13:03:33 -0500 [thread overview]
Message-ID: <20200209180333.GJ3584@sasha-vm> (raw)
In-Reply-To: <158124842070142@kroah.com>
On Sun, Feb 09, 2020 at 12:40:20PM +0100, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 4.19-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From 2c1fb9d86f6820abbfaa38a6836157c76ccb4e7b Mon Sep 17 00:00:00 2001
>From: Claudiu Beznea <claudiu.beznea@microchip.com>
>Date: Wed, 18 Dec 2019 14:28:25 +0200
>Subject: [PATCH] drm: atmel-hlcdc: enable clock before configuring timing
> engine
>
>Changing pixel clock source without having this clock source enabled
>will block the timing engine and the next operations after (in this case
>setting ATMEL_HLCDC_CFG(5) settings in atmel_hlcdc_crtc_mode_set_nofb()
>will fail). It is recomended (although in datasheet this is not present)
>to actually enabled pixel clock source before doing any changes on timing
>enginge (only SAM9X60 datasheet specifies that the peripheral clock and
>pixel clock must be enabled before using LCD controller).
>
>Fixes: 1a396789f65a ("drm: add Atmel HLCDC Display Controller support")
>Signed-off-by: Claudiu Beznea <claudiu.beznea@microchip.com>
>Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
>Cc: Boris Brezillon <boris.brezillon@free-electrons.com>
>Cc: <stable@vger.kernel.org> # v4.0+
>Link: https://patchwork.freedesktop.org/patch/msgid/1576672109-22707-3-git-send-email-claudiu.beznea@microchip.com
I've adjusted context because we don't have:
a6eca2abdd42 ("drm: atmel-hlcdc: add config option for clock selection")
319711f98208 ("drm/atmel-hlcdc: prefer a higher rate clock as pixel-clock base")
and queued it for 4.19-4.4.
--
Thanks,
Sasha
prev parent reply other threads:[~2020-02-09 18:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-09 11:40 FAILED: patch "[PATCH] drm: atmel-hlcdc: enable clock before configuring timing" failed to apply to 4.19-stable tree gregkh
2020-02-09 18:03 ` Sasha Levin [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=20200209180333.GJ3584@sasha-vm \
--to=sashal@kernel.org \
--cc=boris.brezillon@free-electrons.com \
--cc=claudiu.beznea@microchip.com \
--cc=gregkh@linuxfoundation.org \
--cc=sam@ravnborg.org \
--cc=stable@vger.kernel.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