Home
last modified time | relevance | path

Searched refs:interfaces (Results 1 – 25 of 891) sorted by relevance

12345678910>>...36

/linux/drivers/net/phy/
A Dsfp-bus.c178 __set_bit(PHY_INTERFACE_MODE_10GBASER, interfaces); in sfp_parse_support()
182 __set_bit(PHY_INTERFACE_MODE_10GBASER, interfaces); in sfp_parse_support()
186 __set_bit(PHY_INTERFACE_MODE_10GBASER, interfaces); in sfp_parse_support()
190 __set_bit(PHY_INTERFACE_MODE_10GBASER, interfaces); in sfp_parse_support()
202 __set_bit(PHY_INTERFACE_MODE_SGMII, interfaces); in sfp_parse_support()
215 __set_bit(PHY_INTERFACE_MODE_100BASEX, interfaces); in sfp_parse_support()
219 __set_bit(PHY_INTERFACE_MODE_100BASEX, interfaces); in sfp_parse_support()
270 __set_bit(PHY_INTERFACE_MODE_25GBASER, interfaces); in sfp_parse_support()
282 __set_bit(PHY_INTERFACE_MODE_25GBASER, interfaces); in sfp_parse_support()
291 __set_bit(PHY_INTERFACE_MODE_5GBASER, interfaces); in sfp_parse_support()
[all …]
A Dmarvell10g.c155 int (*select_mactype)(unsigned long *interfaces);
490 DECLARE_PHY_INTERFACE_MASK(interfaces); in mv3310_sfp_insert()
652 if (test_bit(PHY_INTERFACE_MODE_USXGMII, interfaces)) in mv2110_select_mactype()
655 !test_bit(PHY_INTERFACE_MODE_10GBASER, interfaces)) in mv2110_select_mactype()
691 if (test_bit(PHY_INTERFACE_MODE_USXGMII, interfaces)) in mv3310_select_mactype()
694 test_bit(PHY_INTERFACE_MODE_10GBASER, interfaces)) in mv3310_select_mactype()
697 test_bit(PHY_INTERFACE_MODE_RXAUI, interfaces)) in mv3310_select_mactype()
700 test_bit(PHY_INTERFACE_MODE_XAUI, interfaces)) in mv3310_select_mactype()
704 else if (test_bit(PHY_INTERFACE_MODE_RXAUI, interfaces)) in mv3310_select_mactype()
706 else if (test_bit(PHY_INTERFACE_MODE_XAUI, interfaces)) in mv3310_select_mactype()
[all …]
/linux/Documentation/driver-api/
A Dfirewire.rst8 The Linux FireWire subsystem adds some interfaces into the Linux system to
11 The main purpose of these interfaces is to access address space on each node
15 Two types of interfaces are added, according to consumers of the interface. A
16 set of userspace interfaces is available via `firewire character devices`. A set
17 of kernel interfaces is available via exported symbols in `firewire-core` module.
28 Firewire device probing and sysfs interfaces
37 Firewire core transaction interfaces
43 Firewire Isochronous I/O interfaces
A Dtarget.rst10 Target core device interfaces
16 Target core transport interfaces
44 iSCSI TCP interfaces
/linux/Documentation/ABI/
A DREADME2 userspace, and the relative stability of these interfaces. Due to the
4 interfaces should be used by userspace programs in different ways.
13 This directory documents the interfaces that the developer has
15 interfaces with no restrictions, and backward compatibility for
16 them will be guaranteed for at least 2 years. Most interfaces
21 This directory documents interfaces that are felt to be stable,
27 aware of changes that can occur before these interfaces move to
28 be marked stable. Programs that use these interfaces are
30 these interfaces, so that the kernel developers can easily
52 it changes. This is very important for interfaces in
[all …]
/linux/Documentation/networking/
A Dipv6.rst37 No IPv6 addresses will be added to interfaces, and
45 on all interfaces. This might be used when one does not wish
52 IPv6 address autoconfiguration is disabled on all interfaces.
55 will be added to interfaces.
58 IPv6 address autoconfiguration is enabled on all interfaces.
64 Specifies whether to disable IPv6 on all interfaces.
70 IPv6 is enabled on all interfaces.
75 IPv6 is disabled on all interfaces.
77 No IPv6 addresses will be added to interfaces.
A D6lowpan.rst4 Netdev private dataroom for 6lowpan interfaces
7 All 6lowpan able net devices, means all interfaces with ARPHRD_6LOWPAN,
53 by ARPHRD_6LOWPAN interfaces.
A Dproc_net_tcp.rst7 This document describes the interfaces /proc/net/tcp and /proc/net/tcp6.
8 Note that these interfaces are deprecated in favor of tcp_diag.
10 These /proc interfaces provide information about currently active TCP
/linux/Documentation/scsi/
A Dbnx2fc.rst7 cooperates with all interfaces provided by the Linux ecosystem for FC/FCoE and
13 depend on the state of the network interfaces to operate. As such, the network
15 It is recommended that the network interfaces be configured to be brought up
18 Furthermore, the Broadcom FCoE offload solution creates VLAN interfaces to
20 eth0.1001-fcoe). Do not delete or disable these interfaces or FCoE operation
28 2. Configure the interfaces on which bnx2fc driver has to operate on.
33 c. Repeat this for all the interfaces where FCoE has to be enabled.
41 the system, bnx2fc driver would automatically claim the interfaces, starts vlan
69 <INTERFACE>.<VLAN>-fcoe interfaces are automatically created.
72 create/destroy interfaces or to display lun/target information.
/linux/Documentation/admin-guide/
A Dabi-testing.rst4 Documents interfaces that are felt to be stable,
11 Userspace programs can start to rely on these interfaces, but they must
12 be aware of changes that can occur before these interfaces move to
15 Programs that use these interfaces are strongly encouraged to add their
16 name to the description of these interfaces, so that the kernel
A Dabi-stable.rst4 Documents the interfaces that the developer has defined to be stable.
6 Userspace programs are free to use these interfaces with no
10 Most interfaces (like syscalls) are expected to never change and always
/linux/drivers/greybus/
A Dmodule.c30 intf = module->interfaces[i]; in eject_store()
96 module = kzalloc(struct_size(module, interfaces, num_interfaces), in gb_module_create()
122 module->interfaces[i] = intf; in gb_module_create()
129 gb_interface_put(module->interfaces[i]); in gb_module_create()
210 gb_module_register_interface(module->interfaces[i]); in gb_module_add()
221 gb_module_deregister_interface(module->interfaces[i]); in gb_module_del()
233 gb_interface_put(module->interfaces[i]); in gb_module_put()
/linux/Documentation/devicetree/bindings/phy/
A Dmicrochip,lan966x-serdes.yaml13 Lan966x has 7 interfaces, consisting of 2 copper transceivers(CU),
14 3 SERDES6G and 2 RGMII interfaces. Two of the SERDES6G support QSGMII.
16 interfaces. The Serdes controller will allow to configure these interfaces
17 and allows to "mux" the interfaces to different ports.
/linux/drivers/i2c/algos/
A DKconfig10 tristate "I2C bit-banging interfaces"
13 tristate "I2C PCF 8584 interfaces"
16 tristate "I2C PCA 9564 interfaces"
/linux/Documentation/devicetree/bindings/media/i2c/
A Dmipi-ccs.yaml24 Documentation/devicetree/bindings/media/video-interfaces.txt .
62 description: Flash LED phandles. See ../video-interfaces.txt for details.
65 description: Lens focus controller phandles. See ../video-interfaces.txt
69 description: Rotation of the sensor. See ../video-interfaces.txt for
79 $ref: /schemas/media/video-interfaces.yaml#
107 #include <dt-bindings/media/video-interfaces.h>
A Dtoshiba,et8ek8.txt6 Documentation/devicetree/bindings/media/video-interfaces.txt .
26 - flash-leds: See ../video-interfaces.txt
27 - lens-focus: See ../video-interfaces.txt
/linux/Documentation/usb/
A Dauthorization.rst12 its interfaces are immediately made available to the users. With this
98 There is a similar approach to allow or deny specific USB interfaces.
109 The default value for new interfaces
112 Allow interfaces per default::
116 Deny interfaces per default::
121 So all interfaces would authorized per default.
127 For drivers that need multiple interfaces all needed interfaces should be
/linux/Documentation/process/
A Dstable-api-nonsense.rst15 Please realize that this article describes the **in kernel** interfaces, not
16 the kernel to userspace interfaces.
41 to worry about the in-kernel interfaces changing. For the majority of
53 So, there are two main topics here, binary kernel interfaces and stable
54 kernel source interfaces. They both depend on each other, but we will
117 As a specific examples of this, the in-kernel USB interfaces have
132 which have had to maintain their older USB interfaces over time. This
148 number of times this has caused internal kernel interfaces to be
150 happens, all drivers that use the interfaces were also fixed at the
158 as small as possible, and that all potential interfaces are tested as
[all …]
/linux/drivers/net/dsa/
A Dmv88e6060.c253 unsigned long *interfaces = config->supported_interfaces; in mv88e6060_phylink_get_caps() local
279 __set_bit(PHY_INTERFACE_MODE_MII, interfaces); in mv88e6060_phylink_get_caps()
280 __set_bit(PHY_INTERFACE_MODE_REVMII, interfaces); in mv88e6060_phylink_get_caps()
281 __set_bit(PHY_INTERFACE_MODE_REVRMII, interfaces); in mv88e6060_phylink_get_caps()
288 __set_bit(PHY_INTERFACE_MODE_INTERNAL, interfaces); in mv88e6060_phylink_get_caps()
290 __set_bit(PHY_INTERFACE_MODE_GMII, interfaces); in mv88e6060_phylink_get_caps()
/linux/drivers/net/can/usb/
A DKconfig2 menu "CAN USB interfaces"
18 tristate "esd electronics gmbh CAN/USB interfaces"
20 This driver adds support for several CAN/USB interfaces
32 tristate "ETAS ES58X CAN/USB interfaces"
36 This driver supports the ES581.4, ES582.1 and ES584.1 interfaces
55 tristate "Geschwister Schneider UG and candleLight compatible interfaces"
61 interfaces.
137 tristate "PEAK PCAN-USB/USB Pro interfaces for CAN 2.0b/CAN-FD"
/linux/Documentation/
A Dsubsystem-apis.rst27 Human interfaces
40 Networking interfaces
52 Storage interfaces
/linux/Documentation/networking/dsa/
A Dbcm_sf2.rst13 ports, offering a range of built-in and customizable interfaces:
19 - several external MII/RevMII/GMII/RGMII interfaces
23 band back-pressure to the host CPU network interface when downstream interfaces
30 - ``SWITCH_REG``: external interfaces switch register
79 Multimedia over CoAxial (MoCA) interfaces
82 MoCA interfaces are fairly specific and require the use of a firmware blob which
89 The MoCA interfaces are supported using the PHY library's fixed PHY/emulated PHY
/linux/Documentation/gpu/imagination/
A Duapi.rst75 :doc: PowerVR IOCTL CREATE_VM_CONTEXT and DESTROY_VM_CONTEXT interfaces
84 :doc: PowerVR IOCTL VM_MAP and VM_UNMAP interfaces
93 :doc: PowerVR IOCTL CREATE_CONTEXT and DESTROY_CONTEXT interfaces
112 :doc: PowerVR IOCTL CREATE_FREE_LIST and DESTROY_FREE_LIST interfaces
123 :doc: PowerVR IOCTL CREATE_HWRT_DATASET and DESTROY_HWRT_DATASET interfaces
/linux/tools/testing/selftests/devices/probe/boards/
A Dgoogle,spherion.yaml37 # For USB leaf devices, the 'interfaces' key should contain a list of the
38 # interfaces in that device that should be bound to a driver.
45 interfaces: [0, 1]
48 interfaces: [0, 1]
/linux/net/mac802154/
A Dutil.c33 list_for_each_entry_rcu(sdata, &local->interfaces, list) { in ieee802154_wake_queue()
58 list_for_each_entry_rcu(sdata, &local->interfaces, list) { in ieee802154_stop_queue()
92 list_for_each_entry_rcu(sdata, &local->interfaces, list) { in ieee802154_disable_queue()

Completed in 32 milliseconds

12345678910>>...36