From: Greg KH <gregkh@linuxfoundation.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [stable 4.19][PATCH 1/4] ARM: dts: am4372: Set memory bandwidth limit for DISPC
Date: Wed, 16 Oct 2019 11:31:21 -0700 [thread overview]
Message-ID: <20191016183121.GD801860@kroah.com> (raw)
In-Reply-To: <20191015065937.23169-1-mathieu.poirier@linaro.org>
On Tue, Oct 15, 2019 at 12:59:34AM -0600, Mathieu Poirier wrote:
> From: Peter Ujfalusi <peter.ujfalusi@ti.com>
>
> commit f90ec6cdf674248dcad85bf9af6e064bf472b841 upstream
>
> Set memory bandwidth limit to filter out resolutions above 720p@60Hz to
> avoid underflow errors due to the bandwidth needs of higher resolutions.
>
> am43xx can not provide enough bandwidth to DISPC to correctly handle
> 'high' resolutions.
>
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
> Signed-off-by: Tony Lindgren <tony@atomide.com>
> Cc: stable <stable@vger.kernel.org> # 4.19
> Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>
> ---
> arch/arm/boot/dts/am4372.dtsi | 2 ++
> 1 file changed, 2 insertions(+)
What about 5.3? Is this ok there?
thanks,
greg k-h
next prev parent reply other threads:[~2019-10-16 18:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 6:59 [stable 4.19][PATCH 1/4] ARM: dts: am4372: Set memory bandwidth limit for DISPC Mathieu Poirier
2019-10-15 6:59 ` [stable 4.19][PATCH 2/4] ASoC: pcm3168a: The codec does not support S32_LE Mathieu Poirier
2019-10-15 6:59 ` [stable 4.19][PATCH 3/4] arm64: dts: ti: k3-am65-main: Fix gic-its node unit-address Mathieu Poirier
2019-10-15 6:59 ` [stable 4.19][PATCH 4/4] usb: gadget: udc: core: Fix segfault if udc_bind_to_driver() for pending driver fails Mathieu Poirier
2019-10-16 18:31 ` Greg KH [this message]
2019-10-17 16:50 ` [stable 4.19][PATCH 1/4] ARM: dts: am4372: Set memory bandwidth limit for DISPC Mathieu Poirier
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=20191016183121.GD801860@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.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;
as well as URLs for NNTP newsgroup(s).