From: Jung Daehwan <dh10.jung@samsung.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Mathias Nyman <mathias.nyman@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"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>,
"chihhao . chen" <chihhao.chen@mediatek.com>,
sc.suh@samsung.com, cpgs@samsung.com, cpgsproxy5@samsung.com
Subject: Re: [PATCH v1 1/4] usb: host: export symbols for xhci hooks usage
Date: Wed, 23 Mar 2022 11:58:22 +0900 [thread overview]
Message-ID: <1983025922.01648006681661.JavaMail.epsvc@epcpadp4> (raw)
In-Reply-To: <b33d8497-d6d5-18e2-93a9-e0564a84c1c5@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2030 bytes --]
On Mon, Mar 07, 2022 at 10:59:06AM +0100, Krzysztof Kozlowski wrote:
> On 04/03/2022 07:23, Daehwan Jung wrote:
> > Export symbols for xhci hooks usage:
> > xhci_ring_free
> > - Allow xhci hook to free xhci_ring.
>
> Instead of copying-pasting the name of function, please explain why do
> you need these symbols exported.
>
> The "Why" is actually one of most important questions, because "what is
> this patch doing" we can easily see...
>
> >
> > xhci_get_slot_ctx
> > - Allow xhci hook to get slot_ctx from the xhci_container_ctx
> > for getting the slot_ctx information to know which slot is
> > offloading and compare the context in remote subsystem memory
> > if needed.
> >
>
>
> Best regards,
> Krzysztof
>
Hi Krzysztof
xhci_ring_free has been removed from v3..
The reason why I want to export is for managing vendor specific ring.
I want to alloc and free vendor specific ring on specific address.
It's done with xhci hooks.
Below is the patch of v3
Export symbols for xhci hooks usage:
xhci_get_slot_ctx
xhci_get_endpoint_address
- Allow xhci hook to get ep_ctx from the xhci_container_ctx for
getting the ep_ctx information to know which ep is offloading and
comparing the context in remote subsystem memory if needed.
xhci_ring_alloc
- Allow xhci hook to allocate vendor specific ring.
xhci_trb_virt_to_dma
- Used to retrieve the DMA address of vendor specific ring.
xhci_segment_free
xhci_link_segments
- Allow xhci hook to handle vendor specific segment.
xhci_initialize_ring_info
- Allow xhci hook to initialize vendor specific ring.
xhci_check_trb_in_td_math
- Allow xhci hook to Check TRB math for validation.
xhci_address_device
- Allow override to give configuration info to Co-processor.
xhci_bus_suspend
xhci_bus_resume
- Allow override of suspend and resume for power scenario.
xhci_remove_stream_mapping
- Allow xhci hook to remove stream mapping.
Best Regards,
Jung Daehwan.
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2022-03-23 3:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220304062617epcas2p2084161966aaa66d07f4c25720ec18088@epcas2p2.samsung.com>
[not found] ` <1646375038-72082-1-git-send-email-dh10.jung@samsung.com>
2022-03-04 6:23 ` [PATCH v1 1/4] usb: host: export symbols for xhci hooks usage Daehwan Jung
2022-03-07 9:59 ` Krzysztof Kozlowski
2022-03-23 2:58 ` Jung Daehwan [this message]
2022-03-23 9:41 ` Krzysztof Kozlowski
2022-03-23 11:43 ` Greg Kroah-Hartman
2022-03-25 2:07 ` Jung Daehwan
2022-03-25 1:28 ` Jung Daehwan
2022-03-25 11:36 ` Krzysztof Kozlowski
2022-03-29 2:43 ` Jung Daehwan
2022-03-08 5:35 ` kernel test robot
2022-03-04 6:23 ` [PATCH v1 2/4] usb: host: add xhci hooks for USB offload Daehwan Jung
2022-03-08 6:16 ` kernel test robot
2022-03-08 10:51 ` kernel test robot
2022-03-04 6:23 ` [PATCH v1 3/4] usb: host: add some to xhci overrides " Daehwan Jung
2022-03-04 6:23 ` [PATCH v1 4/4] usb: host: add xhci-exynos module Daehwan Jung
2022-03-04 7:37 ` Greg Kroah-Hartman
2022-03-07 10:07 ` Krzysztof Kozlowski
2022-03-07 10:26 ` Jung Daehwan
2022-03-07 10:59 ` Krzysztof Kozlowski
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=1983025922.01648006681661.JavaMail.epsvc@epcpadp4 \
--to=dh10.jung@samsung.com \
--cc=chihhao.chen@mediatek.com \
--cc=cpgs@samsung.com \
--cc=cpgsproxy5@samsung.com \
--cc=elavila@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=howardyen@google.com \
--cc=jackp@codeaurora.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=pumahsu@google.com \
--cc=sc.suh@samsung.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