From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
<linux-snps-arc@lists.infradead.org>
Cc: <linux-kernel@vger.kernel.org>,
Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v4] hsdk: initial port for HSDK board
Date: Tue, 6 Jun 2017 15:15:10 -0700 [thread overview]
Message-ID: <c416d6e1-f4ae-e698-d96c-33390f062661@synopsys.com> (raw)
In-Reply-To: <1496692249-11699-1-git-send-email-abrodkin@synopsys.com>
On 06/05/2017 12:50 PM, Alexey Brodkin wrote:
> This initial port adds support of ARC HS Development Kit board with some
> basic features such serial port, USB, SD/MMC and Ethernet.
>
> Essentially we run Linux kernel on all 4 cores (i.e. utilize SMP) and
> heavily use IO Coherency for speeding-up DMA-aware peripherals.
>
> Note as opposed to other ARC boards we link Linux kernel to
> 0x9000_0000 intentionally because cores 1 and 3 configured with DCCM
> situated at our more usual link base 0x8000_0000.
>
> Signed-off-by: Eugeniy Paltsev <paltsev@synopsys.com>
> Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
> Cc: Vineet Gupta <vgupta@synopsys.com>
> Cc: Rob Herring <robh+dt@kernel.org>
> ---
>
> Changes v3 -> v4:
> * Removed senseless "ranges" property from "memory" node in .dts
> * Refined early-boot code:
> - CREG_PAE should be set only once thus master does that in init_early()
> - ICCM relocation should be done on each and every core that sports ICCM
> so we leave it in init_per_cpu(). Even though init_per_cpu() gets called
> on the master core pretty late still it is way much earlier than that
> moment when it might affect us - as it only huts us when addresses in
> 0x7z-0x7fff_ffff range are used, i.e. virtual addresses that we don't
> use during init. This also makes code much cleaner compared to
> additional check in case of master etc.
So you are assuming that vmalloc machinery would not have kicked in by then i.e.
by the time of irq_init() i.e. - perhaps that is true. Lets go with what you have
now....
-Vineet
prev parent reply other threads:[~2017-06-06 22:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 19:50 Alexey Brodkin
2017-06-06 22:15 ` Vineet Gupta [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=c416d6e1-f4ae-e698-d96c-33390f062661@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=robh+dt@kernel.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
all inboxes | Powered by JetHome®