From: John Crispin <blogic@openwrt.org>
To: Andrew Bresticker <abrestic@chromium.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: [PATCH 1/2] MIPS: ralink: add gic support
Date: Thu, 16 Oct 2014 11:06:25 +0200 [thread overview]
Message-ID: <543F8A91.9050602@openwrt.org> (raw)
In-Reply-To: <CAL1qeaHPSdLwec5-V8PHLuyicgNUF74vO0gY7Y7U2k-etQ7eBw@mail.gmail.com>
Hi Andrew,
>> +static int __init
>> +of_gic_init(struct device_node *node,
>> + struct device_node *parent)
>> + if (of_address_to_resource(node, 2, &gcmp))
>> + panic("Failed to get gic memory range");
>> + if (request_mem_region(gcmp.start, resource_size(&gcmp),
>> + gcmp.name) < 0)
>> + panic("Failed to request gcmp memory");
> Ah, so this SoC has a CM2 as well. Is it at the address reported by
> C0_CMGCRBase? If so, then mips_cm_probe() will be able to find it and
> set it up. Otherwise, device-tree based probing should probably be
> added to the mips-cm driver.
i change my code and made use of mips-cm. unit boots fine now and indeed
C0_CMGCRBase holds the valid address. I will look into updating the gic
code to use the generic driver once i cleaned up the remainig mt7621
patches.
i had to apply a hack to mips-cm.c to disable the "disable CM regions"
code, this deadlocked the mt7621. i will send a separate regarding this
in a sec.
John
prev parent reply other threads:[~2014-10-16 9:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 9:34 [PATCH 1/2] MIPS: ralink: add gic support John Crispin
2014-10-10 9:34 ` [PATCH 2/2] MIPS: ralink: add MT7621 support John Crispin
2014-10-10 17:29 ` Andrew Bresticker
2014-10-10 17:01 ` [PATCH 1/2] MIPS: ralink: add gic support Andrew Bresticker
2014-10-10 17:36 ` John Crispin
2014-10-16 9:06 ` John Crispin [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=543F8A91.9050602@openwrt.org \
--to=blogic@openwrt.org \
--cc=abrestic@chromium.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.