| 1 |
2 |
dimamali |
Gaisler USB 2.0 Host Controller enable
|
| 2 |
|
|
CONFIG_GRUSBHC_ENABLE
|
| 3 |
|
|
Say Y here to enable the Gaisler Research USB 2.0 Host Controller.
|
| 4 |
|
|
The core contains one EHCI controller which can be configured to
|
| 5 |
|
|
contain 0 to 15 UHCI companion controllers. The controller can also
|
| 6 |
|
|
be configured to exclude the EHCI controller. The EHCI controller
|
| 7 |
|
|
contains one AHB master interface to access memory and one APB slave
|
| 8 |
|
|
for accessing control registers. The UHCI controller contains one AHB
|
| 9 |
|
|
master interface for accessing memory and one AHB slave interface for
|
| 10 |
|
|
accessing control registers.
|
| 11 |
|
|
|
| 12 |
|
|
Gaisler Enhanced Host Controller enable
|
| 13 |
|
|
CONFIG_GRUSBHC_EHC
|
| 14 |
|
|
Say Y here to enable the Gaisler Research Enhanced Host Controller.
|
| 15 |
|
|
This USB 2.0 controller implements the Enhanced Host Controller
|
| 16 |
|
|
Interface and supports High-Speed USB traffic.
|
| 17 |
|
|
|
| 18 |
|
|
Gaisler Universal Host Controller enable
|
| 19 |
|
|
CONFIG_GRUSBHC_UHC
|
| 20 |
|
|
Say Y here to enable the Gaisler Research Universal Host Controller.
|
| 21 |
|
|
This USB 1.1 controller implements the Universal Host Controller
|
| 22 |
|
|
Interface and supports Full- and Low-Speed USB traffic. Controllers
|
| 23 |
|
|
of this type will be configured as companion controllers if the
|
| 24 |
|
|
Enhanced Host Controller is enabled.
|
| 25 |
|
|
|
| 26 |
|
|
CONFIG_GRUSBHC_NCC
|
| 27 |
|
|
Number of companion (universal) host controllers. A universal host
|
| 28 |
|
|
controller may handle up to fifteen ports. Some designers choose
|
| 29 |
|
|
to implement one universal host controller per port. If you are
|
| 30 |
|
|
unsure, set this value to 1 to let one controller handle all ports.
|
| 31 |
|
|
|
| 32 |
|
|
CONFIG_GRUSBHC_NPORTS
|
| 33 |
|
|
Number of transceivers connected to the core.
|
| 34 |
|
|
|
| 35 |
|
|
CONFIG_GRUSBHC_ULPI
|
| 36 |
|
|
Select the interface of the transceiver(s) that the core will be
|
| 37 |
|
|
connected to.
|
| 38 |
|
|
|
| 39 |
|
|
CONFIG_GRUSBHC_VBUSEXT
|
| 40 |
|
|
Selects the source for bus power generation. Select External if
|
| 41 |
|
|
external USB power switch is used (recommended for USB hosts) or
|
| 42 |
|
|
select Internal if not USB power switch is present and ULPI
|
| 43 |
|
|
transceiver should generate VBUS.
|
| 44 |
|
|
|
| 45 |
|
|
CONFIG_GRUSBHC_FAULTL
|
| 46 |
|
|
Selects active level of fault signal from external USB power switch.
|
| 47 |
|
|
Select None if the external USB power switch does'nt have fault
|
| 48 |
|
|
detection.
|
| 49 |
|
|
|
| 50 |
|
|
CONFIG_GRUSBHC_ENABLEH
|
| 51 |
|
|
Selects the active level of the outgoing vbus enable signal
|
| 52 |
|
|
(connected between the core's drvvbus output and a USB power switch
|
| 53 |
|
|
enable input). The UTMI+ specification defines the drvvbus signal to be
|
| 54 |
|
|
active high, but GRUSBHC can be configured with an active low
|
| 55 |
|
|
drvvbus in order to support more USB power switches without the
|
| 56 |
|
|
need for an external inverter.
|
| 57 |
|
|
|
| 58 |
|
|
CONFIG_GRUSBHC_FAULT2H
|
| 59 |
|
|
Selects the active level of the incoming vbus valid indicator
|
| 60 |
|
|
(connected between the core's vbusvalid input and a USB power switch
|
| 61 |
|
|
fault ouput). The UTMI+ specification defines the vbusvalid signal to be
|
| 62 |
|
|
active high, but GRUSBHC can be configured with an active low
|
| 63 |
|
|
vbusvalid in order to support more USB power switches without the
|
| 64 |
|
|
need for an external inverter.
|
| 65 |
|
|
|
| 66 |
|
|
CONFIG_GRUSBHC_ENDIAN
|
| 67 |
|
|
The host controller works internally with little endian. If the
|
| 68 |
|
|
controller is connected to a big endian bus (such as the AMBA bus
|
| 69 |
|
|
in GRLIB) endian conversion must be enabled.
|
| 70 |
|
|
|
| 71 |
|
|
CONFIG_GRUSBHC_BEREGS
|
| 72 |
|
|
With this option enabled the register space will be arranged
|
| 73 |
|
|
according to big endian addressing. If this option is
|
| 74 |
|
|
not enabled the register space of both controllers will be
|
| 75 |
|
|
byte swapped. See the IP core user's manual for details.
|
| 76 |
|
|
|
| 77 |
|
|
CONFIG_GRUSBHC_BEDESC
|
| 78 |
|
|
With this option enabled the in-memory transfer descriptors will
|
| 79 |
|
|
be in big endian format. Without this option software must byte
|
| 80 |
|
|
swap all descriptors.
|
| 81 |
|
|
|
| 82 |
|
|
CONFIG_GRUSBHC_BWRD
|
| 83 |
|
|
Maximum burst length in words.
|
| 84 |
|
|
|
| 85 |
|
|
CONFIG_GRUSBHC_NPCC
|
| 86 |
|
|
Number of ports per companion controller. This option must be
|
| 87 |
|
|
consistent with number of ports and number of companion
|
| 88 |
|
|
controllers. Number of companion controller multiplied with
|
| 89 |
|
|
this value may not be less than the total number of ports.
|
| 90 |
|
|
In addition, there can not be a companion controller that is left
|
| 91 |
|
|
without ports.
|
| 92 |
|
|
|
| 93 |
|
|
CONFIG_GRUSBHC_PRR
|
| 94 |
|
|
If CONFIG_GRUSBHC_PRR are disabled the lowest CONFIG_GRUSBHC_NPCC
|
| 95 |
|
|
ports are routed to the lowest numbered companion controller and
|
| 96 |
|
|
so on. If CONFIG_GRUSBHC_PRR is enabled each port can be
|
| 97 |
|
|
individually routed to a specific companion controller.
|
| 98 |
|
|
|
| 99 |
|
|
|
| 100 |
|
|
CONFIG_GRUSBHC_PR1
|
| 101 |
|
|
The companion controller that port 1 should be routed to. Unused
|
| 102 |
|
|
ports should have their value set to 0.
|
| 103 |
|
|
|
| 104 |
|
|
CONFIG_GRUSBHC_PR2
|
| 105 |
|
|
The companion controller that port 2 should be routed to. Unused
|
| 106 |
|
|
ports should have their value set to 0.
|
| 107 |
|
|
|
| 108 |
|
|
CONFIG_GRUSBHC_PR3
|
| 109 |
|
|
The companion controller that port 3 should be routed to. Unused
|
| 110 |
|
|
ports should have their value set to 0.
|
| 111 |
|
|
|
| 112 |
|
|
CONFIG_GRUSBHC_PR4
|
| 113 |
|
|
The companion controller that port 4 should be routed to. Unused
|
| 114 |
|
|
ports should have their value set to 0.
|
| 115 |
|
|
|
| 116 |
|
|
CONFIG_GRUSBHC_PR5
|
| 117 |
|
|
The companion controller that port 5 should be routed to. Unused
|
| 118 |
|
|
ports should have their value set to 0.
|
| 119 |
|
|
|
| 120 |
|
|
CONFIG_GRUSBHC_PR6
|
| 121 |
|
|
The companion controller that port 6 should be routed to. Unused
|
| 122 |
|
|
ports should have their value set to 0.
|
| 123 |
|
|
|
| 124 |
|
|
CONFIG_GRUSBHC_PR7
|
| 125 |
|
|
The companion controller that port 7 should be routed to. Unused
|
| 126 |
|
|
ports should have their value set to 0.
|
| 127 |
|
|
|
| 128 |
|
|
CONFIG_GRUSBHC_PR8
|
| 129 |
|
|
The companion controller that port 8 should be routed to. Unused
|
| 130 |
|
|
ports should have their value set to 0.
|
| 131 |
|
|
|
| 132 |
|
|
CONFIG_GRUSBHC_PR9
|
| 133 |
|
|
The companion controller that port 9 should be routed to. Unused
|
| 134 |
|
|
ports should have their value set to 0.
|
| 135 |
|
|
|
| 136 |
|
|
CONFIG_GRUSBHC_PR10
|
| 137 |
|
|
The companion controller that port 10 should be routed to. Unused
|
| 138 |
|
|
ports should have their value set to 0.
|
| 139 |
|
|
|
| 140 |
|
|
CONFIG_GRUSBHC_PR11
|
| 141 |
|
|
The companion controller that port 11 should be routed to. Unused
|
| 142 |
|
|
ports should have their value set to 0.
|
| 143 |
|
|
|
| 144 |
|
|
CONFIG_GRUSBHC_PR12
|
| 145 |
|
|
The companion controller that port 12 should be routed to. Unused
|
| 146 |
|
|
ports should have their value set to 0.
|
| 147 |
|
|
|
| 148 |
|
|
CONFIG_GRUSBHC_PR13
|
| 149 |
|
|
The companion controller that port 13 should be routed to. Unused
|
| 150 |
|
|
ports should have their value set to 0.
|
| 151 |
|
|
|
| 152 |
|
|
CONFIG_GRUSBHC_PR14
|
| 153 |
|
|
The companion controller that port 14 should be routed to. Unused
|
| 154 |
|
|
ports should have their value set to 0.
|
| 155 |
|
|
|
| 156 |
|
|
CONFIG_GRUSBHC_PR15
|
| 157 |
|
|
The companion controller that port 15 should be routed to. Unused
|
| 158 |
|
|
ports should have their value set to 0.
|
| 159 |
|
|
|
