From: Scott Wood <oss@buserror.net>
To: Alessio Igor Bogani <alessio.bogani@elettra.eu>,
Kumar Gala <galak@kernel.crashing.org>,
linuxppc-dev@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/1] powerpc/86xx: Add support for Emerson/Artesyn MVME7100
Date: Wed, 20 Apr 2016 18:04:00 -0500 [thread overview]
Message-ID: <1461193440.32510.211.camel@buserror.net> (raw)
In-Reply-To: <1461146533-9500-1-git-send-email-alessio.bogani@elettra.eu>
On Wed, 2016-04-20 at 12:02 +0200, Alessio Igor Bogani wrote:
> Add support for the Artesyn MVME7100 Single Board Computer.
>
> The MVME7100 is a 6U form factor VME64 computer with:
>
> - A two e600 cores Freescale MPC8641D CPU
> - 2 GB of DDR2 onboard memory
> - Four Gigabit Ethernets
> - Five 16550 compatible UARTs
> - One USB 2.0 port
> - Two PCI/PCI eXpress Mezzanine Card (PMC/XMC) Slots
> - A DS1375 Real Time Clock (RTC)
> - 512 KB of Non-Volatile Memory (NVRAM)
> - Two 64 KB EEPROMs
> - 128 MB NOR and 4/8 GB NAND Flash
>
> This patch is based on linux-4.6-rc4 and has been only boot tested.
>
> Signed-off-by: Alessio Igor Bogani <alessio.bogani@elettra.eu>
> ---
> This patch requires
> https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-April/141813.html
> to be built and
> https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-April/141980.html to
> work correctly.
>
> v2 -> v3
> Simplify device tree using pci1 definition from the header file
> as suggested bt Scott Wood
> Move assembly code into a separated file as suggested by Scott Wood
> Increase from 2 to 5 the number of UARTs
>
> v1 -> v2
> Fix BCSR handling
> Add missing @interrupt-cells in the device tree
> to avoid 'of_irq_parse_pci() failed with rc=-22'
> Reduce from 3 to 2 the PCI windows to avoid
> 'Ran out of outbound PCI ATMUs for IO resource'
>
> Limitations:
> This patch covers only models 171 and 173
> No plans to support CPLD timers
>
> Know issues:
> All four PHYs work in polling mode
>
> Configuration is missing for:
> PCI IDSEL and PCI Interrupt definition
>
> Support is missing for:
> Cache and memory controllers (which are very similar to the 85xx ones
> but right now I don't know if we can re-use their support)
> Watchdog, USB, NVRAM, NOR, NAND, EEPROMs, VME, PMC/XMC and RTC
All of the above other than the changelog should go above the --- line
Until you figure out the PCI interrupt mapping, the PCI nodes should be marked
disabled. Likewise anything else that has an incorrect/incomplete device tree
node.
-Scott
next prev parent reply other threads:[~2016-04-20 23:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <460384482-21320-1-git-send-email-alessio.bogani@elettra.eu>
2016-04-18 7:57 ` [PATCH v2 1/1] powerpc/86xx: Add support for Emerson/Artesyn MVME7100 Alessio Igor Bogani
2016-04-19 4:26 ` Scott Wood
2016-04-19 8:33 ` Alessio Igor Bogani
2016-04-19 21:33 ` Scott Wood
2016-04-20 8:18 ` [PATCH v1 1/1] powerpc/86xx: Mode pci1 definition to the include file Alessio Igor Bogani
2016-04-20 10:02 ` [PATCH v3 1/1] powerpc/86xx: Add support for Emerson/Artesyn MVME7100 Alessio Igor Bogani
2016-04-20 23:04 ` Scott Wood [this message]
2016-04-27 8:35 ` [PATCH v4 " Alessio Igor Bogani
2016-05-16 23:41 ` [v4,1/1] " Scott Wood
2016-05-30 9:46 ` Alessio Igor Bogani
2016-05-30 9:47 ` [PATCH v5 1/1] " Alessio Igor Bogani
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=1461193440.32510.211.camel@buserror.net \
--to=oss@buserror.net \
--cc=alessio.bogani@elettra.eu \
--cc=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).