/linux/drivers/extcon/ |
H A D | extcon-max77843.c | 199 u8 val, bool attached, bool nobccomp) in max77843_muic_set_path() argument 205 if (attached) in max77843_muic_set_path() 224 if (attached) in max77843_muic_set_path() 240 ctrl1, ctrl2, attached ? "attached" : "detached"); in max77843_muic_set_path() 261 enum max77843_muic_cable_group group, bool *attached) in max77843_muic_get_cable_type() argument 272 *attached = false; in max77843_muic_get_cable_type() 276 *attached = true; in max77843_muic_get_cable_type() 292 *attached = false; in max77843_muic_get_cable_type() 301 *attached in max77843_muic_get_cable_type() 371 bool attached; max77843_muic_adc_gnd_handler() local 410 max77843_muic_jig_handler(struct max77843_muic_info * info,int cable_type,bool attached) max77843_muic_jig_handler() argument 440 max77843_muic_dock_handler(struct max77843_muic_info * info,bool attached) max77843_muic_dock_handler() argument 462 bool attached; max77843_muic_adc_handler() local 534 bool attached; max77843_muic_chg_handler() local 708 bool attached; max77843_muic_detect_cable_wq() local 815 bool attached; max77843_muic_probe() local [all...] |
H A D | extcon-max8997.c | 188 * max8997_muic_set_path - Set hardware line according to attached cable 190 * @value: the path according to attached cable 191 * @attached: the state of cable (true:attached, false:detached) 195 * attached cable. 198 u8 val, bool attached) in max8997_muic_set_path() argument 203 if (attached) in max8997_muic_set_path() 215 if (attached) in max8997_muic_set_path() 230 ctrl1, ctrl2, attached ? "attached" in max8997_muic_set_path() 247 max8997_muic_get_cable_type(struct max8997_muic_info * info,enum max8997_muic_cable_group group,bool * attached) max8997_muic_get_cable_type() argument 313 max8997_muic_handle_usb(struct max8997_muic_info * info,enum max8997_muic_usb_type usb_type,bool attached) max8997_muic_handle_usb() argument 342 max8997_muic_handle_dock(struct max8997_muic_info * info,int cable_type,bool attached) max8997_muic_handle_dock() argument 367 max8997_muic_handle_jig_uart(struct max8997_muic_info * info,bool attached) max8997_muic_handle_jig_uart() argument 386 bool attached; max8997_muic_adc_handler() local 464 bool attached; max8997_muic_chg_handler() local 581 bool attached; max8997_muic_detect_dev() local 639 bool attached; max8997_muic_probe() local [all...] |
H A D | extcon-max14577.c | 186 * max14577_muic_set_path - Set hardware line according to attached cable 188 * @value: the path according to attached cable 189 * @attached: the state of cable (true:attached, false:detached) 193 * attached cable. 196 u8 val, bool attached) in max14577_muic_set_path() argument 210 if (attached) in max14577_muic_set_path() 223 if (attached) in max14577_muic_set_path() 238 ctrl1, ctrl2, attached ? "attached" in max14577_muic_set_path() 255 max14577_muic_get_cable_type(struct max14577_muic_info * info,enum max14577_muic_cable_group group,bool * attached) max14577_muic_get_cable_type() argument 322 max14577_muic_jig_handler(struct max14577_muic_info * info,int cable_type,bool attached) max14577_muic_jig_handler() argument 359 bool attached; max14577_muic_adc_handler() local 430 bool attached; max14577_muic_chg_handler() local 608 bool attached; max14577_muic_detect_accessory() local 662 bool attached; max14577_muic_probe() local [all...] |
/linux/Documentation/ABI/testing/ |
H A D | configfs-most | 49 name of the device the link is to be attached to 52 name of the channel the link is to be attached to 61 a physical device is being attached to the bus. 104 name of the device the link is to be attached to 107 name of the channel the link is to be attached to 116 a physical device is being attached to the bus. 159 name of the device the link is to be attached to 162 name of the channel the link is to be attached to 171 a physical device is being attached to the bus. 225 name of the device the link is to be attached t [all...] |
H A D | sysfs-class-extcon | 12 attached simultaneously. Many of docks, cradles, and 15 may have both HDMI and Charger attached, or analog audio, 16 video, and USB cables attached simultaneously. 52 cables attached and HDMI and EAR_JACK cables detached. 82 (attached).
|
/linux/Documentation/admin-guide/mm/ |
H A D | swap_numa.rst | 16 swapB, with swapA attached to node 0 and swapB attached to node 1, are going 27 be swapped on: swapA and swapB are attached to node 0, swapC is attached to 28 node 1, swapD and swapE are attached to node 2 and swapF is attached to node3. 76 as the promoted value. So if multiple swap devices are attached to the same
|
/linux/drivers/iio/imu/bno055/ |
H A D | Kconfig | 9 tristate "Bosch BNO055 attached via UART" 14 Enable this to support Bosch BNO055 IMUs attached via UART. 20 tristate "Bosch BNO055 attached via I2C bus" 25 Enable this to support Bosch BNO055 IMUs attached via I2C bus.
|
/linux/kernel/bpf/ |
H A D | net_namespace.c | 9 * Functions to manage BPF programs attached to netns 21 struct list_head node; /* node in list of links attached to net */ 300 struct bpf_prog *attached; in netns_bpf_prog_attach() local 331 attached = net->bpf.progs[type]; in netns_bpf_prog_attach() 332 if (attached == prog) { in netns_bpf_prog_attach() 333 /* The same program cannot be attached twice */ in netns_bpf_prog_attach() 353 if (attached) in netns_bpf_prog_attach() 354 bpf_prog_put(attached); in netns_bpf_prog_attach() 367 struct bpf_prog *attached; in __netns_bpf_prog_detach() local 369 /* Progs attached vi in __netns_bpf_prog_detach() [all...] |
/linux/tools/usb/ffs-aio-example/multibuff/host_app/ |
H A D | test.c | 44 * @attached: indicates that device was attached to kernel, and has to be 52 int attached; member 68 state->attached = 0; in test_init() 115 state->attached = 1; in test_init() 127 if (state->attached == 1) in test_init() 148 if (state->attached == 1) in test_exit()
|
/linux/Documentation/bpf/ |
H A D | prog_sk_lookup.rst | 36 BPF sk_lookup program can be attached to a network namespace with 40 Multiple programs can be attached to one network namespace. Programs will be 41 invoked in the same order as they were attached. 46 The attached BPF sk_lookup programs run whenever the transport layer needs to 52 The attached BPF programs must return with either ``SK_PASS`` or ``SK_DROP`` 65 When multiple programs are attached, the end result is determined from return
|
H A D | map_cgroup_storage.rst | 11 storage is identified by the cgroup the program is attached to. 13 The map provide a local storage at the cgroup that the BPF program is attached 132 that uses the map. A program may be attached to multiple cgroups or have 144 attached to a cgroup, the kernel would create a new storage only if the map 148 only when either the map or the cgroup attached to is being freed. Detaching 165 The storage is bound at attach time. Even if the program is attached to parent
|
/linux/drivers/scsi/elx/libefc/ |
H A D | efc_device.c | 280 if (node->attached) { in __efc_d_initiate_shutdown() 282 * away or sometime later, will check node->attached in __efc_d_initiate_shutdown() 467 /* we're not attached and nport is p2p, in efc_d_check_plogi_topology() 474 /* we're not attached and nport is fabric, domain in efc_d_check_plogi_topology() 523 * and domain is attached in __efc_d_init() 526 node->nport->domain->attached) { in __efc_d_init() 533 node_printf(node, "domain attached=%d\n", in __efc_d_init() 534 node->nport->domain->attached); in __efc_d_init() 547 /* domain not attached; several possibilities: */ in __efc_d_init() 548 if (!node->nport->domain->attached) { in __efc_d_init() [all...] |
/linux/tools/usb/ffs-aio-example/simple/host_app/ |
H A D | test.c | 44 * @attached: indicates that device was attached to kernel, and has to be 52 int attached; member 68 state->attached = 0; in test_init() 115 state->attached = 1; in test_init() 127 if (state->attached == 1) in test_init() 148 if (state->attached == 1) in test_exit()
|
/linux/tools/testing/selftests/ftrace/test.d/dynevent/ |
H A D | eprobes_syntax_errors.tc | 4 # requires: dynamic_events events/syscalls/sys_enter_openat "<attached-group>.<attached-event> [<args>]":README error_log 25 if grep -q '<attached-group>\.<attached-event>.*\[if <filter>\]' README; then
|
H A D | add_remove_fprobe.tc | 13 # Some functions may have BPF programs attached, therefore 31 # Make sure the event is attached and is the only one 39 # It should till be the only attached function 46 # If the function is different, the attached function should be increased
|
/linux/include/linux/i3c/ |
H A D | master.h | 86 * This object is created by the core and later attached to the controller 125 * struct i3c_device_ibi_info - IBI information attached to a specific device 147 * i3c_device_request_ibi() is called and attached to a specific device. This 201 * @ibi: IBI info attached to a device. Should be NULL until 207 * @boardinfo: pointer to the boardinfo attached to this I3C device 230 * @bus: I3C bus this device is attached to 343 * devices connected on the bus and successfully attached to the 346 * devices connected on the bus and successfully attached to the 390 * @attach_i3c_dev: called every time an I3C device is attached to the bus. It 412 * attached o [all...] |
/linux/include/linux/power/ |
H A D | charger-manager.h | 46 * charger cable. If charger cable is attached, enable charger. 49 * (External Connector) when charger cable is attached/detached. 50 * @attached: the state of charger cable. 51 * true: the charger cable is attached 67 bool attached; member 73 * according to a kind of charger cable when cable is attached. 92 * in the array of charger cables is attached/detached.
|
/linux/Documentation/devicetree/ |
H A D | of_unittest.rst | 13 is attached to the live tree dynamically, independent of the machine's 142 in Figure 2 is attached to the live tree described in Figure 1:: 153 Figure 2: Example test data tree to be attached to live tree. 156 required to attach the root('/') node. All other nodes are attached by calling 159 In the function of_attach_node(), the new node is attached as the child of the 162 data node is attached to the live tree above (Figure 1), the final structure is 203 test-child0 the test-sibling1 is attached that pushes the child node 208 already present in the live tree), then the node isn't attached rather its 217 order to remove the device nodes attached initially (first the leaf nodes are
|
/linux/drivers/message/fusion/ |
H A D | mptsas.c | 170 "Attached Device Handle=0x%X\n", ioc->name, in mptsas_print_phy_pg0() 175 "Attached PHY Identifier=0x%X\n", ioc->name, in mptsas_print_phy_pg0() 177 dsasprintk(ioc, printk(MYIOC_s_DEBUG_FMT "Attached Device Info=0x%X\n", in mptsas_print_phy_pg0() 255 "Attached Device Handle=0x%X\n\n", ioc->name, in mptsas_print_expander_pg1() 460 mptsas_is_end_device(struct mptsas_devinfo * attached) in mptsas_is_end_device() argument 462 if ((attached->sas_address) && in mptsas_is_end_device() 463 (attached->device_info & in mptsas_is_end_device() 465 ((attached->device_info & in mptsas_is_end_device() 467 (attached->device_info & in mptsas_is_end_device() 469 (attached in mptsas_is_end_device() [all...] |
/linux/Documentation/driver-api/cxl/linux/example-configurations/ |
H A D | hb-interleave.rst | 10 * Two CXL Host Bridges have a single CXL Memory Expander Attached 46 This chunk shows the CXL "bus" (root0) has 4 downstream ports attached to CXL 47 Host Bridges. The `Root` can be considered the singular upstream port attached 114 This chunk shows the endpoints attached to the host bridge :code:`port1`. 144 target is :code:`dport1` - which is attached to :code:`endpoint5`. 147 the second host bridge with a memory device attached. 212 The next chunk shows the two CXL host bridges without attached endpoints.
|
H A D | single-device.rst | 10 * One CXL Host Bridges has a single CXL Memory Expander Attached 46 This chunk shows the CXL "bus" (root0) has 4 downstream ports attached to CXL 47 Host Bridges. The `Root` can be considered the singular upstream port attached 113 This chunk shows the endpoints attached to the host bridge :code:`port1`. 143 target is :code:`dport1` - which is attached to :code:`endpoint5`. 145 The next chunk shows the three CXL host bridges without attached endpoints.
|
H A D | intra-hb-interleave.rst | 10 * One (1) CXL Host Bridges has two CXL Memory Expanders Attached 46 This chunk shows the CXL "bus" (root0) has 4 downstream ports attached to CXL 47 Host Bridges. The `Root` can be considered the singular upstream port attached 140 This chunk shows the endpoints attached to the host bridge :code:`port1`. 178 targets: :code:`dport1` and :code:`dport3` - which are attached to 183 The next chunk shows the three CXL host bridges without attached endpoints.
|
H A D | multi-interleave.rst | 10 * Two CXL Host Bridges have a two CXL Memory Expanders Attached each. 47 This chunk shows the CXL "bus" (root0) has 4 downstream ports attached to CXL 48 Host Bridges. The `Root` can be considered the singular upstream port attached 141 This chunk shows the endpoints attached to the host bridge :code:`port1`. 181 targets are :code:`dport0` and :code:`dport2` - which are attached to 185 the second host bridge with a memory device attached. 288 The next chunk shows the two CXL host bridges without attached endpoints.
|
/linux/tools/bpf/bpftool/Documentation/ |
H A D | bpftool-net.rst | 45 For programs attached to a particular cgroup, e.g., 56 programs attached to the same networking device through **tc**, the order 57 will be first all bpf programs attached to tcx, netkit, then tc classes, 58 then all bpf programs attached to non clsact qdiscs, and finally all bpf 59 programs attached to root and clsact qdisc. 63 by *ATTACH_TYPE*. Previously attached bpf program can be replaced by the 76 Detach bpf program attached to network interface *NAME* with type specified
|
/linux/Documentation/networking/ |
H A D | ppp_generic.rst | 154 queue of transmit packets for each attached channel. Normally the 170 If multilink is not in use, this packet is then passed to the attached 256 /dev/ppp acts independently and can be attached either to a PPP unit 264 unattached. Using an ioctl call, it can then be attached to an 265 existing unit, attached to a newly-created unit, or attached to an 266 existing channel. An instance attached to a unit can be used to send 269 attached to a channel can be used to send and receive PPP frames on 274 write to the unit (i.e., to an instance of /dev/ppp attached to the 280 A channel is not initially attached t [all...] |