From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Rob Herring <robh+dt@kernel.org>,
Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
Cc: arcml <linux-snps-arc@lists.infradead.org>,
lkml <linux-kernel@vger.kernel.org>,
Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH 3/3 v8] ARC: hsdk: initial port for HSDK board
Date: Thu, 31 Aug 2017 10:38:17 -0700 [thread overview]
Message-ID: <c689523e-3fb9-8763-c3ec-83815cadbfd4@synopsys.com> (raw)
In-Reply-To: <20170717173823.lklxhoyylhdxjawa@rob-hp-laptop>
Hi Rob,
On 07/17/2017 10:38 AM, Rob Herring wrote:
> On Wed, Jul 12, 2017 at 12:40:23PM +0300, Eugeniy Paltsev wrote:
>> From: Alexey Brodkin <abrodkin-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
>>
>> 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. We still can use
>> memory region starting at 0x8000_0000 as we reallocate DCCM in our
>> platform code.
>>
>> Note that PAE remapping for DMA clients does not work due to an RTL bug,
>> so CREG_PAE register must be programmed to all zeroes, otherwise it will
>> cause problems with DMA to/from peripherals even if PAE40 is not used.
>>
>> Signed-off-by: Alexey Brodkin <abrodkin-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
>> Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
>> ---
>> Changes v7 -> v8:
>> * DTS: move cpu_intc, idu_intc, arcpct, timer, gfrc nodes to root
>> level and out of the cpus node.
>> * DTS: add vendor-specific compatible for ohci and ehci nodes.
>> * DTS: style fixes
>
> Acked-by: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
>
>> + ohci@60000 {
>> + compatible = "snps,hsdk-v1.0-ohci", "generic-ohci";
>> + reg = <0x60000 0x100>;
>> + interrupts = <15>;
>> + };
>> +
>> + ehci@40000 {
>> + compatible = "snps,hsdk-v1.0-ehci", "generic-ehci";
>> + reg = <0x40000 0x100>;
>> + interrupts = <15>;
>> + };
>
> Of course, now these compatibles need to be documented. You can do that
> in a separate follow-up patch.
Are these v1 suffixes really needed. We don't envision any change to usb IP even
if we were to ever do a respin of the board !
Thx,
-Vineet
prev parent reply other threads:[~2017-08-31 17:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 9:40 [PATCH 0/3 v8] " Eugeniy Paltsev
2017-07-12 9:40 ` [PATCH 1/3 v8] ARC: Set IO-coherency aperture base to LINUX_LINK_BASE Eugeniy Paltsev
2017-08-22 21:44 ` Vineet Gupta
2017-08-25 15:57 ` Eugeniy Paltsev
2017-07-12 9:40 ` [PATCH 2/3 v8] ARC: Decouple linux kernel memory address and link address Eugeniy Paltsev
2017-07-12 9:40 ` [PATCH 3/3 v8] ARC: hsdk: initial port for HSDK board Eugeniy Paltsev
2017-07-17 17:38 ` Rob Herring
2017-08-31 17:38 ` 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=c689523e-3fb9-8763-c3ec-83815cadbfd4@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=devicetree@vger.kernel.org \
--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®