From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] ARM: sun8i: dt: Add mali node
Date: Mon, 30 Jan 2017 10:40:25 -0600 [thread overview]
Message-ID: <CAL_JsqLs8bMjx2AcLePeNSxXDs0UAaReLrfaGRZOEun3tVqwiw@mail.gmail.com> (raw)
In-Reply-To: <20170130140015.dopcfbula6spu2xo@lukather>
On Mon, Jan 30, 2017 at 8:00 AM, Maxime Ripard
<maxime.ripard@free-electrons.com> wrote:
> Hi Rob,
>
> On Fri, Jan 27, 2017 at 02:21:19PM -0600, Rob Herring wrote:
>> On Mon, Jan 23, 2017 at 03:00:46PM +0100, Maxime Ripard wrote:
>> > The A23 and A33 have an ARM Mali 400 GPU. Now that we have a binding, add
>> > it to our DT.
>> >
>> > Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
>> > ---
>> > arch/arm/boot/dts/sun8i-a23-a33.dtsi | 26 ++++++++++++++++++++++++++
>> > 1 file changed, 26 insertions(+), 0 deletions(-)
>> >
>> > diff --git a/arch/arm/boot/dts/sun8i-a23-a33.dtsi b/arch/arm/boot/dts/sun8i-a23-a33.dtsi
>> > index e4991a78ad73..982705719ef2 100644
>> > --- a/arch/arm/boot/dts/sun8i-a23-a33.dtsi
>> > +++ b/arch/arm/boot/dts/sun8i-a23-a33.dtsi
>> > @@ -486,6 +486,32 @@
>> > #size-cells = <0>;
>> > };
>> >
>> > + mali: gpu at 01c40000 {
>>
>> Drop leading 0.
>>
>> > + compatible = "allwinner,sun8i-a23-mali",
>> > + "allwinner,sun7i-a20-mali", "arm,mali-400";
>> > + reg = <0x01c40000 0x10000>;
>>
>> Does this really use 64K or that's just the register spacing? Set it
>> to what's used.
>
> The memory maps in our datasheet allocates 64k for that block. I
> always thought that we had to put the size of the whole memory block
> allocated to that device.
>
> For now, the driver only uses space up to 0xe000 (so we wouldn't
> "waste" a lot of space anyway), but what if at some point the driver
> needs more than what we put in the DT?
Well, it should be what the h/w is, not what the driver needs.
I only asked because 64K spacing of peripherals is becoming common,
but that wastes a bit of virtual address space on 32-bit if really the
h/w registers are only <4KB. Given that it is 0xe000 in this case, it
doesn't really matter here.
Rob
next prev parent reply other threads:[~2017-01-30 16:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 14:00 [PATCH v2 1/2] dt-bindings: gpu: Add Mali Utgard bindings Maxime Ripard
2017-01-23 14:00 ` [PATCH v2 2/2] ARM: sun8i: dt: Add mali node Maxime Ripard
2017-01-27 20:21 ` Rob Herring
2017-01-30 14:00 ` Maxime Ripard
2017-01-30 16:40 ` Rob Herring [this message]
2017-01-27 20:19 ` [PATCH v2 1/2] dt-bindings: gpu: Add Mali Utgard bindings Rob Herring
2017-01-30 13:48 ` Maxime Ripard
2017-01-30 16:24 ` Neil Armstrong
2017-01-31 9:56 ` Maxime Ripard
2017-01-31 10:17 ` Neil Armstrong
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=CAL_JsqLs8bMjx2AcLePeNSxXDs0UAaReLrfaGRZOEun3tVqwiw@mail.gmail.com \
--to=robh@kernel.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).