[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <df83f981-8146-576a-c7a5-420aa2dd4b72@mediatek.com>
Date: Mon, 7 Feb 2022 11:48:00 +0800
From: Macpaul Lin <macpaul.lin@...iatek.com>
To: Mathias Nyman <mathias.nyman@...ux.intel.com>,
Daehwan Jung <dh10.jung@...sung.com>,
Mathias Nyman <mathias.nyman@...el.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC: "open list:USB XHCI DRIVER" <linux-usb@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
Howard Yen <howardyen@...gle.com>,
Jack Pham <jackp@...eaurora.org>,
Puma Hsu <pumahsu@...gle.com>,
"J . Avila" <elavila@...gle.com>,
Eddie Hung <eddie.hung@...iatek.com>,
Chunfeng Yun <chunfeng.yun@...iatek.com>
Subject: Re: [PATCH 0/3] support USB offload feature
On 2/3/22 5:33 PM, Mathias Nyman wrote:
> On 3.2.2022 4.57, Daehwan Jung wrote:
>> This patchset is for USB offload feature, which makes Co-processor to use
>> some memories of xhci. Especially it's useful for USB Audio scenario.
>> Audio stream would get shortcut because Co-processor directly write/read
>> data in xhci memories. It could get speed-up using faster memory like SRAM.
>> That's why this also gives vendors flexibilty of memory management.
>> Below pathches have been merged in AOSP kernel(android12-5.10) and I put
>> together and split into 3 patches.
>
> Can you share the full USB offload support series?
>
> I'd like to see the big picture before taking any exporting and override
> patches.
>
> Thanks
> -Mathias
>
>
Dear Daehwan,
I'm very appreciate for your upstream work.
We know that, USB offload (especially for headset - USB Audio) is a very
important feature in current smart phone devices. It is able to improve
both audio latency and power consumption under music playing or phone
call scenarios. However, the solution varies between different SOC
vendors, because the implementations are different in both software and
hardware interfaces.
I think a design description (document) to your implementation is
important for introducing this feature to Linux community. Maybe a
configuration how-to is required for not only maintainers but also
developers to understand these modifications. And I think other vendors
should follow up if they likes to upstream their solutions. :)
Thanks!
MAcpaul Lin
Powered by blists - more mailing lists