From: Grant Likely <grant.likely@linaro.org>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [linux-sunxi] Re: [PATCH v3 1/4] dt-bindings: simplefb: Specify node location and handoff relate
Date: Thu, 13 Nov 2014 16:07:18 +0000 [thread overview]
Message-ID: <CACxGe6tA90T+nj5aBbWWd4SJVofzKLY9AS2cXeqUJyAVMYECbw@mail.gmail.com> (raw)
In-Reply-To: <5464D3C7.7060707@ti.com>
On Thu, Nov 13, 2014 at 3:52 PM, Tomi Valkeinen <tomi.valkeinen@ti.com> wrote:
> On 13/11/14 16:46, Hans de Goede wrote:
>> Hi,
>>
>> On 11/13/2014 03:28 PM, Tomi Valkeinen wrote:
>>> On 13/11/14 15:34, Hans de Goede wrote:
>>>
>>>> +chosen {
>>>> + framebuffer0: framebuffer@5fc00000 {
>>>> compatible = "simple-framebuffer";
>>>> - reg = <0x1d385000 (1600 * 1200 * 2)>;
>>>> + reg = <0x5fc00000 (4096 * 1024)>;
>>>
>>> Was there a reason for this change?
>>
>> I changed the node name to match the new bindings text which
>> specifies that the node name must be framebuffer@<address>,
>> while at it I've taken a real world address range.
>>
>> I assume you refer to the bit where the size of the reg property
>> is changed ? That indeed is not really necessary.
>
> Yes, I meant the size of the reg prop. As this is an example, I think it
> should be as clear as possible.
>
> I guess a valid use case here is to set the size to larger-than-needed,
> so that it gets preallocated and you don't need to worry about getting
> the memory later when the system has already been running for a longer
> time. But if that's the case in this example, I think it would be better
> to describe it explicitly.
Besides, we already have a mechanism for that called /reserved-memory.
Any memory used by a framebuffer needs to be described in the reserved
map anyway, and that region can be made larger than the firmware
configured framebuffer.
g.
prev parent reply other threads:[~2014-11-13 16:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 13:34 [PATCH v3 1/4] dt-bindings: simplefb: Specify node location and handoff related properties Hans de Goede
2014-11-13 13:34 ` [PATCH v3 2/4] simplefb: Add support for enumerating simplefb dt nodes in /chosen Hans de Goede
2014-11-13 13:34 ` [PATCH v3 3/4] simplefb: Change simplefb_init from module_init to fs_initcall Hans de Goede
2014-11-13 14:32 ` Tomi Valkeinen
2014-11-13 14:47 ` Hans de Goede
2014-11-13 13:34 ` [PATCH v3 4/4] fbcon: Change fbcon_init " Hans de Goede
2014-11-13 14:34 ` Tomi Valkeinen
2014-11-13 14:28 ` [PATCH v3 1/4] dt-bindings: simplefb: Specify node location and handoff related properties Tomi Valkeinen
2014-11-13 14:46 ` [linux-sunxi] Re: [PATCH v3 1/4] dt-bindings: simplefb: Specify node location and handoff relate Hans de Goede
2014-11-13 15:52 ` Tomi Valkeinen
2014-11-13 16:07 ` Grant Likely [this message]
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=CACxGe6tA90T+nj5aBbWWd4SJVofzKLY9AS2cXeqUJyAVMYECbw@mail.gmail.com \
--to=grant.likely@linaro.org \
--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).