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 3CC5AC4332F for ; Thu, 29 Dec 2022 14:21:15 +0000 (UTC) Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id 45F8285D4; Thu, 29 Dec 2022 15:20:16 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz 45F8285D4 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1672323666; bh=d68hC20589Ctcis4IfSbCF+uNdhJbKhVIIf7umjLP70=; h=Date:From:To:Subject:In-Reply-To:References:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Cc:From; b=g+a+9fOkDctUHokY4+KDPYDjzBMfuxYwz+A2ITn14rUZUHwx3TKG6Z+UG+C9+7peC cPnwKmWr8mKNugS83XJWhkulKmp9QrwmbRQW39hZG+LG3uSxqLDK+nx9qePq6OGmSR jZrgeEEr3gUwHmaY3hWMiHNfZzyRqTxCJkdvQWO0= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id B9DDEF804E7; Thu, 29 Dec 2022 15:20:15 +0100 (CET) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 35399F804F1; Thu, 29 Dec 2022 15:20:14 +0100 (CET) Received: from smtp-out1.suse.de (smtp-out1.suse.de [IPv6:2001:67c:2178:6::1c]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id 97F76F804E4 for ; Thu, 29 Dec 2022 15:20:12 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 97F76F804E4 Authentication-Results: alsa1.perex.cz; dkim=pass (1024-bit key, unprotected) header.d=suse.de header.i=@suse.de header.a=rsa-sha256 header.s=susede2_rsa header.b=IagYAO9K; dkim=pass header.d=suse.de header.i=@suse.de header.a=ed25519-sha256 header.s=susede2_ed25519 header.b=h9m3zYuQ Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id A1A7F21C16; Thu, 29 Dec 2022 14:20:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1672323611; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=6S/5dUuk93/quxJDXW8zPtubkuqAP+2SRjZ0dzR6/K0=; b=IagYAO9Ke7u0hhsyuKd6Fx8s/lHiA1HQlem/YX675oLgpHOuzvlVF7DzdZs/xvamON9oxP HiR1VrukdpjKTgvJb/bpl/sHvZr3n5QP6gjt20fp28a7oZZ7T+qX3FoShMf9I38nzfGdW5 stIlnOsK61/J+STImJeRxnLobuJoWTg= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1672323611; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=6S/5dUuk93/quxJDXW8zPtubkuqAP+2SRjZ0dzR6/K0=; b=h9m3zYuQenkof35tDdAvbDSA9frScOvdOw/6TJSrwTvQmMkK6oB8ZT3vboUDe7lR5jKv1+ PCFmsbNvlNRNQ7DA== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 4174313913; Thu, 29 Dec 2022 14:20:11 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id IroEDxuirWNXOQAAMHmgww (envelope-from ); Thu, 29 Dec 2022 14:20:11 +0000 Date: Thu, 29 Dec 2022 15:20:10 +0100 Message-ID: <87lemqxpet.wl-tiwai@suse.de> From: Takashi Iwai To: Oliver Neukum Subject: Re: [RFC PATCH 04/14] sound: usb: card: Introduce USB SND vendor op callbacks In-Reply-To: <80f92635-6d14-8ff3-17ac-de2e5b977947@suse.com> References: <20221223233200.26089-1-quic_wcheng@quicinc.com> <20221223233200.26089-5-quic_wcheng@quicinc.com> <80f92635-6d14-8ff3-17ac-de2e5b977947@suse.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/27.2 Mule/6.0 MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-BeenThere: alsa-devel@alsa-project.org X-Mailman-Version: 2.1.29 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: , Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, alsa-devel@alsa-project.org, linux-usb@vger.kernel.org, bgoswami@quicinc.com, mathias.nyman@intel.com, gregkh@linuxfoundation.org, andersson@kernel.org, tiwai@suse.com, lgirdwood@gmail.com, robh+dt@kernel.org, broonie@kernel.org, srinivas.kandagatla@linaro.org, agross@kernel.org, krzysztof.kozlowski+dt@linaro.org, Thinh.Nguyen@synopsys.com, quic_plai@quicinc.com, Wesley Cheng , linux-kernel@vger.kernel.org, quic_jackp@quicinc.com Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" On Thu, 29 Dec 2022 14:49:21 +0100, Oliver Neukum wrote: > > > > On 24.12.22 00:31, Wesley Cheng wrote: > > Allow for different vendors to be notified on USB SND connect/disconnect > > seqeunces. This allows for vendor USB SND modules to properly initialize > > and populate internal structures with references to the USB SND chip > > device. > > Hi, > > this raises a design question. If the system is suspending or, worse, > hibernating, how do you make sure the offloader and the device are > suspended in the correct order? > And what happens if you need to go into reset_resume() when resuming? I guess we'd need to establish a device link when the binding from the offload driver is done. Then the PM order will be assured. Takashi 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 CABDEC4708E for ; Thu, 29 Dec 2022 14:20:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233187AbiL2OUQ (ORCPT ); Thu, 29 Dec 2022 09:20:16 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44624 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229658AbiL2OUP (ORCPT ); Thu, 29 Dec 2022 09:20:15 -0500 Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F1EC41A2; Thu, 29 Dec 2022 06:20:12 -0800 (PST) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id A1A7F21C16; Thu, 29 Dec 2022 14:20:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1672323611; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=6S/5dUuk93/quxJDXW8zPtubkuqAP+2SRjZ0dzR6/K0=; b=IagYAO9Ke7u0hhsyuKd6Fx8s/lHiA1HQlem/YX675oLgpHOuzvlVF7DzdZs/xvamON9oxP HiR1VrukdpjKTgvJb/bpl/sHvZr3n5QP6gjt20fp28a7oZZ7T+qX3FoShMf9I38nzfGdW5 stIlnOsK61/J+STImJeRxnLobuJoWTg= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1672323611; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=6S/5dUuk93/quxJDXW8zPtubkuqAP+2SRjZ0dzR6/K0=; b=h9m3zYuQenkof35tDdAvbDSA9frScOvdOw/6TJSrwTvQmMkK6oB8ZT3vboUDe7lR5jKv1+ PCFmsbNvlNRNQ7DA== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 4174313913; Thu, 29 Dec 2022 14:20:11 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id IroEDxuirWNXOQAAMHmgww (envelope-from ); Thu, 29 Dec 2022 14:20:11 +0000 Date: Thu, 29 Dec 2022 15:20:10 +0100 Message-ID: <87lemqxpet.wl-tiwai@suse.de> From: Takashi Iwai To: Oliver Neukum Cc: Wesley Cheng , srinivas.kandagatla@linaro.org, mathias.nyman@intel.com, perex@perex.cz, broonie@kernel.org, lgirdwood@gmail.com, andersson@kernel.org, krzysztof.kozlowski+dt@linaro.org, gregkh@linuxfoundation.org, Thinh.Nguyen@synopsys.com, bgoswami@quicinc.com, tiwai@suse.com, robh+dt@kernel.org, agross@kernel.org, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, alsa-devel@alsa-project.org, devicetree@vger.kernel.org, linux-usb@vger.kernel.org, quic_jackp@quicinc.com, quic_plai@quicinc.com Subject: Re: [RFC PATCH 04/14] sound: usb: card: Introduce USB SND vendor op callbacks In-Reply-To: <80f92635-6d14-8ff3-17ac-de2e5b977947@suse.com> References: <20221223233200.26089-1-quic_wcheng@quicinc.com> <20221223233200.26089-5-quic_wcheng@quicinc.com> <80f92635-6d14-8ff3-17ac-de2e5b977947@suse.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/27.2 Mule/6.0 MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org On Thu, 29 Dec 2022 14:49:21 +0100, Oliver Neukum wrote: > > > > On 24.12.22 00:31, Wesley Cheng wrote: > > Allow for different vendors to be notified on USB SND connect/disconnect > > seqeunces. This allows for vendor USB SND modules to properly initialize > > and populate internal structures with references to the USB SND chip > > device. > > Hi, > > this raises a design question. If the system is suspending or, worse, > hibernating, how do you make sure the offloader and the device are > suspended in the correct order? > And what happens if you need to go into reset_resume() when resuming? I guess we'd need to establish a device link when the binding from the offload driver is done. Then the PM order will be assured. Takashi