linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 3/3] arm64: dts: add Hi6220 mailbox node
Date: Tue, 25 Aug 2015 15:13:26 +0100	[thread overview]
Message-ID: <55DC7806.2010003@arm.com> (raw)
In-Reply-To: <20150825140450.GB28262@leoy-linaro>



On 25/08/15 15:04, Leo Yan wrote:
> Hi Sudeep,
>
> On Tue, Aug 25, 2015 at 12:36:12PM +0100, Sudeep Holla wrote:
>>
>>
>> On 19/08/15 10:37, Leo Yan wrote:
>>> On Hi6220, below memory regions in DDR have specific purpose:
>>>
>>>    0x05e0,0000 - 0x05ef,ffff: For MCU firmware using at runtime;
>>>    0x0740,f000 - 0x0740,ffff: For MCU firmware's section;
>>>    0x06df,f000 - 0x06df,ffff: For mailbox message data.
>>>
>>
>> Unless I am reading the DTS file completely wrong, I don't think the
>> above memory regions are in DDR as per the memory node.
>
> i'm not sure if understand correctly for your question; Hikey board
> has DDR 1GB at 0x0, but there have some memory regions are used for MCU.
>

Ah, I misread the address range, left the leading zero and assumed they
are not in DDR range. Sorry for the noise.

Regards,
Sudeep

      reply	other threads:[~2015-08-25 14:13 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19  9:37 [PATCH v1 0/3] mailbox: hisilicon: add Hi6220 mailbox driver Leo Yan
2015-08-19  9:37 ` [PATCH v1 1/3] dt-bindings: mailbox: Document " Leo Yan
2015-08-25 11:17   ` Sudeep Holla
2015-08-25 13:01     ` Leo Yan
2015-08-19  9:37 ` [PATCH v1 2/3] mailbox: Hi6220: add " Leo Yan
2015-08-19  9:37 ` [PATCH v1 3/3] arm64: dts: add Hi6220 mailbox node Leo Yan
2015-08-21 18:40   ` Mark Rutland
2015-08-22 13:30     ` Leo Yan
2015-08-24  3:27       ` Leo Yan
2015-08-24  9:18     ` Leo Yan
2015-08-24  9:51       ` Mark Rutland
2015-08-24 10:19         ` Haojian Zhuang
2015-08-24 11:49           ` Leif Lindholm
2015-08-25  8:13             ` Haojian Zhuang
2015-08-25  9:46               ` Leif Lindholm
2015-08-25 10:15                 ` Haojian Zhuang
2015-08-25 10:40                   ` Leif Lindholm
2015-08-25 10:42                   ` Mark Rutland
2015-08-25 13:43                     ` Haojian Zhuang
2015-08-25 14:24                       ` Leif Lindholm
2015-08-25 14:51                         ` Ard Biesheuvel
2015-08-25 15:37                           ` Leif Lindholm
2015-08-25 15:45                             ` Ard Biesheuvel
2015-08-26  2:41                             ` Haojian Zhuang
2015-08-25 16:00                       ` Leo Yan
2015-08-26  1:25                         ` Haojian Zhuang
2015-08-26  6:59                           ` Leo Yan
2015-08-27 16:31                             ` Mark Rutland
2015-08-28  6:37                               ` Leo Yan
2015-08-27 15:54                           ` Daniel Thompson
2015-08-27 16:46                           ` Mark Rutland
2015-08-24 12:48           ` Mark Rutland
2015-08-25  8:04             ` Haojian Zhuang
2015-08-25 11:09               ` Mark Rutland
2015-08-25 11:36   ` Sudeep Holla
2015-08-25 14:04     ` Leo Yan
2015-08-25 14:13       ` Sudeep Holla [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=55DC7806.2010003@arm.com \
    --to=sudeep.holla@arm.com \
    --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).