From: Jung Daehwan <dh10.jung@samsung.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
Mathias Nyman <mathias.nyman@intel.com>,
Felipe Balbi <balbi@kernel.org>,
"open list:USB SUBSYSTEM" <linux-usb@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
sc.suh@samsung.com, taehyun.cho@samsung.com,
jh0801.jung@samsung.com, eomji.oh@samsung.com
Subject: Re: [RFC PATCH v2 1/3] usb: support Samsung Exynos xHCI Controller
Date: Mon, 2 Jan 2023 15:24:48 +0900 [thread overview]
Message-ID: <20230102062448.GC74470@ubuntu> (raw)
In-Reply-To: <bc531774-ed70-39b7-3534-5683dff20591@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 2813 bytes --]
On Thu, Dec 29, 2022 at 11:25:58AM +0100, Krzysztof Kozlowski wrote:
> On 29/12/2022 10:57, Daehwan Jung wrote:
> > Currently, dwc3 invokes just xhci platform driver without any data.
> > We add xhci node as child of dwc3 node in order to get data from
> > device tree. It populates "xhci" child by name during initialization
> > of host. This patch only effects if dwc3 node has a child named "xhci"
> > not to disturb original path.
> >
> > We add "samsung,exynos-xhci" compatible in xhci platform driver
>
> Where? It is not documented.
I submitted the patch of dt bindings on same patchset.
Is there any missing documentation?
>
> > to support Exynos SOCs.
>
> That's so not true. You do nothing to support Exynos SoC here. Please
> stop pasting incorrect and misleading commit msgs.
I agree misleading commit msgs. I will modify it.
>
> > We introduce roothub wakeup, which uses roothub
> > as system wakeup source. It needs xhci platform driver to override
> > roothub ops.
>
> You did not explain why you introduced wakelocks...
>
I'm sorry I didn't write description enough.
I add it below.
>
> (...)
>
> > if (shared_hcd) {
> > usb_remove_hcd(shared_hcd);
> > xhci->shared_hcd = NULL;
> > diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
> > index 79d7931c048a..693495054001 100644
> > --- a/drivers/usb/host/xhci.c
> > +++ b/drivers/usb/host/xhci.c
> > @@ -5502,6 +5502,10 @@ void xhci_init_driver(struct hc_driver *drv,
> > drv->check_bandwidth = over->check_bandwidth;
> > if (over->reset_bandwidth)
> > drv->reset_bandwidth = over->reset_bandwidth;
> > + if (over->bus_suspend)
> > + drv->bus_suspend = over->bus_suspend;
> > + if (over->bus_resume)
> > + drv->bus_resume = over->bus_resume;
> > }
> > }
> > EXPORT_SYMBOL_GPL(xhci_init_driver);
> > diff --git a/drivers/usb/host/xhci.h b/drivers/usb/host/xhci.h
> > index c9f06c5e4e9d..cb9c54a6a22c 100644
> > --- a/drivers/usb/host/xhci.h
> > +++ b/drivers/usb/host/xhci.h
> > @@ -1752,6 +1752,8 @@ struct xhci_hub {
> > struct xhci_hcd {
> > struct usb_hcd *main_hcd;
> > struct usb_hcd *shared_hcd;
> > + struct wakeup_source *main_wakelock;
> > + struct wakeup_source *shared_wakelock;
>
> Drop wakelocks. This is not related to USB and not needed here. Do you
> see anywhere else in core kernel code usage of the wakelocks?
>
> You got this comment already, didn't you? So why you do not address it?
>
I want to add a new feature in xhci platform driver. I want to make it
possible to enter system sleep while usb host connected like USB Mouse.
It gets system enter sleep only if there's no usb transaction at all.
Deciding if there's tranaction or not is in root hub because it's parent
of all child usb devices.
Best Regards,
Jung Daehwan
> Best regards,
> Krzysztof
>
>
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2023-01-02 6:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20221229100409epcas2p123de28f73dfb4d7429d0e15e41bb13a7@epcas2p1.samsung.com>
2022-12-29 9:57 ` [RFC PATCH v2 0/3] support Samsung Exynos xHCI Controller Daehwan Jung
2022-12-29 9:57 ` [RFC PATCH v2 1/3] usb: " Daehwan Jung
2022-12-29 10:25 ` Krzysztof Kozlowski
2023-01-02 6:24 ` Jung Daehwan [this message]
2023-01-02 8:30 ` Krzysztof Kozlowski
2022-12-29 14:44 ` Arnd Bergmann
2023-01-02 6:35 ` Jung Daehwan
2022-12-29 9:57 ` [RFC PATCH v2 2/3] dt-bindings: usb: generic-xhci: add Samsung Exynos compatible Daehwan Jung
2022-12-29 10:19 ` Krzysztof Kozlowski
2023-01-02 5:30 ` Jung Daehwan
2023-01-02 8:27 ` Krzysztof Kozlowski
2022-12-29 9:57 ` [RFC PATCH v2 3/3] dt-bindings: usb: snps,dwc3: add generic-xhci as child Daehwan Jung
2022-12-29 10:23 ` Krzysztof Kozlowski
2023-01-02 5:45 ` Jung Daehwan
2023-01-03 18:52 ` Rob Herring
2022-12-30 16:34 ` Rob Herring
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=20230102062448.GC74470@ubuntu \
--to=dh10.jung@samsung.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eomji.oh@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=jh0801.jung@samsung.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=robh+dt@kernel.org \
--cc=sc.suh@samsung.com \
--cc=taehyun.cho@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).