Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20200708175020.194436-1-daniele.alessandrelli@linux.intel.com>
In-Reply-To: <20200708175020.194436-1-daniele.alessandrelli@linux.intel.com>
From:   Arnd Bergmann <arnd@arndb.de>
Date:   Tue, 14 Jul 2020 14:40:28 +0200
Message-ID: <CAK8P3a3GVZftAZKEHC3TjDRL86vYOkND6TNuVq1KjssOHi5AXw@mail.gmail.com>
Subject: Re: [PATCH v2 0/5] Add initial Keem Bay SoC / Board support
To:     Daniele Alessandrelli <daniele.alessandrelli@linux.intel.com>
Cc:     Linux ARM <linux-arm-kernel@lists.infradead.org>,
        SoC Team <soc@kernel.org>, Rob Herring <robh+dt@kernel.org>,
        Jassi Brar <jassisinghbrar@gmail.com>,
        Olof Johansson <olof@lixom.net>,
        DTML <devicetree@vger.kernel.org>,
        Catalin Marinas <catalin.marinas@arm.com>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Dinh Nguyen <dinguyen@kernel.org>,
        Paul Murphy <paul.j.murphy@intel.com>,
        Will Deacon <will@kernel.org>,
        Daniele Alessandrelli <daniele.alessandrelli@intel.com>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Wed, Jul 8, 2020 at 7:50 PM 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.
>
> Changes from v1 to v2:
> * Moved keembay-scmi-mailbox driver to a separate patchset
> * Removed Keem Bay SCMI mailbox and SCMI node from Keem Bay SoC device tree

This all looks basically ok, but I noticed that the DT bindings ands
DTS files all have a
"GPL-2.0-only" tag. Usually we make those dual-licensed in order to
make it easier
to distribute them with a non-GPL bootloader and synchronize them between
projects.

Do you know if the GPL-2.0-only part was picked intentionally, or if it can
be changed to dual-licensed?

      Arnd