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 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 smtp.lore.kernel.org (Postfix) with ESMTPS id 14A4BC00140 for ; Mon, 15 Aug 2022 06:38:59 +0000 (UTC) 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 429E2100; Mon, 15 Aug 2022 08:38:07 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz 429E2100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1660545537; bh=i3Lhu29DAuR1+5toOtx6WUN5Q9/XjYipUqxecRURQhc=; h=Date:From:To:Subject:References:In-Reply-To:Cc:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=tnXdDTLEcY683lk/09VP6QgTkpdhlXqClNP0Ed55UHbd61CIpUpnzsi4GsDj2a4K1 YIWR06mvBNUYAzgapYtRrsmrU9tw5XAV++fjbNsyKVytetS/QL4k2VkNB+kwXy/dkz 26O3J6U6lkCUZ/d5Zls87x9ff+sBJZvi4lawhLuw= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id 45948F80245; Mon, 15 Aug 2022 08:38:06 +0200 (CEST) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 7F280F8025A; Mon, 15 Aug 2022 08:38:02 +0200 (CEST) Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id 2CA08F80125 for ; Mon, 15 Aug 2022 08:37:53 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 2CA08F80125 Authentication-Results: alsa1.perex.cz; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="dOLsO0eW" Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id CC945B80C82; Mon, 15 Aug 2022 06:37:49 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 743EAC433D7; Mon, 15 Aug 2022 06:37:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1660545468; bh=i3Lhu29DAuR1+5toOtx6WUN5Q9/XjYipUqxecRURQhc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=dOLsO0eWL1louTh1erlzYfiyxe3e1GCuC6rITTMB6BAFW0KYj4VI2sod/q921wwgf qgeNPTQAt9VclhBL3OLkn0QO3EDriXGrjbiBwZf5gf4gjsOO8njLu3nhbLUBuuPqQE mSU/BTQYvSJzrPgD6m1fVkeJrGXt3Yx+Tzq0GG6U= Date: Mon, 15 Aug 2022 08:37:44 +0200 From: Greg KH To: Khalid Masum Subject: Re: [RFC PATCH] Soundwire: Initialize multi_link with fwnode props Message-ID: References: <20220814080416.7531-1-khalid.masum.92@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: alsa-devel@alsa-project.org, Heikki Krogerus , "Rafael J . Wysocki" , Bard Liao , linux-kernel@vger.kernel.org, Pierre-Louis Bossart , Daniel Scally , linux-acpi@vger.kernel.org, Vinod Koul , Sakari Ailus , Sanyog Kale , Andy Shevchenko , linux-kernel-mentees@lists.linuxfoundation.org, Len Brown 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: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" On Mon, Aug 15, 2022 at 10:08:07AM +0600, Khalid Masum wrote: > On 8/14/22 15:45, Greg KH wrote: > > On Sun, Aug 14, 2022 at 02:04:15PM +0600, Khalid Masum wrote: > > > According to the TODO, In sw_bus_master_add, bus->multi_link is to be > > > populated with properties from FW node props. Make this happen by > > > creating a new fwnode_handle flag FWNODE_FLAG_MULTI_LINKED and use > > > the flag to store the multi_link value from intel_link_startup. Use > > > this flag to initialize bus->multi_link. > > > > > > Signed-off-by: Khalid Masum > > > --- > > > I do not think adding a new flag for fwnode_handle is a good idea. > > > So, what would be the best way to initialize bus->multilink with > > > fwnode props? > > > > > > -- Khalid Masum > > > > > > drivers/soundwire/bus.c | 4 ++-- > > > drivers/soundwire/intel.c | 1 + > > > include/linux/fwnode.h | 1 + > > > 3 files changed, 4 insertions(+), 2 deletions(-) > > > > > > diff --git a/drivers/soundwire/bus.c b/drivers/soundwire/bus.c > > > index a2bfb0434a67..80df1672c60b 100644 > > > --- a/drivers/soundwire/bus.c > > > +++ b/drivers/soundwire/bus.c > > > @@ -74,9 +74,9 @@ int sdw_bus_master_add(struct sdw_bus *bus, struct device *parent, > > > /* > > > * Initialize multi_link flag > > > - * TODO: populate this flag by reading property from FW node > > > */ > > > - bus->multi_link = false; > > > + bus->multi_link = (fwnode->flags & FWNODE_FLAG_MULTI_LINKED) > > > + == FWNODE_FLAG_MULTI_LINKED; I missed that this was an if statement here, please write this to be more obvious and readable. > > > if (bus->ops->read_prop) { > > > ret = bus->ops->read_prop(bus); > > > if (ret < 0) { > > > diff --git a/drivers/soundwire/intel.c b/drivers/soundwire/intel.c > > > index 505c5ef061e3..034d1c523ddf 100644 > > > --- a/drivers/soundwire/intel.c > > > +++ b/drivers/soundwire/intel.c > > > @@ -1347,6 +1347,7 @@ int intel_link_startup(struct auxiliary_device *auxdev) > > > */ > > > bus->multi_link = true; > > > bus->hw_sync_min_links = 1; > > > + dev->fwnode->flags |= FWNODE_FLAG_MULTI_LINKED; > > > } > > > /* Initialize shim, controller */ > > > diff --git a/include/linux/fwnode.h b/include/linux/fwnode.h > > > index 9a81c4410b9f..446a52744953 100644 > > > --- a/include/linux/fwnode.h > > > +++ b/include/linux/fwnode.h > > > @@ -32,6 +32,7 @@ struct device; > > > #define FWNODE_FLAG_NOT_DEVICE BIT(1) > > > #define FWNODE_FLAG_INITIALIZED BIT(2) > > > #define FWNODE_FLAG_NEEDS_CHILD_BOUND_ON_ADD BIT(3) > > > +#define FWNODE_FLAG_MULTI_LINKED BIT(4) > > > > What does this commit actually change? > > The new flag will lets us save if the device has multilink in fwnode_handle > whenever needed. > Then for soundwire/intel, save the multi_link flag into fwnode during > startup. > Later at master_add, as written in todo, initialize the multilink flag with > fwnode's flag property. And what does that allow to happen? What changes with all of this? thanks, greg k-h 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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id EC902C00140 for ; Mon, 15 Aug 2022 06:37:53 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231251AbiHOGhx (ORCPT ); Mon, 15 Aug 2022 02:37:53 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39522 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230455AbiHOGhw (ORCPT ); Mon, 15 Aug 2022 02:37:52 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3389019C2E; Sun, 14 Aug 2022 23:37:51 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id E228CB80C87; Mon, 15 Aug 2022 06:37:49 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 743EAC433D7; Mon, 15 Aug 2022 06:37:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1660545468; bh=i3Lhu29DAuR1+5toOtx6WUN5Q9/XjYipUqxecRURQhc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=dOLsO0eWL1louTh1erlzYfiyxe3e1GCuC6rITTMB6BAFW0KYj4VI2sod/q921wwgf qgeNPTQAt9VclhBL3OLkn0QO3EDriXGrjbiBwZf5gf4gjsOO8njLu3nhbLUBuuPqQE mSU/BTQYvSJzrPgD6m1fVkeJrGXt3Yx+Tzq0GG6U= Date: Mon, 15 Aug 2022 08:37:44 +0200 From: Greg KH To: Khalid Masum Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, linux-kernel-mentees@lists.linuxfoundation.org, Heikki Krogerus , "Rafael J . Wysocki" , Pierre-Louis Bossart , Daniel Scally , Vinod Koul , Sakari Ailus , Sanyog Kale , Andy Shevchenko , Bard Liao , Len Brown Subject: Re: [RFC PATCH] Soundwire: Initialize multi_link with fwnode props Message-ID: References: <20220814080416.7531-1-khalid.masum.92@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-acpi@vger.kernel.org On Mon, Aug 15, 2022 at 10:08:07AM +0600, Khalid Masum wrote: > On 8/14/22 15:45, Greg KH wrote: > > On Sun, Aug 14, 2022 at 02:04:15PM +0600, Khalid Masum wrote: > > > According to the TODO, In sw_bus_master_add, bus->multi_link is to be > > > populated with properties from FW node props. Make this happen by > > > creating a new fwnode_handle flag FWNODE_FLAG_MULTI_LINKED and use > > > the flag to store the multi_link value from intel_link_startup. Use > > > this flag to initialize bus->multi_link. > > > > > > Signed-off-by: Khalid Masum > > > --- > > > I do not think adding a new flag for fwnode_handle is a good idea. > > > So, what would be the best way to initialize bus->multilink with > > > fwnode props? > > > > > > -- Khalid Masum > > > > > > drivers/soundwire/bus.c | 4 ++-- > > > drivers/soundwire/intel.c | 1 + > > > include/linux/fwnode.h | 1 + > > > 3 files changed, 4 insertions(+), 2 deletions(-) > > > > > > diff --git a/drivers/soundwire/bus.c b/drivers/soundwire/bus.c > > > index a2bfb0434a67..80df1672c60b 100644 > > > --- a/drivers/soundwire/bus.c > > > +++ b/drivers/soundwire/bus.c > > > @@ -74,9 +74,9 @@ int sdw_bus_master_add(struct sdw_bus *bus, struct device *parent, > > > /* > > > * Initialize multi_link flag > > > - * TODO: populate this flag by reading property from FW node > > > */ > > > - bus->multi_link = false; > > > + bus->multi_link = (fwnode->flags & FWNODE_FLAG_MULTI_LINKED) > > > + == FWNODE_FLAG_MULTI_LINKED; I missed that this was an if statement here, please write this to be more obvious and readable. > > > if (bus->ops->read_prop) { > > > ret = bus->ops->read_prop(bus); > > > if (ret < 0) { > > > diff --git a/drivers/soundwire/intel.c b/drivers/soundwire/intel.c > > > index 505c5ef061e3..034d1c523ddf 100644 > > > --- a/drivers/soundwire/intel.c > > > +++ b/drivers/soundwire/intel.c > > > @@ -1347,6 +1347,7 @@ int intel_link_startup(struct auxiliary_device *auxdev) > > > */ > > > bus->multi_link = true; > > > bus->hw_sync_min_links = 1; > > > + dev->fwnode->flags |= FWNODE_FLAG_MULTI_LINKED; > > > } > > > /* Initialize shim, controller */ > > > diff --git a/include/linux/fwnode.h b/include/linux/fwnode.h > > > index 9a81c4410b9f..446a52744953 100644 > > > --- a/include/linux/fwnode.h > > > +++ b/include/linux/fwnode.h > > > @@ -32,6 +32,7 @@ struct device; > > > #define FWNODE_FLAG_NOT_DEVICE BIT(1) > > > #define FWNODE_FLAG_INITIALIZED BIT(2) > > > #define FWNODE_FLAG_NEEDS_CHILD_BOUND_ON_ADD BIT(3) > > > +#define FWNODE_FLAG_MULTI_LINKED BIT(4) > > > > What does this commit actually change? > > The new flag will lets us save if the device has multilink in fwnode_handle > whenever needed. > Then for soundwire/intel, save the multi_link flag into fwnode during > startup. > Later at master_add, as written in todo, initialize the multilink flag with > fwnode's flag property. And what does that allow to happen? What changes with all of this? thanks, greg k-h 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 smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.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 24467C00140 for ; Mon, 15 Aug 2022 06:37:59 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id 951C84049F; Mon, 15 Aug 2022 06:37:59 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 951C84049F Authentication-Results: smtp2.osuosl.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=dOLsO0eW X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp2.osuosl.org ([127.0.0.1]) by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DOFkUMQKjBU8; Mon, 15 Aug 2022 06:37:58 +0000 (UTC) Received: from lists.linuxfoundation.org (lf-lists.osuosl.org [140.211.9.56]) by smtp2.osuosl.org (Postfix) with ESMTPS id 887E840146; Mon, 15 Aug 2022 06:37:58 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 887E840146 Received: from lf-lists.osuosl.org (localhost [127.0.0.1]) by lists.linuxfoundation.org (Postfix) with ESMTP id 4158EC0032; Mon, 15 Aug 2022 06:37:58 +0000 (UTC) Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137]) by lists.linuxfoundation.org (Postfix) with ESMTP id 89EACC002D for ; Mon, 15 Aug 2022 06:37:57 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id 4FD6E415D0 for ; Mon, 15 Aug 2022 06:37:57 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 4FD6E415D0 Authentication-Results: smtp4.osuosl.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=dOLsO0eW X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp4.osuosl.org ([127.0.0.1]) by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r8Qgpnsmk-j8 for ; Mon, 15 Aug 2022 06:37:53 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org D1CC2415B5 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by smtp4.osuosl.org (Postfix) with ESMTPS id D1CC2415B5 for ; Mon, 15 Aug 2022 06:37:52 +0000 (UTC) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id CC945B80C82; Mon, 15 Aug 2022 06:37:49 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 743EAC433D7; Mon, 15 Aug 2022 06:37:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1660545468; bh=i3Lhu29DAuR1+5toOtx6WUN5Q9/XjYipUqxecRURQhc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=dOLsO0eWL1louTh1erlzYfiyxe3e1GCuC6rITTMB6BAFW0KYj4VI2sod/q921wwgf qgeNPTQAt9VclhBL3OLkn0QO3EDriXGrjbiBwZf5gf4gjsOO8njLu3nhbLUBuuPqQE mSU/BTQYvSJzrPgD6m1fVkeJrGXt3Yx+Tzq0GG6U= Date: Mon, 15 Aug 2022 08:37:44 +0200 From: Greg KH To: Khalid Masum Subject: Re: [RFC PATCH] Soundwire: Initialize multi_link with fwnode props Message-ID: References: <20220814080416.7531-1-khalid.masum.92@gmail.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Cc: alsa-devel@alsa-project.org, Heikki Krogerus , "Rafael J . Wysocki" , Bard Liao , linux-kernel@vger.kernel.org, Pierre-Louis Bossart , Daniel Scally , linux-acpi@vger.kernel.org, Vinod Koul , Sakari Ailus , Sanyog Kale , Andy Shevchenko , linux-kernel-mentees@lists.linuxfoundation.org, Len Brown X-BeenThere: linux-kernel-mentees@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 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 Errors-To: linux-kernel-mentees-bounces@lists.linuxfoundation.org Sender: "Linux-kernel-mentees" On Mon, Aug 15, 2022 at 10:08:07AM +0600, Khalid Masum wrote: > On 8/14/22 15:45, Greg KH wrote: > > On Sun, Aug 14, 2022 at 02:04:15PM +0600, Khalid Masum wrote: > > > According to the TODO, In sw_bus_master_add, bus->multi_link is to be > > > populated with properties from FW node props. Make this happen by > > > creating a new fwnode_handle flag FWNODE_FLAG_MULTI_LINKED and use > > > the flag to store the multi_link value from intel_link_startup. Use > > > this flag to initialize bus->multi_link. > > > > > > Signed-off-by: Khalid Masum > > > --- > > > I do not think adding a new flag for fwnode_handle is a good idea. > > > So, what would be the best way to initialize bus->multilink with > > > fwnode props? > > > > > > -- Khalid Masum > > > > > > drivers/soundwire/bus.c | 4 ++-- > > > drivers/soundwire/intel.c | 1 + > > > include/linux/fwnode.h | 1 + > > > 3 files changed, 4 insertions(+), 2 deletions(-) > > > > > > diff --git a/drivers/soundwire/bus.c b/drivers/soundwire/bus.c > > > index a2bfb0434a67..80df1672c60b 100644 > > > --- a/drivers/soundwire/bus.c > > > +++ b/drivers/soundwire/bus.c > > > @@ -74,9 +74,9 @@ int sdw_bus_master_add(struct sdw_bus *bus, struct device *parent, > > > /* > > > * Initialize multi_link flag > > > - * TODO: populate this flag by reading property from FW node > > > */ > > > - bus->multi_link = false; > > > + bus->multi_link = (fwnode->flags & FWNODE_FLAG_MULTI_LINKED) > > > + == FWNODE_FLAG_MULTI_LINKED; I missed that this was an if statement here, please write this to be more obvious and readable. > > > if (bus->ops->read_prop) { > > > ret = bus->ops->read_prop(bus); > > > if (ret < 0) { > > > diff --git a/drivers/soundwire/intel.c b/drivers/soundwire/intel.c > > > index 505c5ef061e3..034d1c523ddf 100644 > > > --- a/drivers/soundwire/intel.c > > > +++ b/drivers/soundwire/intel.c > > > @@ -1347,6 +1347,7 @@ int intel_link_startup(struct auxiliary_device *auxdev) > > > */ > > > bus->multi_link = true; > > > bus->hw_sync_min_links = 1; > > > + dev->fwnode->flags |= FWNODE_FLAG_MULTI_LINKED; > > > } > > > /* Initialize shim, controller */ > > > diff --git a/include/linux/fwnode.h b/include/linux/fwnode.h > > > index 9a81c4410b9f..446a52744953 100644 > > > --- a/include/linux/fwnode.h > > > +++ b/include/linux/fwnode.h > > > @@ -32,6 +32,7 @@ struct device; > > > #define FWNODE_FLAG_NOT_DEVICE BIT(1) > > > #define FWNODE_FLAG_INITIALIZED BIT(2) > > > #define FWNODE_FLAG_NEEDS_CHILD_BOUND_ON_ADD BIT(3) > > > +#define FWNODE_FLAG_MULTI_LINKED BIT(4) > > > > What does this commit actually change? > > The new flag will lets us save if the device has multilink in fwnode_handle > whenever needed. > Then for soundwire/intel, save the multi_link flag into fwnode during > startup. > Later at master_add, as written in todo, initialize the multilink flag with > fwnode's flag property. And what does that allow to happen? What changes with all of this? thanks, greg k-h _______________________________________________ Linux-kernel-mentees mailing list Linux-kernel-mentees@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees