Home
last modified time | relevance | path

Searched refs:going (Results 1 – 25 of 266) sorted by relevance

1234567891011

/Linux-v5.10/drivers/usb/host/
Du132-hcd.c185 int going; member
253 u132->going += 1; in u132_hcd_delete()
258 "2=%p going=%d pdev=%p\n", hcd, u132, u132->going, pdev); in u132_hcd_delete()
474 if (u132->going > 1) { in u132_hcd_monitor_work()
476 , u132->going); in u132_hcd_monitor_work()
479 } else if (u132->going > 0) { in u132_hcd_monitor_work()
490 u132->going = 1; in u132_hcd_monitor_work()
624 if (u132->going > 1) { in u132_hcd_interrupt_recv()
626 , u132->going); in u132_hcd_interrupt_recv()
635 } else if (u132->going > 0) { in u132_hcd_interrupt_recv()
[all …]
/Linux-v5.10/tools/perf/arch/x86/tests/
Dgen-insn-x86-dat.awk16 going = 0
20 going = 1
24 going = 0
28 if (going) {
/Linux-v5.10/arch/arm/boot/dts/
Dxenvm-4.2.dts20 /* this field is going to be adjusted by the hypervisor */
50 /* this field is going to be adjusted by the hypervisor */
73 /* this field is going to be adjusted by the hypervisor */
75 /* this field is going to be adjusted by the hypervisor */
Drk3288-veyron-analog-audio.dtsi81 * HACK: We're going to _pull down_ this _active low_ interrupt
/Linux-v5.10/Documentation/ABI/obsolete/
Dsysfs-class-net-mesh15 Indicates whether the data traffic going from a
24 Indicates whether the data traffic going through the
41 Indicates whether the data traffic going through the
87 mesh are going to use classic flooding for any
/Linux-v5.10/Documentation/driver-api/
Dhsi.rst18 commonly prefixed by AC for signals going from the application die to the
19 cellular die and CA for signals going the other way around.
/Linux-v5.10/Documentation/devicetree/bindings/timer/
Dsnps,arc-timer.txt11 - interrupts : single Interrupt going into parent intc
/Linux-v5.10/Documentation/devicetree/bindings/security/tpm/
Dst33zp24-spi.txt10 If set, power must be present when the platform is going into sleep/hibernate mode.
Dst33zp24-i2c.txt11 If set, power must be present when the platform is going into sleep/hibernate mode.
/Linux-v5.10/Documentation/driver-api/pm/
Dnotifiers.rst30 The system is going to hibernate, tasks will be frozen immediately. This
41 The system is going to restore a hibernation image. If all goes well,
/Linux-v5.10/Documentation/devicetree/bindings/rtc/
Drtc-meson-vrtc.txt14 program an always-on timer before going sleep. When the timer expires,
/Linux-v5.10/drivers/i2c/
DKconfig143 problem with I2C support and want to see more of what is going on.
150 a problem with I2C support and want to see more of what is going
159 a problem with I2C support and want to see more of what is going
/Linux-v5.10/arch/arm/mach-prima2/
Dsleep.S46 @ the RAM is going to self refresh mode
/Linux-v5.10/tools/testing/selftests/drivers/net/mlxsw/
Dqos_lib.sh67 same time, one of them is arbitrarily going to overwrite
/Linux-v5.10/Documentation/vm/
Dswap_numa.rst18 swapB, with swapA attached to node 0 and swapB attached to node 1, are going
28 A more complex example on a 4 node machine. Assume 6 swap devices are going to
Dremap_file_pages.rst28 emulation creates new VMAs instead of nonlinear mappings. It's going to
/Linux-v5.10/Documentation/gpu/
Dmeson.rst12 that are going to be documented below:
/Linux-v5.10/Documentation/devicetree/bindings/hwmon/
Dgpio-fan.txt12 - alarm-gpios: This pin going active indicates something is wrong with
/Linux-v5.10/Documentation/networking/
Dieee802154.rst103 This layer is going to be extended soon.
143 Telling 802.15.4 module the frame in the skb is or going to be
170 Handler that 802.15.4 module calls for each frame in the skb going to be
Dip_dynaddr.rst21 going up. So, the *same* (local AND masqueraded) connections requests that
/Linux-v5.10/Documentation/i2c/
Dgpio-fault-injection.rst99 Arbitration lost is achieved by waiting for SCL going down by the master under
104 should be detected beforehand. Also note, that SCL going down is monitored
129 Start of a transfer is detected by waiting for SCL going down by the master
/Linux-v5.10/drivers/pps/
DKconfig30 problem with PPS support and want to see more of what is going on.
/Linux-v5.10/tools/lib/traceevent/Documentation/
Dlibtraceevent-reg_event_handler.txt29 which is going to be called to parse the information for a given event.
34 _event_name_ are used. The _func_ is a pointer to the function, which is going
/Linux-v5.10/Documentation/fb/
Dcirrusfb.rst8 .. just a little something to get people going; contributors welcome!
/Linux-v5.10/Documentation/process/
D6.Followthrough.rst64 explain what is really going on. If you have a technical objection to a
84 going to remember all the details of the code you posted the last time
92 What if you've tried to do everything right and things still aren't going
95 honestly believe that this decision is going against you wrongly, you can
117 being -mm. Patches which affect multiple subsystems can also end up going

1234567891011