| /linux/drivers/extcon/ |
| 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" : "detached"); in max8997_muic_set_path()
238 * @group: the path according to attached cable
239 * @attached: store cable state and return
[all …]
|
| H A D | extcon-max77693.c | 248 * max77693_muic_set_path - Set hardware line according to attached cable
250 * @value: the path according to attached cable
251 * @attached: the state of cable (true:attached, false:detached)
255 * attached cable.
258 u8 val, bool attached) in max77693_muic_set_path() argument
263 if (attached) in max77693_muic_set_path()
275 if (attached) in max77693_muic_set_path()
291 ctrl1, ctrl2, attached ? "attached" : "detached"); in max77693_muic_set_path()
299 * @group: the path according to attached cable
300 * @attached: store cable state and return
[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" : "detached"); in max14577_muic_set_path()
246 * @group: the path according to attached cable
247 * @attached: store cable state and return
[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 to
[all …]
|
| H A D | sysfs-bus-i2c-devices-fsa9480 | 5 show what device is attached
9 USB USB device is attached
10 UART UART is attached
11 CHARGER Charger is attached
12 JIG JIG is attached
|
| 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/tools/perf/pmu-events/arch/x86/skylakex/ |
| H A D | uncore-io.json | 13 … device plugged into the first slot of a PCIe riser card or to a device attached to the IIO unit w…
29 … device plugged into the first slot of a PCIe riser card or to a device attached to the IIO unit w…
205 …mber of double word (4 bytes) requests initiated by the main die to the attached device.; x16 card…
218 …mber of double word (4 bytes) requests initiated by the main die to the attached device.; x4 card …
231 …mber of double word (4 bytes) requests initiated by the main die to the attached device.; x8 card …
244 …mber of double word (4 bytes) requests initiated by the main die to the attached device.; x4 card …
257 …mber of double word (4 bytes) requests initiated by the main die to the attached device.; VTd - Ty…
270 …mber of double word (4 bytes) requests initiated by the main die to the attached device.; VTd - Ty…
283 …mber of double word (4 bytes) requests initiated by the main die to the attached device.; x16 card…
296 …mber of double word (4 bytes) requests initiated by the main die to the attached device.; x4 card …
[all …]
|
| /linux/tools/perf/pmu-events/arch/x86/cascadelakex/ |
| H A D | uncore-io.json | 13 … device plugged into the first slot of a PCIe riser card or to a device attached to the IIO unit w…
29 … device plugged into the first slot of a PCIe riser card or to a device attached to the IIO unit w…
205 …mber of double word (4 bytes) requests initiated by the main die to the attached device.; x16 card…
218 …mber of double word (4 bytes) requests initiated by the main die to the attached device.; x4 card …
231 …mber of double word (4 bytes) requests initiated by the main die to the attached device.; x8 card …
244 …mber of double word (4 bytes) requests initiated by the main die to the attached device.; x4 card …
257 …mber of double word (4 bytes) requests initiated by the main die to the attached device.; VTd - Ty…
270 …mber of double word (4 bytes) requests initiated by the main die to the attached device.; VTd - Ty…
283 …mber of double word (4 bytes) requests initiated by the main die to the attached device.; x16 card…
296 …mber of double word (4 bytes) requests initiated by the main die to the attached device.; x4 card …
[all …]
|
| /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/kernel/bpf/ |
| H A D | net_namespace.c | 9 * Functions to manage BPF programs attached to netns
23 struct list_head node; /* node in list of links attached to net */
301 struct bpf_prog *attached; in netns_bpf_prog_attach() local
332 attached = net->bpf.progs[type]; in netns_bpf_prog_attach()
333 if (attached == prog) { in netns_bpf_prog_attach()
334 /* The same program cannot be attached twice */ in netns_bpf_prog_attach()
354 if (attached) in netns_bpf_prog_attach()
355 bpf_prog_put(attached); in netns_bpf_prog_attach()
368 struct bpf_prog *attached; in __netns_bpf_prog_detach() local
370 /* Progs attached via links cannot be detached */ in __netns_bpf_prog_detach()
[all …]
|
| /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/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/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/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/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/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->device_info & in mptsas_is_end_device()
[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
144 in Figure 2 is attached to the live tree described in Figure 1::
155 Figure 2: Example test data tree to be attached to live tree.
158 required to attach the root('/') node. All other nodes are attached by calling
161 In the function of_attach_node(), the new node is attached as the child of the
164 data node is attached to the live tree above (Figure 1), the final structure is
205 test-child0 the test-sibling1 is attached that pushes the child node
210 already present in the live tree), then the node isn't attached rather its
219 order to remove the device nodes attached initially (first the leaf nodes are
|
| /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> [<ar…
25 if grep -q '<attached-group>\.<attached-event>.*\[if <filter>\]' README; then
|
| /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/tools/perf/pmu-events/arch/x86/icelakex/ |
| H A D | other.json | 113 … fetches and L1 instruction cache prefetches that were supplied by DRAM attached to this socket, u…
153 …"BriefDescription": "Counts demand data reads that were supplied by DRAM attached to this socket, …
163 …"BriefDescription": "Counts demand data reads that were supplied by PMM attached to this socket, u…
183 …"BriefDescription": "Counts demand data reads that were supplied by DRAM attached to another socke…
193 …"BriefDescription": "Counts demand data reads that were supplied by PMM attached to another socket…
243 …efetches for exclusive ownership (PREFETCHW) that were supplied by DRAM attached to this socket, u…
253 …refetches for exclusive ownership (PREFETCHW) that were supplied by PMM attached to this socket, u…
273 …refetches for exclusive ownership (PREFETCHW) that were supplied by PMM attached to another socket…
313 …s and software prefetches (except PREFETCHW) that were supplied by DRAM attached to this socket, u…
393 …and prefetches to the core caches (L1 or L2) that were supplied by DRAM attached to this socket, u…
[all …]
|
| /linux/tools/perf/pmu-events/arch/x86/sapphirerapids/ |
| H A D | other.json | 39 … fetches and L1 instruction cache prefetches that were supplied by DRAM attached to this socket, u…
79 …"BriefDescription": "Counts demand data reads that were supplied by DRAM attached to this socket, …
89 …"BriefDescription": "Counts demand data reads that were supplied by PMM attached to this socket, w…
109 …"BriefDescription": "Counts demand data reads that were supplied by DRAM attached to another socke…
119 …"BriefDescription": "Counts demand data reads that were supplied by PMM attached to another socket…
159 …efetches for exclusive ownership (PREFETCHW) that were supplied by DRAM attached to this socket, u…
249 …and prefetches to the core caches (L1 or L2) that were supplied by DRAM attached to this socket, u…
259 …and prefetches to the core caches (L1 or L2) that were supplied by DRAM attached to this socket, w…
269 … and prefetches to the core caches (L1 or L2) that were supplied by PMM attached to this socket, w…
289 …and prefetches to the core caches (L1 or L2) that were supplied by DRAM attached to another socket…
[all …]
|
| /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 to any unit. In this state it can
286 on whether it is unattached, attached to a PPP interface, or attached
[all …]
|
| /linux/drivers/infiniband/sw/rxe/ |
| H A D | rxe_mcast.c | 12 * attached to a new mgid for the first time. These are indexed by
15 * qp is attached to the same mgid. It is cleaned up when the last qp
16 * is detached from the mcg. Each time a qp is attached to an mcg an
18 * of qp's that are attached to the mcg. The qp_list is used to replicate
254 * no qp's are attached to mcg
271 * Context: no qp's are attached to mcg
324 * rxe_attach_mcg - attach qp to mcg if not already attached
353 /* re-check to see if someone else just attached qp */ in rxe_attach_mcg()
394 * Returns: 0 on success else an error if qp is not attached.
406 /* if the number of qp's attached to the in rxe_detach_mcg()
|