linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: p.zabel@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 2/2] ARM: imx6q: Mark VPU and IPU AXI transfers as cacheable, increase IPU priority
Date: Fri, 21 Feb 2014 11:28:16 +0100	[thread overview]
Message-ID: <1392978496.3091.9.camel@pizza.hi.pengutronix.de> (raw)
In-Reply-To: <20140221021947.GR3010@S2101-09.ap.freescale.net>

Hi Shawn,

Am Freitag, den 21.02.2014, 10:19 +0800 schrieb Shawn Guo:
> On Thu, Feb 20, 2014 at 12:44:33PM +0100, Philipp Zabel wrote:
> > This is needed so that the IPU framebuffer scanout cannot be
> > starved by VPU or GPU activity.
> > Some boards like the SabreLite and SabreSD seem to set this in
> > the DCD already, but the documented register reset values do not
> > contain the necessary settings.
> > 
> > Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> 
> I'm fine with the patches, but not sure if I should just apply them
> since you add 'RFC' tag in there.

I'm not sure whether this specific fixed QoS configuration should be
imposed on everyone. OTOH, following the principle of least surprise,
it's probably better to have this here, out in the open, than included
hidden in bootloader DCD tables (or not, depending on the board).
So if nobody objects, feel free to apply them.

regards
Philipp

  reply	other threads:[~2014-02-21 10:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20 11:44 [RFC PATCH 1/2] ARM: imx6q: Add GPR6 and GPR7 register definitions for iomuxc gpr Philipp Zabel
2014-02-20 11:44 ` [RFC PATCH 2/2] ARM: imx6q: Mark VPU and IPU AXI transfers as cacheable, increase IPU priority Philipp Zabel
2014-02-20 13:34   ` Fabio Estevam
2014-02-21  2:19   ` Shawn Guo
2014-02-21 10:28     ` Philipp Zabel [this message]
2014-02-24  2:03       ` Shawn Guo
2014-02-24  9:32         ` Philipp Zabel

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=1392978496.3091.9.camel@pizza.hi.pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --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;
as well as URLs for NNTP newsgroup(s).