[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 07 Jul 2020 22:17:59 +0100
From: Daniele Alessandrelli <daniele.alessandrelli@...ux.intel.com>
To: Jassi Brar <jassisinghbrar@...il.com>
Cc: linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
Rob Herring <robh+dt@...nel.org>,
Arnd Bergmann <arnd@...db.de>, Olof Johansson <olof@...om.net>,
Paul Murphy <paul.j.murphy@...el.com>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
Dinh Nguyen <dinguyen@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Devicetree List <devicetree@...r.kernel.org>,
Daniele Alessandrelli <daniele.alessandrelli@...el.com>
Subject: Re: [PATCH 0/7] Add initial Keem Bay SoC / Board support
On Sun, 2020-07-05 at 23:36 -0500, Jassi Brar wrote:
> On Tue, Jun 16, 2020 at 10:56 AM Daniele Alessandrelli
> <daniele.alessandrelli@...ux.intel.com> wrote:
> > Hi,
> >
> > This patch-set adds initial support for a new Intel Movidius SoC
> > code-named
> > Keem Bay. The SoC couples an ARM Cortex A53 CPU with an Intel
> > Movidius VPU.
> >
> > This initial patch-set enables only the minimal set of components
> > required to
> > make the Keem Bay EVM board boot into initramfs.
> >
> > Brief summary of the patch-set:
> > * Patches 1-2 add the Keem Bay SCMI Mailbox driver (needed to
> > enable SCMI in
> > Keem Bay)
> > * Patch 3 adds the ARCH_KEEMBAY config option
> > * Patches 4-7 add minimal device tree for Keem Bay SoC and Keem Bay
> > EVM
> > (together with information about the SoC maintainers)
> >
> Please break this into two patchsets - first enabling platform
> support
> and second adding mailbox support.
Thanks for your feedback Jassi. I will split the patcheset into two
different patchsets.
Just one question: should I remove the mailbox and scmi nodes from the
soc DT or can I keep them there even if the mailbox driver is not
available yet?
>
> thanks.
Powered by blists - more mailing lists