[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fc564f68194b5cc668bb9e7a88cc097d38c9b128.camel@mediatek.com>
Date: Fri, 6 May 2022 19:37:07 +0800
From: Tinghan Shen <tinghan.shen@...iatek.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC: Matthias Brugger <matthias.bgg@...il.com>,
Javier Martinez Canillas <javierm@...hat.com>,
Thomas Zimmermann <tzimmermann@...e.de>,
Sudeep Holla <sudeep.holla@....com>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Borislav Petkov <bp@...e.de>,
Michal Suchanek <msuchanek@...e.de>,
"Cristian Marussi" <cristian.marussi@....com>,
Etienne Carriere <etienne.carriere@...aro.org>,
Arnd Bergmann <arnd@...db.de>,
Daniel Vetter <daniel.vetter@...ll.ch>,
Simon Trimmer <simont@...nsource.cirrus.com>,
"John Stultz" <john.stultz@...aro.org>,
Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>,
Allen-KH Cheng <allen-kh.cheng@...iatek.com>,
YC Hung <yc.hung@...iatek.com>,
Tzung-Bi Shih <tzungbi@...gle.com>,
Curtis Malainey <cujomalainey@...omium.org>,
Mark Brown <broonie@...nel.org>,
<linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-mediatek@...ts.infradead.org>,
<alsa-devel@...a-project.org>,
<Project_Global_Chrome_Upstream_Group@...iatek.com>
Subject: Re: [RESEND PATCH v7 1/1] firmware: mediatek: add adsp ipc protocol
interface
Hi Greg,
Thanks for your review.
On Thu, 2022-05-05 at 23:10 +0200, Greg Kroah-Hartman wrote:
> On Thu, May 05, 2022 at 01:30:48PM +0800, Tinghan Shen wrote:
> > From: TingHan Shen <tinghan.shen@...iatek.com>
> >
> > Some of mediatek processors contain
> > the Tensilica HiFix DSP for audio processing.
> >
> > The communication between Host CPU and DSP firmware is
> > taking place using a shared memory area for message passing.
> >
> > ADSP IPC protocol offers (send/recv) interfaces using
> > mediatek-mailbox APIs.
> >
> > We use two mbox channels to implement a request-reply protocol.
> >
> > Signed-off-by: Allen-KH Cheng <allen-kh.cheng@...iatek.com>
> > Signed-off-by: TingHan Shen <tinghan.shen@...iatek.com>
> > Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
> > Reviewed-by: Curtis Malainey <cujomalainey@...omium.org>
> > Reviewed-by: Tzung-Bi Shih <tzungbi@...gle.com>
> > Reviewed-by: YC Hung <yc.hung@...iatek.com>
> > Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
> > ---
> > drivers/firmware/Kconfig | 1 +
> > drivers/firmware/Makefile | 1 +
> > drivers/firmware/mediatek/Kconfig | 9 +
> > drivers/firmware/mediatek/Makefile | 2 +
> > drivers/firmware/mediatek/mtk-adsp-ipc.c | 161 ++++++++++++++++++
> > .../linux/firmware/mediatek/mtk-adsp-ipc.h | 65 +++++++
> > 6 files changed, 239 insertions(+)
> > create mode 100644 drivers/firmware/mediatek/Kconfig
> > create mode 100644 drivers/firmware/mediatek/Makefile
> > create mode 100644 drivers/firmware/mediatek/mtk-adsp-ipc.c
> > create mode 100644 include/linux/firmware/mediatek/mtk-adsp-ipc.h
>
> Why do you have a .h file, and export symbols in your .c file, yet you
> have no user of these symbols or header file?
>
> Without a user, we can not take this, sorry.
MediaTek have adsp client drivers on 2 chips that use symbols from this module.
We were planned to upstream them after Linux community accept this module.
I will add those client drivers in next version.
>
> This should just be one single .c file.
>
> Also, why a whole subdirectory for just one .c file?
Ok, I'll move the souce out and remove this subdirectory in next version.
Thank you very much.
Best regards,
TingHan
>
> thanks,
>
> greg k-h
Powered by blists - more mailing lists