From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/4] tegra: video: Always use write-through cache on LCD
Date: Mon, 18 Jan 2016 13:07:10 -0700 [thread overview]
Message-ID: <569D45EE.4020700@wwwdotorg.org> (raw)
In-Reply-To: <1452803219-16675-4-git-send-email-sjg@chromium.org>
On 01/14/2016 01:26 PM, Simon Glass wrote:
> This seems to give the best performance, so let's use it always.
I thought we chose the current cache mode due to display corruption
issues with other modes, but I tested a change that I believe does the
same as this change on Seaboard without any apparent issue so,
Acked-by: Stephen Warren <swarren@nvidia.com>
next prev parent reply other threads:[~2016-01-18 20:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 20:26 [U-Boot] [PATCH 0/4] tegra: Move tegra20 towards the 'new' display bindings Simon Glass
2016-01-14 20:26 ` [U-Boot] [PATCH 1/4] tegra: dts: Sync seaboard device tree file with Linux Simon Glass
2016-01-18 19:32 ` Stephen Warren
2016-01-19 2:01 ` Simon Glass
2016-01-14 20:26 ` [U-Boot] [PATCH 2/4] video: tegra: Move to using simple-panel and pwm-backlight Simon Glass
2016-01-18 19:43 ` Stephen Warren
2016-01-19 2:08 ` Simon Glass
2016-01-19 16:49 ` Stephen Warren
2016-01-20 4:33 ` Simon Glass
2016-01-14 20:26 ` [U-Boot] [PATCH 3/4] tegra: video: Always use write-through cache on LCD Simon Glass
2016-01-18 20:07 ` Stephen Warren [this message]
2016-01-20 14:53 ` Thierry Reding
2016-01-20 16:18 ` Simon Glass
2016-01-14 20:26 ` [U-Boot] [PATCH 4/4] fdt: Drop some unused compatible strings Simon Glass
2016-01-14 20:34 ` [U-Boot] [PATCH 0/4] tegra: Move tegra20 towards the 'new' display bindings Lucas Stach
2016-01-14 23:12 ` Simon Glass
2016-01-18 19:52 ` Stephen Warren
2016-01-19 1:58 ` Simon Glass
2016-01-19 16:47 ` Stephen Warren
2016-01-20 15:37 ` Thierry Reding
2016-01-20 16:18 ` Simon Glass
2016-01-18 19:57 ` Stephen Warren
2016-01-19 1:58 ` Simon Glass
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=569D45EE.4020700@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.de \
/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