xref: /openbmc/linux/drivers/net/usb/Kconfig (revision 55fd7e02)
1# SPDX-License-Identifier: GPL-2.0-only
2#
3# USB Network devices configuration
4#
5comment "Host-side USB support is needed for USB Network Adapter support"
6	depends on !USB && NET
7
8menuconfig USB_NET_DRIVERS
9	tristate "USB Network Adapters"
10	default USB if USB
11	depends on USB && NET
12
13if USB_NET_DRIVERS
14
15config USB_CATC
16	tristate "USB CATC NetMate-based Ethernet device support"
17	select CRC32
18	help
19	  Say Y if you want to use one of the following 10Mbps USB Ethernet
20	  device based on the EL1210A chip. Supported devices are:
21	  Belkin F5U011
22	  Belkin F5U111
23	  CATC NetMate
24	  CATC NetMate II
25	  smartBridges smartNIC
26
27	  This driver makes the adapter appear as a normal Ethernet interface,
28	  typically on eth0, if it is the only ethernet device, or perhaps on
29	  eth1, if you have a PCI or ISA ethernet card installed.
30
31	  To compile this driver as a module, choose M here: the
32	  module will be called catc.
33
34config USB_KAWETH
35	tristate "USB KLSI KL5USB101-based ethernet device support"
36	help
37	  Say Y here if you want to use one of the following 10Mbps only
38	  USB Ethernet adapters based on the KLSI KL5KUSB101B chipset:
39	  3Com 3C19250
40	  ADS USB-10BT
41	  ATEN USB Ethernet
42	  ASANTE USB To Ethernet Adapter
43	  AOX Endpoints USB Ethernet
44	  Correga K.K.
45	  D-Link DSB-650C and DU-E10
46	  Entrega / Portgear E45
47	  I-O DATA USB-ET/T
48	  Jaton USB Ethernet Device Adapter
49	  Kingston Technology USB Ethernet Adapter
50	  Linksys USB10T
51	  Mobility USB-Ethernet Adapter
52	  NetGear EA-101
53	  Peracom Enet and Enet2
54	  Portsmith Express Ethernet Adapter
55	  Shark Pocket Adapter
56	  SMC 2202USB
57	  Sony Vaio port extender
58
59	  This driver is likely to work with most 10Mbps only USB Ethernet
60	  adapters, including some "no brand" devices. It does NOT work on
61	  SmartBridges smartNIC or on Belkin F5U111 devices - you should use
62	  the CATC NetMate driver for those. If you are not sure which one
63	  you need, select both, and the correct one should be selected for
64	  you.
65
66	  This driver makes the adapter appear as a normal Ethernet interface,
67	  typically on eth0, if it is the only ethernet device, or perhaps on
68	  eth1, if you have a PCI or ISA ethernet card installed.
69
70	  To compile this driver as a module, choose M here: the
71	  module will be called kaweth.
72
73config USB_PEGASUS
74	tristate "USB Pegasus/Pegasus-II based ethernet device support"
75	select MII
76	help
77	  Say Y here if you know you have Pegasus or Pegasus-II based adapter.
78	  If in doubt then look at <file:drivers/net/usb/pegasus.h> for the
79	  complete list of supported devices.
80
81	  If your particular adapter is not in the list and you are _sure_ it
82	  is Pegasus or Pegasus II based then send me
83	  <petkan@users.sourceforge.net> vendor and device IDs.
84
85	  To compile this driver as a module, choose M here: the
86	  module will be called pegasus.
87
88config USB_RTL8150
89	tristate "USB RTL8150 based ethernet device support"
90	select MII
91	help
92	  Say Y here if you have RTL8150 based usb-ethernet adapter.
93	  Send me <petkan@users.sourceforge.net> any comments you may have.
94	  You can also check for updates at <http://pegasus2.sourceforge.net/>.
95
96	  To compile this driver as a module, choose M here: the
97	  module will be called rtl8150.
98
99config USB_RTL8152
100	tristate "Realtek RTL8152/RTL8153 Based USB Ethernet Adapters"
101	select MII
102	help
103	  This option adds support for Realtek RTL8152 based USB 2.0
104	  10/100 Ethernet adapters and RTL8153 based USB 3.0 10/100/1000
105	  Ethernet adapters.
106
107	  To compile this driver as a module, choose M here: the
108	  module will be called r8152.
109
110config USB_LAN78XX
111	tristate "Microchip LAN78XX Based USB Ethernet Adapters"
112	select MII
113	select PHYLIB
114	select MICROCHIP_PHY
115	select FIXED_PHY
116	help
117	  This option adds support for Microchip LAN78XX based USB 2
118	  & USB 3 10/100/1000 Ethernet adapters.
119	  LAN7800 : USB 3 to 10/100/1000 Ethernet adapter
120	  LAN7850 : USB 2 to 10/100/1000 Ethernet adapter
121	  LAN7801 : USB 3 to 10/100/1000 Ethernet adapter (MAC only)
122
123	  Proper PHY driver is required for LAN7801.
124
125	  To compile this driver as a module, choose M here: the
126	  module will be called lan78xx.
127
128config USB_USBNET
129	tristate "Multi-purpose USB Networking Framework"
130	select MII
131	help
132	  This driver supports several kinds of network links over USB,
133	  with "minidrivers" built around a common network driver core
134	  that supports deep queues for efficient transfers.  (This gives
135	  better performance with small packets and at high speeds).
136
137	  The USB host runs "usbnet", and the other end of the link might be:
138
139	  - Another USB host, when using USB "network" or "data transfer"
140	    cables.  These are often used to network laptops to PCs, like
141	    "Laplink" parallel cables or some motherboards.  These rely
142	    on specialized chips from many suppliers.
143
144	  - An intelligent USB gadget, perhaps embedding a Linux system.
145	    These include PDAs running Linux (iPaq, Yopy, Zaurus, and
146	    others), and devices that interoperate using the standard
147	    CDC-Ethernet specification (including many cable modems).
148
149	  - Network adapter hardware (like those for 10/100 Ethernet) which
150	    uses this driver framework.
151
152	  The link will appear with a name like "usb0", when the link is
153	  a two-node link, or "eth0" for most CDC-Ethernet devices.  Those
154	  two-node links are most easily managed with Ethernet Bridging
155	  (CONFIG_BRIDGE) instead of routing.
156
157	  For more information see <http://www.linux-usb.org/usbnet/>.
158
159	  To compile this driver as a module, choose M here: the
160	  module will be called usbnet.
161
162config USB_NET_AX8817X
163	tristate "ASIX AX88xxx Based USB 2.0 Ethernet Adapters"
164	depends on USB_USBNET
165	select CRC32
166	select PHYLIB
167	default y
168	help
169	  This option adds support for ASIX AX88xxx based USB 2.0
170	  10/100 Ethernet adapters.
171
172 	  This driver should work with at least the following devices:
173	    * Aten UC210T
174	    * ASIX AX88172
175	    * Billionton Systems, USB2AR
176	    * Billionton Systems, GUSB2AM-1G-B
177	    * Buffalo LUA-U2-KTX
178	    * Corega FEther USB2-TX
179	    * D-Link DUB-E100
180	    * Hawking UF200
181	    * Linksys USB200M
182	    * Netgear FA120
183	    * Sitecom LN-029
184	    * Sitecom LN-028
185	    * Intellinet USB 2.0 Ethernet
186	    * ST Lab USB 2.0 Ethernet
187	    * TrendNet TU2-ET100
188
189	  This driver creates an interface named "ethX", where X depends on
190	  what other networking devices you have in use.
191
192config USB_NET_AX88179_178A
193	tristate "ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet"
194	depends on USB_USBNET
195	select CRC32
196	select PHYLIB
197	default y
198	help
199	  This option adds support for ASIX AX88179 based USB 3.0/2.0
200	  to Gigabit Ethernet adapters.
201
202	  This driver should work with at least the following devices:
203	    * ASIX AX88179
204	    * ASIX AX88178A
205	    * Sitcomm LN-032
206
207	  This driver creates an interface named "ethX", where X depends on
208	  what other networking devices you have in use.
209
210config USB_NET_CDCETHER
211	tristate "CDC Ethernet support (smart devices such as cable modems)"
212	depends on USB_USBNET
213	default y
214	help
215	  This option supports devices conforming to the Communication Device
216	  Class (CDC) Ethernet Control Model, a specification that's easy to
217	  implement in device firmware.  The CDC specifications are available
218	  from <http://www.usb.org/>.
219
220	  CDC Ethernet is an implementation option for DOCSIS cable modems
221	  that support USB connectivity, used for non-Microsoft USB hosts.
222	  The Linux-USB CDC Ethernet Gadget driver is an open implementation.
223 	  This driver should work with at least the following devices:
224
225	    * Dell Wireless 5530 HSPA
226 	    * Ericsson PipeRider (all variants)
227	    * Ericsson Mobile Broadband Module (all variants)
228 	    * Motorola (DM100 and SB4100)
229 	    * Broadcom Cable Modem (reference design)
230	    * Toshiba (PCX1100U and F3507g/F3607gw)
231	    * ...
232
233	  This driver creates an interface named "ethX", where X depends on
234	  what other networking devices you have in use.  However, if the
235	  IEEE 802 "local assignment" bit is set in the address, a "usbX"
236	  name is used instead.
237
238config USB_NET_CDC_EEM
239	tristate "CDC EEM support"
240	depends on USB_USBNET
241	help
242	  This option supports devices conforming to the Communication Device
243	  Class (CDC) Ethernet Emulation Model, a specification that's easy to
244	  implement in device firmware.  The CDC EEM specifications are available
245	  from <http://www.usb.org/>.
246
247	  This driver creates an interface named "ethX", where X depends on
248	  what other networking devices you have in use.  However, if the
249	  IEEE 802 "local assignment" bit is set in the address, a "usbX"
250	  name is used instead.
251
252config USB_NET_CDC_NCM
253	tristate "CDC NCM support"
254	depends on USB_USBNET
255	default y
256	help
257	  This driver provides support for CDC NCM (Network Control Model
258	  Device USB Class Specification). The CDC NCM specification is
259	  available from <http://www.usb.org/>.
260
261	  Say "y" to link the driver statically, or "m" to build a
262	  dynamically linked module.
263
264	  This driver should work with at least the following devices:
265	    * ST-Ericsson M700 LTE FDD/TDD Mobile Broadband Modem (ref. design)
266	    * ST-Ericsson M5730 HSPA+ Mobile Broadband Modem (reference design)
267	    * ST-Ericsson M570 HSPA+ Mobile Broadband Modem (reference design)
268	    * ST-Ericsson M343 HSPA Mobile Broadband Modem (reference design)
269	    * Ericsson F5521gw Mobile Broadband Module
270
271config USB_NET_HUAWEI_CDC_NCM
272	tristate "Huawei NCM embedded AT channel support"
273	depends on USB_USBNET
274	select USB_WDM
275	select USB_NET_CDC_NCM
276	help
277		This driver supports huawei-style NCM devices, that use NCM as a
278		transport for other protocols, usually an embedded AT channel.
279		Good examples are:
280		* Huawei E3131
281		* Huawei E3251
282
283		To compile this driver as a module, choose M here: the module will be
284		called huawei_cdc_ncm.ko.
285
286config USB_NET_CDC_MBIM
287	tristate "CDC MBIM support"
288	depends on USB_USBNET
289	select USB_WDM
290	select USB_NET_CDC_NCM
291	help
292	  This driver provides support for CDC MBIM (Mobile Broadband
293	  Interface Model) devices. The CDC MBIM specification is
294	  available from <http://www.usb.org/>.
295
296	  MBIM devices require configuration using the management
297	  protocol defined by the MBIM specification.  This driver
298	  provides unfiltered access to the MBIM control channel
299	  through the associated /dev/cdc-wdmx character device.
300
301	  To compile this driver as a module, choose M here: the
302	  module will be called cdc_mbim.
303
304config USB_NET_DM9601
305	tristate "Davicom DM96xx based USB 10/100 ethernet devices"
306	depends on USB_USBNET
307	select CRC32
308	help
309	  This option adds support for Davicom DM9601/DM9620/DM9621A
310	  based USB 10/100 Ethernet adapters.
311
312config USB_NET_SR9700
313	tristate "CoreChip-sz SR9700 based USB 1.1 10/100 ethernet devices"
314	depends on USB_USBNET
315	select CRC32
316	help
317	  This option adds support for CoreChip-sz SR9700 based USB 1.1
318	  10/100 Ethernet adapters.
319
320config USB_NET_SR9800
321	tristate "CoreChip-sz SR9800 based USB 2.0 10/100 ethernet devices"
322	depends on USB_USBNET
323	select CRC32
324	help
325	  Say Y if you want to use one of the following 100Mbps USB Ethernet
326	  device based on the CoreChip-sz SR9800 chip.
327
328	  This driver makes the adapter appear as a normal Ethernet interface,
329	  typically on eth0, if it is the only ethernet device, or perhaps on
330	  eth1, if you have a PCI or ISA ethernet card installed.
331
332	  To compile this driver as a module, choose M here: the
333	  module will be called sr9800.
334
335config USB_NET_SMSC75XX
336	tristate "SMSC LAN75XX based USB 2.0 gigabit ethernet devices"
337	depends on USB_USBNET
338	select BITREVERSE
339	select CRC16
340	select CRC32
341	help
342	  This option adds support for SMSC LAN75XX based USB 2.0
343	  Gigabit Ethernet adapters.
344
345config USB_NET_SMSC95XX
346	tristate "SMSC LAN95XX based USB 2.0 10/100 ethernet devices"
347	depends on USB_USBNET
348	select BITREVERSE
349	select CRC16
350	select CRC32
351	help
352	  This option adds support for SMSC LAN95XX based USB 2.0
353	  10/100 Ethernet adapters.
354
355config USB_NET_GL620A
356	tristate "GeneSys GL620USB-A based cables"
357	depends on USB_USBNET
358	help
359	  Choose this option if you're using a host-to-host cable,
360	  or PC2PC motherboard, with this chip.
361
362	  Note that the half-duplex "GL620USB" is not supported.
363
364config USB_NET_NET1080
365	tristate "NetChip 1080 based cables (Laplink, ...)"
366	default y
367	depends on USB_USBNET
368	help
369	  Choose this option if you're using a host-to-host cable based
370	  on this design:  one NetChip 1080 chip and supporting logic,
371	  optionally with LEDs that indicate traffic
372
373config USB_NET_PLUSB
374	tristate "Prolific PL-2301/2302/25A1/27A1 based cables"
375	# if the handshake/init/reset problems, from original 'plusb',
376	# are ever resolved ... then remove "experimental"
377	depends on USB_USBNET
378	help
379	  Choose this option if you're using a host-to-host cable
380	  with one of these chips.
381
382config USB_NET_MCS7830
383	tristate "MosChip MCS7830 based Ethernet adapters"
384	depends on USB_USBNET
385	help
386	  Choose this option if you're using a 10/100 Ethernet USB2
387	  adapter based on the MosChip 7830 controller. This includes
388	  adapters marketed under the DeLOCK brand.
389
390config USB_NET_RNDIS_HOST
391	tristate "Host for RNDIS and ActiveSync devices"
392	depends on USB_USBNET
393	select USB_NET_CDCETHER
394	help
395	  This option enables hosting "Remote NDIS" USB networking links,
396	  as encouraged by Microsoft (instead of CDC Ethernet!) for use in
397	  various devices that may only support this protocol.  A variant
398	  of this protocol (with even less public documentation) seems to
399	  be at the root of Microsoft's "ActiveSync" too.
400
401	  Avoid using this protocol unless you have no better options.
402	  The protocol specification is incomplete, and is controlled by
403	  (and for) Microsoft; it isn't an "Open" ecosystem or market.
404
405config USB_NET_CDC_SUBSET_ENABLE
406	tristate
407	depends on USB_NET_CDC_SUBSET
408
409config USB_NET_CDC_SUBSET
410	tristate "Simple USB Network Links (CDC Ethernet subset)"
411	depends on USB_USBNET
412	default y
413	help
414	  This driver module supports USB network devices that can work
415	  without any device-specific information.  Select it if you have
416	  one of these drivers.
417
418	  Note that while many USB host-to-host cables can work in this mode,
419	  that may mean not being able to talk to Win32 systems or more
420	  commonly not being able to handle certain events (like replugging
421	  the host on the other end) very well.  Also, these devices will
422	  not generally have permanently assigned Ethernet addresses.
423
424config USB_ALI_M5632
425	bool "ALi M5632 based 'USB 2.0 Data Link' cables"
426	depends on USB_NET_CDC_SUBSET
427	select USB_NET_CDC_SUBSET_ENABLE
428	help
429	  Choose this option if you're using a host-to-host cable
430	  based on this design, which supports USB 2.0 high speed.
431
432config USB_AN2720
433	bool "AnchorChips 2720 based cables (Xircom PGUNET, ...)"
434	depends on USB_NET_CDC_SUBSET
435	select USB_NET_CDC_SUBSET_ENABLE
436	help
437	  Choose this option if you're using a host-to-host cable
438	  based on this design.  Note that AnchorChips is now a
439	  Cypress brand.
440
441config USB_BELKIN
442	bool "eTEK based host-to-host cables (Advance, Belkin, ...)"
443	depends on USB_NET_CDC_SUBSET
444	select USB_NET_CDC_SUBSET_ENABLE
445	default y
446	help
447	  Choose this option if you're using a host-to-host cable
448	  based on this design:  two NetChip 2890 chips and an Atmel
449	  microcontroller, with LEDs that indicate traffic.
450
451config USB_ARMLINUX
452	bool "Embedded ARM Linux links (iPaq, ...)"
453	depends on USB_NET_CDC_SUBSET
454	select USB_NET_CDC_SUBSET_ENABLE
455	default y
456	help
457	  Choose this option to support the "usb-eth" networking driver
458	  used by most of the ARM Linux community with device controllers
459	  such as the SA-11x0 and PXA-25x UDCs, or the tftp capabilities
460	  in some PXA versions of the "blob" boot loader.
461
462	  Linux-based "Gumstix" PXA-25x based systems use this protocol
463	  to talk with other Linux systems.
464
465	  Although the ROMs shipped with Sharp Zaurus products use a
466	  different link level framing protocol, you can have them use
467	  this simpler protocol by installing a different kernel.
468
469config USB_EPSON2888
470	bool "Epson 2888 based firmware (DEVELOPMENT)"
471	depends on USB_NET_CDC_SUBSET
472	select USB_NET_CDC_SUBSET_ENABLE
473	help
474	  Choose this option to support the usb networking links used
475	  by some sample firmware from Epson.
476
477config USB_KC2190
478	bool "KT Technology KC2190 based cables (InstaNet)"
479	depends on USB_NET_CDC_SUBSET
480	select USB_NET_CDC_SUBSET_ENABLE
481	help
482	  Choose this option if you're using a host-to-host cable
483	  with one of these chips.
484
485config USB_NET_ZAURUS
486	tristate "Sharp Zaurus (stock ROMs) and compatible"
487	depends on USB_USBNET
488	select USB_NET_CDCETHER
489	select CRC32
490	default y
491	help
492	  Choose this option to support the usb networking links used by
493	  Zaurus models like the SL-5000D, SL-5500, SL-5600, A-300, B-500.
494	  This also supports some related device firmware, as used in some
495	  PDAs from Olympus and some cell phones from Motorola.
496
497	  If you install an alternate image, such as the Linux 2.6 based
498	  versions of OpenZaurus, you should no longer need to support this
499	  protocol.  Only the "eth-fd" or "net_fd" drivers in these devices
500	  really need this non-conformant variant of CDC Ethernet (or in
501	  some cases CDC MDLM) protocol, not "g_ether".
502
503config USB_NET_CX82310_ETH
504	tristate "Conexant CX82310 USB ethernet port"
505	depends on USB_USBNET
506	help
507	  Choose this option if you're using a Conexant CX82310-based ADSL
508	  router with USB ethernet port. This driver is for routers only,
509	  it will not work with ADSL modems (use cxacru driver instead).
510
511config USB_NET_KALMIA
512	tristate "Samsung Kalmia based LTE USB modem"
513	depends on USB_USBNET
514	help
515	  Choose this option if you have a Samsung Kalmia based USB modem
516	  as Samsung GT-B3730.
517
518	  To compile this driver as a module, choose M here: the
519	  module will be called kalmia.
520
521config USB_NET_QMI_WWAN
522	tristate "QMI WWAN driver for Qualcomm MSM based 3G and LTE modems"
523	depends on USB_USBNET
524	select USB_WDM
525	help
526	  Support WWAN LTE/3G devices based on Qualcomm Mobile Data Modem
527	  (MDM) chipsets.  Examples of such devices are
528	    * Huawei E392/E398
529
530	  This driver will only drive the ethernet part of the chips.
531	  The devices require additional configuration to be usable.
532	  Multiple management interfaces with linux drivers are
533	  available:
534
535	    * option: AT commands on /dev/ttyUSBx
536	    * cdc-wdm: Qualcomm MSM Interface (QMI) protocol on /dev/cdc-wdmx
537
538	  A modem manager with support for QMI is recommended.
539
540	  To compile this driver as a module, choose M here: the
541	  module will be called qmi_wwan.
542
543config USB_HSO
544	tristate "Option USB High Speed Mobile Devices"
545	depends on USB && RFKILL && TTY
546	default n
547	help
548	  Choose this option if you have an Option HSDPA/HSUPA card.
549	  These cards support downlink speeds of 7.2Mbps or greater.
550
551	  To compile this driver as a module, choose M here: the
552	  module will be called hso.
553
554config USB_NET_INT51X1
555	tristate "Intellon PLC based usb adapter"
556	depends on USB_USBNET
557	help
558	  Choose this option if you're using a 14Mb USB-based PLC
559	  (Powerline Communications) solution with an Intellon
560	  INT51x1/INT5200 chip, like the "devolo dLan duo".
561
562config USB_CDC_PHONET
563	tristate "CDC Phonet support"
564	depends on PHONET && USB_USBNET
565	help
566	  Choose this option to support the Phonet interface to a Nokia
567	  cellular modem, as found on most Nokia handsets with the
568	  "PC suite" USB profile.
569
570config USB_IPHETH
571	tristate "Apple iPhone USB Ethernet driver"
572	default n
573	help
574	  Module used to share Internet connection (tethering) from your
575	  iPhone (Original, 3G and 3GS) to your system.
576	  Note that you need userspace libraries and programs that are needed
577	  to pair your device with your system and that understand the iPhone
578	  protocol.
579
580	  For more information: http://giagio.com/wiki/moin.cgi/iPhoneEthernetDriver
581
582config USB_SIERRA_NET
583	tristate "USB-to-WWAN Driver for Sierra Wireless modems"
584	depends on USB_USBNET
585	help
586	  Choose this option if you have a Sierra Wireless USB-to-WWAN device.
587
588	  To compile this driver as a module, choose M here: the
589	  module will be called sierra_net.
590
591config USB_VL600
592	tristate "LG VL600 modem dongle"
593	depends on USB_NET_CDCETHER && TTY
594	select USB_ACM
595	help
596	  Select this if you want to use an LG Electronics 4G/LTE usb modem
597	  called VL600.  This driver only handles the ethernet
598	  interface exposed by the modem firmware.  To establish a connection
599	  you will first need a userspace program that sends the right
600	  command to the modem through its CDC ACM port, and most
601	  likely also a DHCP client.  See this thread about using the
602	  4G modem from Verizon:
603
604	  http://ubuntuforums.org/showpost.php?p=10589647&postcount=17
605
606config USB_NET_CH9200
607	tristate "QingHeng CH9200 USB ethernet support"
608	depends on USB_USBNET
609	select MII
610	help
611	  Choose this option if you have a USB ethernet adapter with a QinHeng
612	  CH9200 chipset.
613
614	  To compile this driver as a module, choose M here: the
615	  module will be called ch9200.
616
617config USB_NET_AQC111
618	tristate "Aquantia AQtion USB to 5/2.5GbE Controllers support"
619	depends on USB_USBNET
620	select CRC32
621	help
622	  This option adds support for Aquantia AQtion USB
623	  Ethernet adapters based on AQC111U/AQC112 chips.
624
625	  This driver should work with at least the following devices:
626	  * Aquantia AQtion USB to 5GbE
627
628endif # USB_NET_DRIVERS
629