mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: Matthias Kaehlcke <mka@chromium.org>
Cc: Doug Anderson <dianders@chromium.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Rob Herring <robh+dt@kernel.org>,
	Frank Rowand <frowand.list@gmail.com>,
	Mathias Nyman <mathias.nyman@intel.com>,
	Felipe Balbi <balbi@kernel.org>,
	Michal Simek <michal.simek@xilinx.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Stephen Boyd <swboyd@chromium.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>, Bastien Nocera <hadess@hadess.net>,
	Peter Chen <peter.chen@kernel.org>,
	Ravi Chandra Sadineni <ravisadineni@chromium.org>,
	Roger Quadros <rogerq@kernel.org>,
	Linux USB List <linux-usb@vger.kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Souradeep Chowdhury <quic_schowdhu@quicinc.com>
Subject: Re: [PATCH v22 2/3] usb: misc: Add onboard_usb_hub driver
Date: Mon, 27 Jun 2022 15:37:10 -0400	[thread overview]
Message-ID: <YroG5keFWVJo8JVR@rowland.harvard.edu> (raw)
In-Reply-To: <Yrn/rfrzSWod5SCT@google.com>

On Mon, Jun 27, 2022 at 12:06:21PM -0700, Matthias Kaehlcke wrote:
> On Mon, Jun 27, 2022 at 02:54:03PM -0400, Alan Stern wrote:
> > On Mon, Jun 27, 2022 at 11:14:47AM -0700, Matthias Kaehlcke wrote:
> > > 
> > >   Further there must be only one platform device for onboard hubs with a
> > >   companion hub (the hub is a single physical device). To achieve this two
> > 
> > What do you mean by "companion hub"?  I think you are using the wrong 
> > word here.  If you're talking about the relation between the two logical 
> > hubs (one attached to the SuperSpeed bus and one attached to the 
> > Low/Full/High-speed bus) within a physical USB-3 hub, the correct term 
> > for this is "peer".  See the existing usages in hub.h, hub.c, and 
> > port.c.
> > 
> > "Companion" refers to something completely different (i.e., the UHCI or 
> > OHCI controllers that handle Low/Full-speed connections on behalf of a 
> > High-speed EHCI controller).
> 
> Yes it's the relation between the two logical hub. The term 'companion-hub'
> stems from the binding and has been around since v6 of this series. I guess
> we should update the binding if the terminology isn't correct.

That sounds like a good idea.

Alan Stern

  reply	other threads:[~2022-06-27 19:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09 19:19 [PATCH v22 0/3] " Matthias Kaehlcke
2022-06-09 19:19 ` [PATCH v22 1/3] of/platform: Add stubs for of_platform_device_create/destroy() Matthias Kaehlcke
2022-06-09 19:19 ` [PATCH v22 2/3] usb: misc: Add onboard_usb_hub driver Matthias Kaehlcke
2022-06-15 21:09   ` Doug Anderson
2022-06-15 23:22     ` Matthias Kaehlcke
2022-06-16 20:12       ` Doug Anderson
2022-06-16 21:08         ` Matthias Kaehlcke
2022-06-16 21:28           ` Doug Anderson
2022-06-16 22:01             ` Matthias Kaehlcke
2022-06-16 22:46               ` Doug Anderson
2022-06-17  0:36                 ` Matthias Kaehlcke
2022-06-17 15:09                   ` Doug Anderson
2022-06-17 16:34                     ` Matthias Kaehlcke
2022-06-24 20:33                       ` Doug Anderson
2022-06-27 18:14                         ` Matthias Kaehlcke
2022-06-27 18:54                           ` Alan Stern
2022-06-27 19:06                             ` Matthias Kaehlcke
2022-06-27 19:37                               ` Alan Stern [this message]
2022-06-29 19:53                           ` Doug Anderson
2022-06-09 19:20 ` [PATCH v22 3/3] usb: core: hub: Create platform devices for onboard hubs in hub_probe() Matthias Kaehlcke
2022-06-15 21:10   ` Doug Anderson

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=YroG5keFWVJo8JVR@rowland.harvard.edu \
    --to=stern@rowland.harvard.edu \
    --cc=balbi@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=frowand.list@gmail.com \
    --cc=geert+renesas@glider.be \
    --cc=gregkh@linuxfoundation.org \
    --cc=hadess@hadess.net \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=michal.simek@xilinx.com \
    --cc=mka@chromium.org \
    --cc=peter.chen@kernel.org \
    --cc=quic_schowdhu@quicinc.com \
    --cc=ravisadineni@chromium.org \
    --cc=robh+dt@kernel.org \
    --cc=rogerq@kernel.org \
    --cc=swboyd@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®