linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: robh+dt@kernel.org, arnd@arndb.de,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, amit.kucheria@linaro.org,
	darren.tsao@bitmain.com, haitao.suo@bitmain.com
Subject: Re: [PATCH 0/5] Add initial Bitmain BM1880 SoC/Board support
Date: Sat, 26 Jan 2019 20:47:33 +0530	[thread overview]
Message-ID: <20190126151733.GA15434@Mani-XPS-13-9360> (raw)
In-Reply-To: <20190126150320.GB20679@lunn.ch>

Hi Andrew,

On Sat, Jan 26, 2019 at 04:03:20PM +0100, Andrew Lunn wrote:
> On Sat, Jan 26, 2019 at 09:40:36AM +0530, Manivannan Sadhasivam wrote:
> > Hello,
> > 
> > This patchset adds initial support for Bitmain BM1880 SoC and Sophon
> > Edge board. BM1880 SoC consists of a Dual Core ARM Cortex A53 Application
> > processor subsystem, a single core RISC-V subsystem and a Tensor
> > Processor subsystem.
> 
> Hi Manivannan
> 
> Interesting combination of CPUs. 
> 
> > This patchset adds support for only ARM Cortex A53 Application
> > processor subsystem with UART, which enables the board to boot into
> > initramfs with 2 CPUs.
> 
> Looking forward, what sharing do you expect at the device tree level?
> 
> Looking at 
> 
> https://sophon-file.bitmain.com.cn/sophon-prod/drive/18/11/06/19/BM1880%20product%20brief%20V0.04_Chinese%20versionV0.06.pdf
> 
> it appears all the devices can be shared between the CPUs. So do you
> plan to have a shared .dtsi file somewhere? 
> 
> Is ARCH_BITMAIN going to be both ARM64 and RISC-V?
> 

We don't have any plan to add support for RISC-V subsystem. Moreover,
from the SoC product brief it look like the RISC-V core is a MCU grade
core, so I doubt whether we can run linux on it! It might be a candidate
for RTOS.

For now, ARCH_BITMAIN is going to have only ARM64 support.

Thanks,
Mani

>    Thanks
> 	Andrew

  reply	other threads:[~2019-01-26 15:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-26  4:10 [PATCH 0/5] Add initial Bitmain BM1880 SoC/Board support Manivannan Sadhasivam
2019-01-26  4:10 ` [PATCH 1/5] dt-bindings: arm: Document Bitmain BM1880 SoC Manivannan Sadhasivam
2019-01-26 19:47   ` Rob Herring
2019-01-26  4:10 ` [PATCH 2/5] arm64: Add ARCH_BITMAIN platform Manivannan Sadhasivam
2019-01-26  4:10 ` [PATCH 3/5] arm64: dts: bitmain: Add BM1880 SoC support Manivannan Sadhasivam
2019-01-26  4:10 ` [PATCH 4/5] arm64: dts: bitmain: Add Sophon Egde board support Manivannan Sadhasivam
2019-01-26  4:10 ` [PATCH 5/5] MAINTAINERS: Add entry for Bitmain SoC platform Manivannan Sadhasivam
2019-01-26 15:03 ` [PATCH 0/5] Add initial Bitmain BM1880 SoC/Board support Andrew Lunn
2019-01-26 15:17   ` Manivannan Sadhasivam [this message]
2019-01-27  9:24 ` Arnd Bergmann
2019-02-01  3:50   ` Manivannan Sadhasivam
2019-02-01  8:41     ` Arnd Bergmann

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=20190126151733.GA15434@Mani-XPS-13-9360 \
    --to=manivannan.sadhasivam@linaro.org \
    --cc=amit.kucheria@linaro.org \
    --cc=andrew@lunn.ch \
    --cc=arnd@arndb.de \
    --cc=darren.tsao@bitmain.com \
    --cc=devicetree@vger.kernel.org \
    --cc=haitao.suo@bitmain.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).