From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jung Daehwan <dh10.jung@samsung.com>
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 10:41:23 +0100 [thread overview]
Message-ID: <105eaeec-d77e-b0eb-86ad-a88c7446ca98@kernel.org> (raw)
In-Reply-To: <1983025922.01648006681661.JavaMail.epsvc@epcpadp4>
On 23/03/2022 03:58, Jung Daehwan wrote:
> 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.
It's better, but still does not explain why these have to be exported.
Please mention where are these hooks going to be. Where are they
implemented. I actually expect all of these exports to be used in your
patchset.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-03-23 9:41 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
2022-03-23 9:41 ` Krzysztof Kozlowski [this message]
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=105eaeec-d77e-b0eb-86ad-a88c7446ca98@kernel.org \
--to=krzk@kernel.org \
--cc=chihhao.chen@mediatek.com \
--cc=cpgs@samsung.com \
--cc=cpgsproxy5@samsung.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 \
--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;
as well as URLs for NNTP newsgroup(s).