Commit e4157519 authored by Randy Dunlap's avatar Randy Dunlap Committed by Greg Kroah-Hartman

Documentation: usb: correct spelling

Correct spelling problems for Documentation/usb/ as reported
by codespell.
Signed-off-by: default avatarRandy Dunlap <rdunlap@infradead.org>
Cc: linux-usb@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org
Link: https://lore.kernel.org/r/20230127064005.1558-33-rdunlap@infradead.orgSigned-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
parent 2d83eb5d
...@@ -35,10 +35,10 @@ which can show otg fsm variables and some controller registers value:: ...@@ -35,10 +35,10 @@ which can show otg fsm variables and some controller registers value::
1) Power up 2 Freescale i.MX6Q sabre SD boards with gadget class driver loaded 1) Power up 2 Freescale i.MX6Q sabre SD boards with gadget class driver loaded
(e.g. g_mass_storage). (e.g. g_mass_storage).
2) Connect 2 boards with usb cable with one end is micro A plug, the other end 2) Connect 2 boards with usb cable: one end is micro A plug, the other end
is micro B plug. is micro B plug.
The A-device(with micro A plug inserted) should enumerate B-device. The A-device (with micro A plug inserted) should enumerate B-device.
3) Role switch 3) Role switch
...@@ -54,18 +54,19 @@ which can show otg fsm variables and some controller registers value:: ...@@ -54,18 +54,19 @@ which can show otg fsm variables and some controller registers value::
echo 0 > /sys/bus/platform/devices/ci_hdrc.0/inputs/b_bus_req echo 0 > /sys/bus/platform/devices/ci_hdrc.0/inputs/b_bus_req
or, by introducing HNP polling, B-Host can know when A-peripheral wish or, by introducing HNP polling, B-Host can know when A-peripheral wishes to
to be host role, so this role switch also can be trigged in A-peripheral be in the host role, so this role switch also can be triggered in
side by answering the polling from B-Host, this can be done on A-device:: A-peripheral side by answering the polling from B-Host. This can be done on
A-device::
echo 1 > /sys/bus/platform/devices/ci_hdrc.0/inputs/a_bus_req echo 1 > /sys/bus/platform/devices/ci_hdrc.0/inputs/a_bus_req
A-device should switch back to host and enumerate B-device. A-device should switch back to host and enumerate B-device.
5) Remove B-device(unplug micro B plug) and insert again in 10 seconds, 5) Remove B-device (unplug micro B plug) and insert again in 10 seconds;
A-device should enumerate B-device again. A-device should enumerate B-device again.
6) Remove B-device(unplug micro B plug) and insert again after 10 seconds, 6) Remove B-device (unplug micro B plug) and insert again after 10 seconds;
A-device should NOT enumerate B-device. A-device should NOT enumerate B-device.
if A-device wants to use bus: if A-device wants to use bus:
...@@ -105,7 +106,7 @@ July 27, 2012 Revision 2.0 version 1.1a" ...@@ -105,7 +106,7 @@ July 27, 2012 Revision 2.0 version 1.1a"
2. How to enable USB as system wakeup source 2. How to enable USB as system wakeup source
-------------------------------------------- --------------------------------------------
Below is the example for how to enable USB as system wakeup source Below is the example for how to enable USB as system wakeup source
at imx6 platform. on an imx6 platform.
2.1 Enable core's wakeup:: 2.1 Enable core's wakeup::
...@@ -128,6 +129,6 @@ at imx6 platform. ...@@ -128,6 +129,6 @@ at imx6 platform.
echo enabled > /sys/bus/usb/devices/1-1/power/wakeup echo enabled > /sys/bus/usb/devices/1-1/power/wakeup
If the system has only one usb port, and you want usb wakeup at this port, you If the system has only one usb port, and you want usb wakeup at this port, you
can use below script to enable usb wakeup:: can use the below script to enable usb wakeup::
for i in $(find /sys -name wakeup | grep usb);do echo enabled > $i;done; for i in $(find /sys -name wakeup | grep usb);do echo enabled > $i;done;
...@@ -813,7 +813,7 @@ the user must provide the following: ...@@ -813,7 +813,7 @@ the user must provide the following:
================== ==================================================== ================== ====================================================
Each frame description contains frame interval specification, and each Each frame description contains frame interval specification, and each
such specification consists of a number of lines with an inverval value such specification consists of a number of lines with an interval value
in each line. The rules stated above are best illustrated with an example:: in each line. The rules stated above are best illustrated with an example::
# mkdir functions/uvc.usb0/control/header/h # mkdir functions/uvc.usb0/control/header/h
......
...@@ -150,7 +150,7 @@ Module parameters ...@@ -150,7 +150,7 @@ Module parameters
- bcdDevice -- USB Device version (BCD) (16 bit integer) - bcdDevice -- USB Device version (BCD) (16 bit integer)
- iManufacturer -- USB Manufacturer string (string) - iManufacturer -- USB Manufacturer string (string)
- iProduct -- USB Product string (string) - iProduct -- USB Product string (string)
- iSerialNumber -- SerialNumber string (sting) - iSerialNumber -- SerialNumber string (string)
sysfs entries sysfs entries
============= =============
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment