linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Peter Chen <peter.chen@nxp.com>
Cc: Peter Chen <hzpeterchen@gmail.com>,
	USB list <linux-usb@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] USB: Fix up terminology
Date: Wed, 1 Jul 2020 08:50:51 +0200	[thread overview]
Message-ID: <20200701065051.GB2044019@kroah.com> (raw)
In-Reply-To: <DB8PR04MB7162C271B04650CBCC87729D8B6C0@DB8PR04MB7162.eurprd04.prod.outlook.com>

On Wed, Jul 01, 2020 at 06:40:20AM +0000, Peter Chen wrote:
>  
> > 
> > On Wed, Jul 01, 2020 at 02:02:00PM +0800, Peter Chen wrote:
> > > > index 3a7179e90f4e..1a12aab208b4 100644
> > > > --- a/drivers/usb/gadget/udc/Kconfig
> > > > +++ b/drivers/usb/gadget/udc/Kconfig
> > > > @@ -474,7 +474,7 @@ config USB_DUMMY_HCD
> > > >         help
> > > >           This host controller driver emulates USB, looping all data transfer
> > > >           requests back to a USB "gadget driver" in the same host.  The host
> > > > -         side is the master; the gadget side is the slave.  Gadget drivers
> > > > +         side is the controller; the gadget side is the device.  Gadget drivers
> > >
> > > 'the host side is the controller' may not be suitable.
> > 
> > Really?  It is literally a "host controller" as per the specification :)
> 
> You are right. At first, I thought, there are device controller, host controller and dual-role
> controller, why you only said, "the host side is the controller"? After checking USB 3.0 spec,
> there are only "device", "host" and "host controller" at its Terms and Abbreviations.
> 
> device
> A logical or physical entity that performs one or more functions. The actual entity
> described depends on the context of the reference. At the lowest level, device may refer
> to a single hardware component, as in a memory device. At a higher level, it may refer to
> a collection of hardware components that perform a particular function, such as a USB
> interface device. At an even higher level, device may refer to the function performed by
> an entity attached to the USB. Devices may be physical, electrical, addressable, and
> logical.
> When used as a non-specific reference, a USB device is either a hub or a peripheral
> device.
> 
> host
> The host computer system where the USB host controller is installed. This includes the
> host hardware platform (CPU, bus, etc.) and the operating system in use.
> 
> host controller
> The interface provided to the system to support devices on the USB.

Thanks for the confirmation.  This is why we had to "invent" the term
"gadget" to describe the code that runs in the device to try to reduce
the confusion here.

greg k-h

  reply	other threads:[~2020-07-01  6:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-30 17:41 [PATCH] USB: Fix up terminology Greg Kroah-Hartman
2020-07-01  6:02 ` Peter Chen
2020-07-01  6:29   ` Greg Kroah-Hartman
2020-07-01  6:40     ` Peter Chen
2020-07-01  6:50       ` Greg Kroah-Hartman [this message]
2020-07-01  6:36 ` Felipe Balbi
2020-07-01  6:48   ` Greg Kroah-Hartman

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=20200701065051.GB2044019@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=hzpeterchen@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=peter.chen@nxp.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).