[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87lemqxpet.wl-tiwai@suse.de>
Date: Thu, 29 Dec 2022 15:20:10 +0100
From: Takashi Iwai <tiwai@...e.de>
To: Oliver Neukum <oneukum@...e.com>
Cc: Wesley Cheng <quic_wcheng@...cinc.com>,
srinivas.kandagatla@...aro.org, mathias.nyman@...el.com,
perex@...ex.cz, broonie@...nel.org, lgirdwood@...il.com,
andersson@...nel.org, krzysztof.kozlowski+dt@...aro.org,
gregkh@...uxfoundation.org, Thinh.Nguyen@...opsys.com,
bgoswami@...cinc.com, tiwai@...e.com, robh+dt@...nel.org,
agross@...nel.org, linux-kernel@...r.kernel.org,
linux-arm-msm@...r.kernel.org, alsa-devel@...a-project.org,
devicetree@...r.kernel.org, linux-usb@...r.kernel.org,
quic_jackp@...cinc.com, quic_plai@...cinc.com
Subject: Re: [RFC PATCH 04/14] sound: usb: card: Introduce USB SND vendor op callbacks
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
Powered by blists - more mailing lists