[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YiW6L9nv1+GwDEpd@kroah.com>
Date: Mon, 7 Mar 2022 08:54:23 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Oh Eomji <eomji.oh@...sung.com>
Cc: Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>,
open list <linux-kernel@...r.kernel.org>,
alsa-devel@...a-project.org, Leon Romanovsky <leon@...nel.org>,
Pavel Skripkin <paskripkin@...il.com>,
JaeHun Jung <jh0801.jung@...sung.com>
Subject: Re: [PATCH 1/2] sound: usb: Add vendor's hooking interface
On Mon, Mar 07, 2022 at 11:21:59AM +0900, Oh Eomji wrote:
> In mobile, a co-processor can be used with USB audio to improve power
> consumption. To support this type of hardware, hooks need to be added
> to the USB audio subsystem to be able to call into the hardware when
> needed.
>
> The main operation of the call-backs are:
> - Initialize the co-processor by transmitting data when initializing.
> - Change the co-processor setting value through the interface
> function.
> - Configure sampling rate
> - pcm open/close
> - other housekeeping
You need to supply the users of the callbacks/hooks, otherwise we can
not properly evaluate them, nor can we accept them.
I have been saying this for over a year, please submit ALL of the needed
parts for these hooks to even be able to be considered. Otherwise they
will just be ignored for the obvious reasons stated numerous times in
the past.
thanks,
greg k-h
Powered by blists - more mailing lists