From: Daniele Alessandrelli <daniele.alessandrelli@linux.intel.com>
To: Jassi Brar <jassisinghbrar@gmail.com>
Cc: linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Rob Herring <robh+dt@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Olof Johansson <olof@lixom.net>,
Paul Murphy <paul.j.murphy@intel.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Dinh Nguyen <dinguyen@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Devicetree List <devicetree@vger.kernel.org>,
Daniele Alessandrelli <daniele.alessandrelli@intel.com>
Subject: Re: [PATCH 0/7] Add initial Keem Bay SoC / Board support
Date: Tue, 07 Jul 2020 22:17:59 +0100 [thread overview]
Message-ID: <08b2713a6f87f78746c22e7168f4813eb753bb0e.camel@linux.intel.com> (raw)
In-Reply-To: <CABb+yY0eUG=bxrQHP9-5gHk7SYF=c+EE+0LGKhnpxgfr078n6w@mail.gmail.com>
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@linux.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.
next prev parent reply other threads:[~2020-07-07 21:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 15:56 [PATCH 0/7] Add initial Keem Bay SoC / Board support Daniele Alessandrelli
2020-06-16 15:56 ` [PATCH 1/7] dt-bindings: mailbox: Add Keem Bay SCMI mailbox bindings Daniele Alessandrelli
2020-07-08 20:40 ` Sudeep Holla
2020-06-16 15:56 ` [PATCH 2/7] mailbox: keembay-scmi-mailbox: Add support for Keem Bay mailbox Daniele Alessandrelli
2020-07-08 20:34 ` Sudeep Holla
2020-07-09 12:23 ` Daniele Alessandrelli
2020-07-09 13:28 ` Paul Murphy
2020-07-10 8:01 ` Sudeep Holla
2020-06-16 15:56 ` [PATCH 3/7] arm64: Add config for Keem Bay SoC Daniele Alessandrelli
2020-06-16 15:56 ` [PATCH 4/7] dt-bindings: arm: Add Keem Bay bindings Daniele Alessandrelli
2020-06-16 15:56 ` [PATCH 5/7] MAINTAINERS: Add maintainers for Keem Bay SoC Daniele Alessandrelli
2020-06-16 15:56 ` [PATCH 6/7] arm64: dts: keembay: Add device tree " Daniele Alessandrelli
2020-07-08 20:39 ` Sudeep Holla
2020-06-16 15:56 ` [PATCH 7/7] arm64: dts: keembay: Add device tree for Keem Bay EVM board Daniele Alessandrelli
2020-06-30 7:07 ` [PATCH 0/7] Add initial Keem Bay SoC / Board support Daniele Alessandrelli
2020-07-06 4:36 ` Jassi Brar
2020-07-07 21:17 ` Daniele Alessandrelli [this message]
2020-07-07 23:44 ` Jassi Brar
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=08b2713a6f87f78746c22e7168f4813eb753bb0e.camel@linux.intel.com \
--to=daniele.alessandrelli@linux.intel.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=daniele.alessandrelli@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=paul.j.murphy@intel.com \
--cc=robh+dt@kernel.org \
--cc=will@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).