From: marc_gonzalez@sigmadesigns.com (Marc Gonzalez)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 2/2] arm-soc: Add support for arm-based tango4 platforms
Date: Mon, 2 Nov 2015 18:33:22 +0100 [thread overview]
Message-ID: <56379E62.4080704@sigmadesigns.com> (raw)
In-Reply-To: <yw1xfv0o9xr3.fsf@unicorn.mansr.com>
On 02/11/2015 17:22, M?ns Rullg?rd wrote:
> Unless I'm missing something, you should enable the SCU before starting
> secondary CPUs. It's also a good idea to structure the code with
> separate prepare and boot functions even if all the current chips are
> only dual-core.
About the SCU: I will check with the firmware author.
About prepare: this is the firmware's responsibility.
(Not all chips are dual-core, the 8756 is single-core.)
> What about other registers? Does the firmware support setting the
> prefetch control register?
Yes, after masking out some bits.
My port uses the firmware-supplied value.
Regards.
next prev parent reply other threads:[~2015-11-02 17:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 15:17 [PATCH v8 0/2] Sigma Designs Tango4 port Marc Gonzalez
2015-11-02 15:18 ` [PATCH v8 1/2] arm-soc: Import initial tango4 device tree Marc Gonzalez
2015-11-02 16:01 ` Måns Rullgård
2015-11-02 17:11 ` Marc Gonzalez
2015-11-02 17:59 ` Måns Rullgård
2015-11-03 0:57 ` Måns Rullgård
2015-11-02 20:33 ` Florian Fainelli
2015-11-02 15:19 ` [PATCH v8 2/2] arm-soc: Add support for arm-based tango4 platforms Marc Gonzalez
2015-11-02 16:22 ` Måns Rullgård
2015-11-02 17:33 ` Marc Gonzalez [this message]
2015-11-02 18:01 ` Måns Rullgård
2015-11-02 18:26 ` Mark Rutland
2015-11-02 18:30 ` Måns Rullgård
2015-11-02 18:37 ` santosh shilimkar
2015-11-03 8:34 ` Marc Gonzalez
2015-11-03 10:12 ` Måns Rullgård
2015-11-03 16:37 ` santosh shilimkar
2015-11-03 17:04 ` Marc Gonzalez
2015-11-03 18:02 ` Måns Rullgård
2015-11-02 15:52 ` [PATCH v8 0/2] Sigma Designs Tango4 port Marc Gonzalez
2015-11-02 21:40 ` Arnd Bergmann
2015-11-03 9:00 ` Marc Gonzalez
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=56379E62.4080704@sigmadesigns.com \
--to=marc_gonzalez@sigmadesigns.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 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.