From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Daehwan Jung <dh10.jung@samsung.com>,
Mathias Nyman <mathias.nyman@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "open list:USB XHCI DRIVER" <linux-usb@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Howard Yen <howardyen@google.com>,
Jack Pham <jackp@codeaurora.org>, Puma Hsu <pumahsu@google.com>,
"J . Avila" <elavila@google.com>
Subject: Re: [PATCH 0/3] support USB offload feature
Date: Thu, 3 Feb 2022 11:33:47 +0200 [thread overview]
Message-ID: <27337aa9-2bfd-18d5-cded-7f8ae0f053d9@linux.intel.com> (raw)
In-Reply-To: <1643857054-112415-1-git-send-email-dh10.jung@samsung.com>
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
next prev parent reply other threads:[~2022-02-03 9:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220203030000epcas2p2a924a55a5ae60e8685cd62b66a5482f3@epcas2p2.samsung.com>
2022-02-03 2:57 ` [PATCH 0/3] support USB offload feature Daehwan Jung
2022-02-03 2:57 ` [PATCH 1/3] usb: host: export symbols for xhci hooks usage Daehwan Jung
2022-02-03 5:12 ` kernel test robot
2022-02-03 2:57 ` [PATCH 2/3] usb: host: add xhci hooks for USB offload Daehwan Jung
2022-02-03 2:57 ` [PATCH 3/3] usb: host: add some to xhci overrides " Daehwan Jung
2022-02-03 7:21 ` [PATCH 0/3] support USB offload feature Greg Kroah-Hartman
2022-02-03 9:33 ` Mathias Nyman [this message]
2022-02-07 3:48 ` Macpaul Lin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=27337aa9-2bfd-18d5-cded-7f8ae0f053d9@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=dh10.jung@samsung.com \
--cc=elavila@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=howardyen@google.com \
--cc=jackp@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=pumahsu@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).