Searched full:go (Results 1 – 25 of 375) sorted by relevance
12345678910>>...15
| /Documentation/arch/loongarch/ |
| D | irq-chip-model.rst | 22 In this model, IPI (Inter-Processor Interrupt) and CPU Local Timer interrupt go
23 to CPUINTC directly, CPU UARTS interrupts go to LIOINTC, while all other devices
24 interrupts go to PCH-PIC/PCH-LPC/PCH-MSI and gathered by HTVECINTC, and then go
59 In this model, IPI (Inter-Processor Interrupt) and CPU Local Timer interrupt go
60 to CPUINTC directly, CPU UARTS interrupts go to LIOINTC, while all other devices
61 interrupts go to PCH-PIC/PCH-LPC/PCH-MSI and gathered by EIOINTC, and then go to
91 In this model, IPI (Inter-Processor Interrupt) and CPU Local Timer interrupt go
92 to CPUINTC directly, CPU UARTS interrupts go to LIOINTC, PCH-MSI interrupts go
93 to AVECINTC, and then go to CPUINTC directly, while all other devices interrupts
94 go to PCH-PIC/PCH-LPC and gathered by EIOINTC, and then go to CPUINTC directly::
|
| /Documentation/power/ |
| D | tricks.rst | 9 * go with minimal config, turn off drivers like USB, AGP you don't
14 * use ext2. At least it has working fsck. [If something seems to go
22 * try running as few processes as possible, preferably go to single
|
| /Documentation/devicetree/bindings/pwm/ |
| D | pwm-tipwmss.txt | 33 /* child nodes go here */
46 /* child nodes go here */
57 /* child nodes go here */
|
| /Documentation/w1/slaves/ |
| D | w1_ds28e17.rst | 23 come and go as the DS28E17 devices come and go. I2C slave devices connected to
42 chips may come and go on the Onewire bus without being de-powered and
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | mc-peripheral-props.yaml | 16 should go in their own separate schema that should be referenced
34 # The controller specific properties go here.
|
| /Documentation/watchdog/ |
| D | convert_drivers_to_kernel_api.rst | 20 go. Only very few driver-specific details have to be moved to other functions.
24 close preparations) can simply go. Device specific stuff needs to go to the
31 - write: Can simply go, all defined behaviour is taken care of by the framework,
85 refactoring. The rest can go.
187 can go, though. This will likely be some code in open(), close() or write().
|
| /Documentation/hwmon/ |
| D | amc6821.rst | 74 pwm1 = pwm1_auto_point2_pwm. It can go from
79 speed. It can go from temp1_auto_point2_temp.
91 pwm1 = pwm1_auto_point2_pwm. It can go from
|
| /Documentation/devicetree/bindings/leds/ |
| D | leds-trigger-pattern.txt | 19 It will make the LED go gradually from zero-intensity to max (255) intensity in
31 2. To make the LED go instantly from one brightness value to another, we should
|
| /Documentation/filesystems/ |
| D | fuse-io.rst | 35 In writeback-cache mode (enabled by the FUSE_WRITEBACK_CACHE flag) writes go to
40 assumes that all changes to the filesystem go through the FUSE kernel module
|
| /Documentation/filesystems/bcachefs/ |
| D | CodingStyle.rst | 37 Assertions are documentation that can't go out of date. Good assertions are
94 through logs. This is a lot of steps to go through when a user is hitting
160 often go astray - doing something because it seems like it'll be useful often
179 don't go overboard. A good commit message is wonderful - but if the information
180 was important enough to go in a commit message, ask yourself if it would be
|
| /Documentation/mm/ |
| D | page_cache.rst | 9 but normal reads, writes and mmaps go through the page cache.
|
| /Documentation/tools/rtla/ |
| D | common_timerlat_description.rst | 3 set a periodic timer to wake themselves up and go back to sleep. After
|
| /Documentation/ABI/testing/ |
| D | debugfs-cros-ec | 42 where a system failed to go into S0ix. When the system resumes,
64 in order to detect cases where a system failed to go into deep
|
| D | sysfs-bus-event_source-devices-format | 6 Attribute group to describe the magic bits that go into
|
| D | sysfs-bus-event_source-devices-dsa | 6 that go into perf_event_attr.config or
|
| /Documentation/maintainer/ |
| D | index.rst | 6 There is a lot yet to go here! Please feel free to propose (and write)
|
| /Documentation/admin-guide/pm/ |
| D | strategies.rst | 46 runtime idle in one go. For this reason, systems usually use less energy in
52 go into a sleep state at that point. On the other hand, if the user simply goes
|
| D | sleep-states.rst | 55 go back to where it left off easily enough.
136 which boots a fresh instance of the kernel (control may also go directly to
274 According to the above, there are two ways to make the system go into the
278 :file:`/sys/power/state`. Likewise, there are two ways to make the system go
282 system go into the :ref:`suspend-to-RAM <s2ram>` state (write "deep" into
|
| /Documentation/devicetree/bindings/ |
| D | submitting-patches.rst | 70 which ones to review and which ones are ok to let go.
74 maintainers after a few weeks, go ahead and take it.
|
| /Documentation/bpf/libbpf/ |
| D | libbpf_naming_convention.rst | 19 sys_bpf system call. These wrappers should go to ``bpf.h`` header file
52 All objects and corresponding functions other than BTF related should go
53 to ``libbpf.h``. BTF types and functions should go to ``btf.h``.
|
| /Documentation/networking/ |
| D | operstates.rst | 155 via RTM_SETLINK instructs the kernel that an interface should go to
170 - do 802.1X, eventually abort if flags go down again
182 waiting for operstate to go IF_OPER_UP/IF_OPER_UNKNOWN before
|
| /Documentation/devicetree/bindings/riscv/ |
| D | canaan.yaml | 26 - const: sipeed,maix-go
|
| /Documentation/i2c/busses/ |
| D | i2c-via.rst | 31 Go to your BIOS setup, section PCI devices or similar.
|
| /Documentation/devicetree/bindings/rng/ |
| D | microsoft,vmgenid.yaml | 17 http://go.microsoft.com/fwlink/?LinkId=260709.
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-arb-gpio-challenge.yaml | 47 6. Go back to 1 (until retry time has expired).
66 Time to wait for a GPIO to go high.
|
12345678910>>...15