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 X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 15AA8C4CEC9 for ; Wed, 18 Sep 2019 15:16:41 +0000 (UTC) Received: from alsa0.perex.cz (alsa0.perex.cz [77.48.224.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 10A5521907 for ; Wed, 18 Sep 2019 15:16:39 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alsa-project.org header.i=@alsa-project.org header.b="iRpMdLtO" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 10A5521907 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linux.intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=alsa-devel-bounces@alsa-project.org Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id CC4681675; Wed, 18 Sep 2019 17:15:47 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz CC4681675 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1568819797; bh=ZGGFyCo/jMyn1gP5Z5uVqkPozRslCbr/3sol3tngWYU=; h=To:References:From:Date:In-Reply-To:Cc:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=iRpMdLtONS3DSVXHmO8PE9w76hi4kTKg+bc7L/NxUGpmFgr6d9AY4AwFL0XuuH4iV hKW3/gyBYTCQ33thGilzl6TO9j+3OoB0yzgPeonGIjM9ybVSDmU1xJfaltI4qYRPxm /l5sij3uhf2j0Xp8WAqLDbt/beyFAHck2cby49iI= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id 50237F804FF; Wed, 18 Sep 2019 17:15:47 +0200 (CEST) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 5CF5DF800C1; Wed, 18 Sep 2019 17:15:45 +0200 (CEST) Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id CBF6CF800C1 for ; Wed, 18 Sep 2019 17:15:41 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz CBF6CF800C1 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Sep 2019 08:15:39 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,521,1559545200"; d="scan'208";a="338355937" Received: from linux.intel.com ([10.54.29.200]) by orsmga004.jf.intel.com with ESMTP; 18 Sep 2019 08:15:38 -0700 Received: from pbossart-mac01.local (unknown [10.251.11.91]) by linux.intel.com (Postfix) with ESMTP id C90925802B0; Wed, 18 Sep 2019 08:15:37 -0700 (PDT) To: Greg KH References: <20190916212342.12578-1-pierre-louis.bossart@linux.intel.com> <20190916212342.12578-9-pierre-louis.bossart@linux.intel.com> <20190917055512.GE2058532@kroah.com> <20190918120629.GD1901208@kroah.com> <20190918135302.GA1919118@kroah.com> <20190918135431.GA1919350@kroah.com> From: Pierre-Louis Bossart Message-ID: Date: Wed, 18 Sep 2019 10:14:51 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: <20190918135431.GA1919350@kroah.com> Content-Language: en-US Cc: alsa-devel@alsa-project.org, tiwai@suse.de, linux-kernel@vger.kernel.org, Ranjani Sridharan , vkoul@kernel.org, broonie@kernel.org, srinivas.kandagatla@linaro.org, jank@cadence.com, slawomir.blauciak@intel.com, Sanyog Kale , Bard liao , Rander Wang Subject: Re: [alsa-devel] [RFC PATCH 8/9] soundwire: intel: remove platform devices and provide new interface X-BeenThere: alsa-devel@alsa-project.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" On 9/18/19 8:54 AM, Greg KH wrote: > On Wed, Sep 18, 2019 at 03:53:02PM +0200, Greg KH wrote: >> On Wed, Sep 18, 2019 at 08:48:33AM -0500, Pierre-Louis Bossart wrote: >>> On 9/18/19 7:06 AM, Greg KH wrote: >>>> On Tue, Sep 17, 2019 at 09:29:52AM -0500, Pierre-Louis Bossart wrote: >>>>> On 9/17/19 12:55 AM, Greg KH wrote: >>>>>> On Mon, Sep 16, 2019 at 04:23:41PM -0500, Pierre-Louis Bossart wrote: >>>>>>> +/** >>>>>>> + * sdw_intel_probe() - SoundWire Intel probe routine >>>>>>> + * @parent_handle: ACPI parent handle >>>>>>> + * @res: resource data >>>>>>> + * >>>>>>> + * This creates SoundWire Master and Slave devices below the controller. >>>>>>> + * All the information necessary is stored in the context, and the res >>>>>>> + * argument pointer can be freed after this step. >>>>>>> + */ >>>>>>> +struct sdw_intel_ctx >>>>>>> +*sdw_intel_probe(struct sdw_intel_res *res) >>>>>>> +{ >>>>>>> + return sdw_intel_probe_controller(res); >>>>>>> +} >>>>>>> +EXPORT_SYMBOL(sdw_intel_probe); >>>>>>> + >>>>>>> +/** >>>>>>> + * sdw_intel_startup() - SoundWire Intel startup >>>>>>> + * @ctx: SoundWire context allocated in the probe >>>>>>> + * >>>>>>> + */ >>>>>>> +int sdw_intel_startup(struct sdw_intel_ctx *ctx) >>>>>>> +{ >>>>>>> + return sdw_intel_startup_controller(ctx); >>>>>>> +} >>>>>>> +EXPORT_SYMBOL(sdw_intel_startup); >>>>>> >>>>>> Why are you exporting these functions if no one calls them? >>>>> >>>>> They are used in the next series, see '[RFC PATCH 04/12] ASoC: SOF: Intel: >>>>> add SoundWire configuration interface' >>>> >>>> That wasn't obvious :) >>>> >>>> Also, why not EXPORT_SYMBOL_GPL()? :) >>> >>> Since the beginning of this SoundWire work, the intent what that the code >>> could be reused in non-GPL open-source circles, hence the dual license and >>> EXPORT_SYMBOL. >> >> Hah, you _have_ talked to your lawyers about this, right? >> >> You have a chance to do something like this for header files, for .c >> files, good luck. That's going to be a hard road to go down. Many have >> tried in the past, all but 1 have failed. > > Also note, the last I checked, the _default_ license for Linux kernel > code from Intel was GPLv2. If you got an exception for this, please > work with your legal council on how to do this "properly" as that was > part of getting that exception, right? > > If you didn't get the exception, um, you have some people to go talk to, > and how come I am the one asking you about this? :( All the legal due-diligence was done when SoundWire was initially contributed in 2018. You asked that question at the time and I will point you to the email exchange Alan Cox and you had on this topic [1]. [1] https://patchwork.kernel.org/patch/10015813/ _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/alsa-devel 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 X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1F105C4CEC4 for ; Wed, 18 Sep 2019 15:15:42 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E346D218AE for ; Wed, 18 Sep 2019 15:15:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731551AbfIRPPk (ORCPT ); Wed, 18 Sep 2019 11:15:40 -0400 Received: from mga14.intel.com ([192.55.52.115]:29252 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727968AbfIRPPk (ORCPT ); Wed, 18 Sep 2019 11:15:40 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Sep 2019 08:15:39 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,521,1559545200"; d="scan'208";a="338355937" Received: from linux.intel.com ([10.54.29.200]) by orsmga004.jf.intel.com with ESMTP; 18 Sep 2019 08:15:38 -0700 Received: from pbossart-mac01.local (unknown [10.251.11.91]) by linux.intel.com (Postfix) with ESMTP id C90925802B0; Wed, 18 Sep 2019 08:15:37 -0700 (PDT) Subject: Re: [alsa-devel] [RFC PATCH 8/9] soundwire: intel: remove platform devices and provide new interface To: Greg KH Cc: alsa-devel@alsa-project.org, tiwai@suse.de, linux-kernel@vger.kernel.org, Ranjani Sridharan , vkoul@kernel.org, broonie@kernel.org, srinivas.kandagatla@linaro.org, jank@cadence.com, slawomir.blauciak@intel.com, Sanyog Kale , Bard liao , Rander Wang References: <20190916212342.12578-1-pierre-louis.bossart@linux.intel.com> <20190916212342.12578-9-pierre-louis.bossart@linux.intel.com> <20190917055512.GE2058532@kroah.com> <20190918120629.GD1901208@kroah.com> <20190918135302.GA1919118@kroah.com> <20190918135431.GA1919350@kroah.com> From: Pierre-Louis Bossart Message-ID: Date: Wed, 18 Sep 2019 10:14:51 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: <20190918135431.GA1919350@kroah.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 9/18/19 8:54 AM, Greg KH wrote: > On Wed, Sep 18, 2019 at 03:53:02PM +0200, Greg KH wrote: >> On Wed, Sep 18, 2019 at 08:48:33AM -0500, Pierre-Louis Bossart wrote: >>> On 9/18/19 7:06 AM, Greg KH wrote: >>>> On Tue, Sep 17, 2019 at 09:29:52AM -0500, Pierre-Louis Bossart wrote: >>>>> On 9/17/19 12:55 AM, Greg KH wrote: >>>>>> On Mon, Sep 16, 2019 at 04:23:41PM -0500, Pierre-Louis Bossart wrote: >>>>>>> +/** >>>>>>> + * sdw_intel_probe() - SoundWire Intel probe routine >>>>>>> + * @parent_handle: ACPI parent handle >>>>>>> + * @res: resource data >>>>>>> + * >>>>>>> + * This creates SoundWire Master and Slave devices below the controller. >>>>>>> + * All the information necessary is stored in the context, and the res >>>>>>> + * argument pointer can be freed after this step. >>>>>>> + */ >>>>>>> +struct sdw_intel_ctx >>>>>>> +*sdw_intel_probe(struct sdw_intel_res *res) >>>>>>> +{ >>>>>>> + return sdw_intel_probe_controller(res); >>>>>>> +} >>>>>>> +EXPORT_SYMBOL(sdw_intel_probe); >>>>>>> + >>>>>>> +/** >>>>>>> + * sdw_intel_startup() - SoundWire Intel startup >>>>>>> + * @ctx: SoundWire context allocated in the probe >>>>>>> + * >>>>>>> + */ >>>>>>> +int sdw_intel_startup(struct sdw_intel_ctx *ctx) >>>>>>> +{ >>>>>>> + return sdw_intel_startup_controller(ctx); >>>>>>> +} >>>>>>> +EXPORT_SYMBOL(sdw_intel_startup); >>>>>> >>>>>> Why are you exporting these functions if no one calls them? >>>>> >>>>> They are used in the next series, see '[RFC PATCH 04/12] ASoC: SOF: Intel: >>>>> add SoundWire configuration interface' >>>> >>>> That wasn't obvious :) >>>> >>>> Also, why not EXPORT_SYMBOL_GPL()? :) >>> >>> Since the beginning of this SoundWire work, the intent what that the code >>> could be reused in non-GPL open-source circles, hence the dual license and >>> EXPORT_SYMBOL. >> >> Hah, you _have_ talked to your lawyers about this, right? >> >> You have a chance to do something like this for header files, for .c >> files, good luck. That's going to be a hard road to go down. Many have >> tried in the past, all but 1 have failed. > > Also note, the last I checked, the _default_ license for Linux kernel > code from Intel was GPLv2. If you got an exception for this, please > work with your legal council on how to do this "properly" as that was > part of getting that exception, right? > > If you didn't get the exception, um, you have some people to go talk to, > and how come I am the one asking you about this? :( All the legal due-diligence was done when SoundWire was initially contributed in 2018. You asked that question at the time and I will point you to the email exchange Alan Cox and you had on this topic [1]. [1] https://patchwork.kernel.org/patch/10015813/