public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [linux-sunxi] [u-boot 2/2] sun5i: bump DEBE priority (useful on a10s only)
Date: Mon, 19 Jan 2015 10:16:15 +0100	[thread overview]
Message-ID: <54BCCB5F.6020106@redhat.com> (raw)
In-Reply-To: <CAOMqctQpAQpzHWvbnOZd5NK-KpYvFTx9gFx-WvMN4F+mEE40Uw@mail.gmail.com>

Hi,

On 19-01-15 10:06, Michal Suchanek wrote:
> On 19 January 2015 at 05:29, Siarhei Siamashka
> <siarhei.siamashka@gmail.com> wrote:
>> On Sun, 04 Jan 2015 20:49:38 +0100
>> Hans de Goede <hdegoede@redhat.com> wrote:
>>
>>> Hi,
>>>
>>> On 04-01-15 20:19, Michal Suchanek wrote:
>>>>     Setting magic 'reserved' hpcr bit on sun5i DEBE seems required for
>>>>     smooth HDMI scanout of large frambuffer (eg. 1080p).
>>>>
>>>>     This fix comes at the cost of some overall memory bandwidth so it
>>>>     might be appropriate to detect a10s and only apply there (and not a13).
>>>
>>> Hmm, Sairhei is the expert on this, adding him to the Cc. Sairhei, what
>>> do you think of the proposed change ?
>>
>> I don't have A10s hardware, so have no idea and can't test anything
>> myself.
>>
>> It would be great to have a better description of what exactly is
>> happening before the patch. And precisely how the patch is helping.
>> A description of the test setup and benchmark numbers would be
>> appreciated. And it would be perfect if somebody else could reproduce
>> the test and confirm the results.
>
> The result is that with full HD HDMI output lima-memtester cube jumps
> without the patch and does not jump with the patch. I have only 1 A10s
> board.

Since you're running lima-memtester, I assume you're using a sunxi-3.4
kernel, correct?

Looking at the patch you're not modifying DEBE DRAM priority, but rather
DEFE priority.

Can you check the fex file and see what fb0_scaler_mode_enable is set too ?

If it is not enabled, it is weird that this fix helps, if it is enabled,
then this fix shouldn't be necessary, but maybe things are different on
sun5i vs sun4i.

Regardless can you try with fb0_scaler_mode_enable inverted from what it
is now, it would be good to know if it has any impact on sun5i.

Regards,

Hans

  reply	other threads:[~2015-01-19  9:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1420399561.git.hramrach@gmail.com>
     [not found] ` <4250c53f8df139084acfaad14a88819a600b9965.1420399561.git.hramrach@gmail.com>
2015-01-04 19:49   ` [U-Boot] [linux-sunxi] [u-boot 2/2] sun5i: bump DEBE priority (useful on a10s only) Hans de Goede
2015-01-19  4:29     ` Siarhei Siamashka
2015-01-19  9:06       ` Michal Suchanek
2015-01-19  9:16         ` Hans de Goede [this message]
2015-01-19  9:29           ` Hans de Goede
2015-01-19  9:37             ` Michal Suchanek
2015-01-20  8:16       ` Siarhei Siamashka
2015-01-20 13:16         ` Hans de Goede
2015-01-22  7:30           ` Siarhei Siamashka
2015-01-22 13:26             ` Hans de Goede
2015-01-22 14:43               ` Michal Suchanek
2015-01-22 16:05                 ` Hans de Goede
     [not found] ` <e256647dd7f6457657f560f2b939cea2c6324854.1420399561.git.hramrach@gmail.com>
2015-01-04 19:49   ` [U-Boot] [linux-sunxi] [u-boot 1/2] sunxi: axp152: bump dcdc4 Hans de Goede

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=54BCCB5F.6020106@redhat.com \
    --to=hdegoede@redhat.com \
    --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