From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 61829EB64DB for ; Tue, 20 Jun 2023 18:21:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=hfrKhTvTkGWClP1dJu2SB7NMlBLcOSr76qwOMk+4KEs=; b=GMsujRrPfgeuaf XVe99HmP7Gg60c4yagVCcc26CMrm3tfBIWoS+yfcCI1MXxS6TrGsIEkTGVVeiP4KuLI+cL0o2E6VJ pO9oweT8oKwzvu31EC0eLYbUiRWdf6grT4HqYvpOcQpu1qdpLGxBWVCYZkBzHDgByIWO0lFFFdIET BaEivKxvRXEKFuxT/D74ZwgIaGDAoDYdE6Wpj7lPj6Unqro5hs9tBCt7eSeZ/ih005P/SS5aGBFEq whh2gyxTOfNrjNGEis/D1ixsvsns4sjurYjfM/X3A0b2kQsgDuEwwFi2ekxLo9xMN8wC+auAp+rE7 SrTHumbQQ5z3OKFNwFwQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1qBfyP-00C2Wz-12; Tue, 20 Jun 2023 18:21:01 +0000 Received: from perceval.ideasonboard.com ([213.167.242.64]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1qBfyN-00C2Uk-0a; Tue, 20 Jun 2023 18:21:00 +0000 Received: from pendragon.ideasonboard.com (213-243-189-158.bb.dnainternet.fi [213.243.189.158]) by perceval.ideasonboard.com (Postfix) with ESMTPSA id 258692B3; Tue, 20 Jun 2023 20:20:21 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ideasonboard.com; s=mail; t=1687285221; bh=sD1PKV7f7iXFcTk9Cp6Tb3XJE7rld19ReTuqZZXis4k=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=iG4rP0MTxRyFxBalRPcEerDsmXq1CeolMkm7bEEGOfK5TNr8sqU1mm9TJJY+8ZIgS 1Zwx82iXbcoNmen7ZmrIQEQtakzFb9Dw/kcwLrXzKjpOyQ5UcD3q8m33/NYDv+tEST XAMrUSsvbCo5SBsiZQsTdXTSgXDIV63116XP7Sz4= Date: Tue, 20 Jun 2023 21:20:54 +0300 From: Laurent Pinchart To: Greg KH Cc: Umang Jain , 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 Message-ID: <20230620182054.GA14686@pendragon.ideasonboard.com> References: <20230620134152.383569-1-umang.jain@ideasonboard.com> <20230620134152.383569-2-umang.jain@ideasonboard.com> <2023062022-whimsical-hasty-b012@gregkh> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <2023062022-whimsical-hasty-b012@gregkh> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230620_112059_362229_115F316E X-CRM114-Status: GOOD ( 25.38 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org 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 > > --- > > 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 being said, I have no objection changing the license of the whole vchiq_arm layer to GPL-2.0 only. Dave, any opinion on this ? -- Regards, Laurent Pinchart _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel