Linus Walleij writes:
> On Thu, Jan 25, 2018 at 4:46 AM, Eric Anholt wrote:
>
>>> + pl111_choose_max_resolution(dev, priv->memory_bw,
>>> + &mode_config->max_width,
>>> + &mode_config->max_height, &bpp);
>>> + dev_info(dev->
On Fri, Jan 26, 2018 at 2:27 PM, Linus Walleij wrote:
> On Thu, Jan 25, 2018 at 4:46 AM, Eric Anholt wrote:
>
>>> + pl111_choose_max_resolution(dev, priv->memory_bw,
>>> + &mode_config->max_width,
>>> + &mode_config->max_height,
On Thu, Jan 25, 2018 at 4:46 AM, Eric Anholt wrote:
>> + pl111_choose_max_resolution(dev, priv->memory_bw,
>> + &mode_config->max_width,
>> + &mode_config->max_height, &bpp);
>> + dev_info(dev->dev, "cap resolution at %u x %u
Linus Walleij writes:
> We were previously selecting 1024x768 and 32BPP as the default
> set-up for the PL111 consumers.
>
> This does not work on elder systems: the device tree bindings
> support a property "max-memory-bandwidth" in bytes/second that
> states that if you exceed this the memory b
We were previously selecting 1024x768 and 32BPP as the default
set-up for the PL111 consumers.
This does not work on elder systems: the device tree bindings
support a property "max-memory-bandwidth" in bytes/second that
states that if you exceed this the memory bus will saturate.
The result is fli
