From: Greg KH <gregkh@linuxfoundation.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Umang Jain <umang.jain@ideasonboard.com>,
linux-staging@lists.linux.dev,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
stefan.wahren@i2se.com, f.fainelli@gmail.com,
athierry@redhat.com, error27@gmail.com,
dave.stevenson@raspberrypi.com, kieran.bingham@ideasonboard.com
Subject: Re: [PATCH v7 1/5] staging: vc04_services: vchiq_arm: Add new bus type and device type
Date: Tue, 20 Jun 2023 20:36:11 +0200 [thread overview]
Message-ID: <2023062030-flattop-jury-e10c@gregkh> (raw)
In-Reply-To: <20230620182054.GA14686@pendragon.ideasonboard.com>
On Tue, Jun 20, 2023 at 09:20:54PM +0300, Laurent Pinchart wrote:
> On Tue, Jun 20, 2023 at 04:17:05PM +0200, Greg KH wrote:
> > On Tue, Jun 20, 2023 at 07:11:48PM +0530, Umang Jain wrote:
> > > The devices that the vchiq interface registers (bcm2835-audio,
> > > bcm2835-camera) are implemented and exposed by the VC04 firmware.
> > > The device tree describes the VC04 itself with the resources required
> > > to communicate with it through a mailbox interface. However, the
> > > vchiq interface registers these devices as platform devices. This
> > > also means the specific drivers for these devices are getting
> > > registered as platform drivers. This is not correct and a blatant
> > > abuse of platform device/driver.
> > >
> > > Add a new bus type, vchiq_bus_type and device type (struct vchiq_device)
> > > which will be used to migrate child devices that the vchiq interfaces
> > > creates/registers from the platform device/driver.
> > >
> > > Signed-off-by: Umang Jain <umang.jain@ideasonboard.com>
> > > ---
> > > drivers/staging/vc04_services/Makefile | 1 +
> > > .../interface/vchiq_arm/vchiq_device.c | 78 +++++++++++++++++++
> > > .../interface/vchiq_arm/vchiq_device.h | 43 ++++++++++
> > > 3 files changed, 122 insertions(+)
> > > create mode 100644 drivers/staging/vc04_services/interface/vchiq_arm/vchiq_device.c
> > > create mode 100644 drivers/staging/vc04_services/interface/vchiq_arm/vchiq_device.h
> > >
> > > diff --git a/drivers/staging/vc04_services/Makefile b/drivers/staging/vc04_services/Makefile
> > > index 44794bdf6173..2d071e55e175 100644
> > > --- a/drivers/staging/vc04_services/Makefile
> > > +++ b/drivers/staging/vc04_services/Makefile
> > > @@ -5,6 +5,7 @@ vchiq-objs := \
> > > interface/vchiq_arm/vchiq_core.o \
> > > interface/vchiq_arm/vchiq_arm.o \
> > > interface/vchiq_arm/vchiq_debugfs.o \
> > > + interface/vchiq_arm/vchiq_device.o \
> > > interface/vchiq_arm/vchiq_connected.o \
> > >
> > > ifdef CONFIG_VCHIQ_CDEV
> > > diff --git a/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_device.c b/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_device.c
> > > new file mode 100644
> > > index 000000000000..e16279a25126
> > > --- /dev/null
> > > +++ b/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_device.c
> > > @@ -0,0 +1,78 @@
> > > +// SPDX-License-Identifier: GPL-2.0 OR BSD-3-Clause
> >
> > Code that directly interacts with the driver core can, for obvious
> > reasons, not be BSD-3 licensed, sorry.
> >
> > Also, why is any of this dual licensed? What good is any of that? In
> > order for me to accept new dual-licensed code, it needs to be documented
> > in the changelog very very well as to exactly why this is required, as
> > the legal issues involved in maintaining dual-licensed code like this is
> > tricky and easy to get wrong (as proven here already in this patch...)
>
> The whole vchiq_arm layer is dual licensed GPL-2.0 + BSD-3. I assume
> this is why Umang used the same licensing terms. We can use GPL-2.0 only
> if this patch qualifies as original work and not derived work of the
> existing code.
This is most certainly original work, not related to the original code
here, and can never work in a BSD-3 licensed environment.
thanks,
greg k-h
next prev parent reply other threads:[~2023-06-20 18:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 13:41 [PATCH v7 0/5] staging: vc04_services: vchiq: Register devices with a custom bus_type Umang Jain
2023-06-20 13:41 ` [PATCH v7 1/5] staging: vc04_services: vchiq_arm: Add new bus type and device type Umang Jain
2023-06-20 14:17 ` Greg KH
2023-06-20 18:20 ` Laurent Pinchart
2023-06-20 18:36 ` Greg KH [this message]
2023-06-20 13:41 ` [PATCH v7 2/5] staging: vc04_services: vchiq_arm: Register vchiq_bus_type Umang Jain
2023-06-20 13:41 ` [PATCH v7 3/5] staging: bcm2835-camera: Register bcm2835-camera with vchiq_bus_type Umang Jain
2023-06-20 13:41 ` [PATCH v7 4/5] staging: bcm2835-audio: Register bcm2835-audio " Umang Jain
2023-06-20 13:41 ` [PATCH v7 5/5] staging: vc04_services: vchiq_arm: Remove vchiq_register_child() Umang Jain
2023-06-20 14:18 ` [PATCH v7 0/5] staging: vc04_services: vchiq: Register devices with a custom bus_type Greg KH
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=2023062030-flattop-jury-e10c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=athierry@redhat.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=error27@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-staging@lists.linux.dev \
--cc=stefan.wahren@i2se.com \
--cc=umang.jain@ideasonboard.com \
/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