From: "Stanley Chang[昌育德]" <stanley_chang@realtek.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Alan Stern <stern@rowland.harvard.edu>,
Roy Luo <royluo@google.com>, Matthias Kaehlcke <mka@chromium.org>,
Douglas Anderson <dianders@chromium.org>,
Flavio Suligoi <f.suligoi@asem.it>, Ray Chi <raychi@google.com>,
"linux-phy@lists.infradead.org" <linux-phy@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: RE: [PATCH v7 1/5] usb: phy: add usb phy notify port status API
Date: Mon, 24 Jul 2023 08:46:18 +0000 [thread overview]
Message-ID: <832fc6ec78074b49a719221ccefd2d90@realtek.com> (raw)
In-Reply-To: 2023072454-mosaic-ogle-9a27@gregkh
Hi Greg,
> > > > > +
> > > > > + if (!ret) {
> > > > > + struct usb_device *hdev = hub->hdev;
> > > > > +
> > > > > + if (hdev && !hdev->parent) {
> > > >
> > > > Why the check for no parent? Please document that here in a
> comment.
> > >
> > > I will add a comment :
> > > /* Only notify roothub. That is, when hdev->parent is empty. */
> >
> > Also document this that this will only happen for root hub status
> > changes, that's not obvious in the callback name or documentation or
> anywhere else here.
>
> All usb phy notifications (connection, disconnection) are only for roothub.
> So I don't special to doc this.
I will add the comment:
/*
* Applies to roothub only. That is, when hdev->parent is
* empty. Only the roothub will be notified of port state
* changes, since the USB PHY only cares about changes at
* the next level.
*/
Thanks,
Stanley
prev parent reply other threads:[~2023-07-24 8:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 6:47 [PATCH v7 1/5] usb: phy: add usb phy notify port status API Stanley Chang
2023-07-07 6:47 ` [PATCH v7 2/5] phy: realtek: usb: Add driver for the Realtek SoC USB 2.0 PHY Stanley Chang
2023-07-07 6:47 ` [PATCH v7 3/5] phy: realtek: usb: Add driver for the Realtek SoC USB 3.0 PHY Stanley Chang
2023-07-07 6:47 ` [PATCH v7 4/5] dt-bindings: phy: realtek: Add Realtek DHC RTD SoC USB 2.0 PHY Stanley Chang
2023-07-14 14:33 ` Rob Herring
2023-07-14 14:33 ` Rob Herring
2023-07-07 6:47 ` [PATCH v7 5/5] dt-bindings: phy: realtek: Add Realtek DHC RTD SoC USB 3.0 PHY Stanley Chang
2023-07-14 14:33 ` Rob Herring
2023-07-14 14:33 ` Rob Herring
2023-07-24 5:50 ` [PATCH v7 1/5] usb: phy: add usb phy notify port status API Greg Kroah-Hartman
2023-07-24 5:50 ` Greg Kroah-Hartman
2023-07-24 6:49 ` Stanley Chang[昌育德]
2023-07-24 7:06 ` Greg Kroah-Hartman
2023-07-24 7:06 ` Greg Kroah-Hartman
2023-07-24 7:33 ` Stanley Chang[昌育德]
2023-07-24 8:46 ` Stanley Chang[昌育德] [this message]
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=832fc6ec78074b49a719221ccefd2d90@realtek.com \
--to=stanley_chang@realtek.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=f.suligoi@asem.it \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=mka@chromium.org \
--cc=raychi@google.com \
--cc=robh+dt@kernel.org \
--cc=royluo@google.com \
--cc=stern@rowland.harvard.edu \
--cc=vkoul@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.