Searched refs:them (Results 1 – 25 of 1065) sorted by relevance
12345678910>>...43
| /Linux-v5.4/drivers/pinctrl/intel/ |
| D | Kconfig | 32 allows configuring of SoC pins and using them as GPIOs.
42 interface that allows configuring of SoC pins and using them as
59 configuring of SoC pins and using them as GPIOs.
67 of Intel Cannon Lake PCH pins and using them as GPIOs.
75 of Intel Cedar Fork PCH pins and using them as GPIOs.
83 of Intel Denverton SoC pins and using them as GPIOs.
91 of Intel Gemini Lake SoC pins and using them as GPIOs.
99 of Intel Ice Lake PCH pins and using them as GPIOs.
107 of Intel Lewisburg pins and using them as GPIOs.
116 using them as GPIOs.
|
| /Linux-v5.4/drivers/staging/media/ |
| D | Kconfig | 8 Most of them don't follow properly the V4L, DVB and/or RC API's,
13 If you wish to work on these drivers, to help improve them, or
14 to report problems you have with them, please use the
22 # Please keep them in alphabetic order
|
| /Linux-v5.4/Documentation/vm/ |
| D | swap_numa.rst | 19 to be swapped on. Simply swapping them on by doing::
26 that the order of them being swapped on doesn't matter.
31 The way to swap them on is the same as above::
40 Then node 0 will use them in the order of::
46 node 1 will use them in the order of::
50 node 2 will use them in the order of::
57 node 3 will use them in the order of::
|
| /Linux-v5.4/Documentation/hwmon/ |
| D | vexpress.rst | 28 from a wide range of boards, each of them containing (apart of the main
33 temperature and power usage. Some of them also calculate consumed energy
40 Tree passed to the kernel. Details of the DT binding for them can be found
|
| D | userspace-tools.rst | 19 setup monitoring limits etc. You can get them on their homepage
32 3) load them and run "sensors" command, you should see some results.
|
| /Linux-v5.4/Documentation/i2c/ |
| D | ten-bit-addresses.rst | 8 address 0x10 (though a single device could respond to both of them).
21 hardware doesn't support them (SMBus doesn't require 10-bit address
33 needs them to be fixed.
|
| /Linux-v5.4/Documentation/x86/ |
| D | microcode.rst | 89 somewhere else and/or you've downloaded them directly from the processor
111 packages already put them there.
137 so that the build system can find those files and integrate them into
138 the final kernel image. The early loader finds them and applies them.
|
| D | intel_mpx.rst | 112 them somewhere. It has two special instructions for this which allow
124 the instructions for moving bounds in and out of them are extremely
131 are a few ways this could be done. We don't think any of them are practical
135 never have to allocate them?
139 even if we clean them up aggressively. In the worst-case scenario, the
143 If we were to preallocate them for the 128TB of user virtual address
167 bounds tables that we could think of, we create them on demand in
207 knowledge, it is also responsible for freeing them when the associated
241 directory at them through XSAVE instruction, and then set valid bit
246 them at the same bounds table.
|
| /Linux-v5.4/arch/arc/plat-eznps/ |
| D | Kconfig | 33 any of them seem like CPU from Linux point of view.
35 core and HW scheduler round robin between them.
57 of the core, so there will be a need to initialize them per cpu.
|
| /Linux-v5.4/Documentation/driver-api/ |
| D | isa.rst | 22 to the driver creating them because it might want to drive them, meaning
54 them in at all. The id is the only thing we ever want other then the
60 of the old .probe in .match, which would only keep them registered after
78 loops over the passed in ndev creating devices and registering them.
79 This causes the bus match method to be called for them, which is::
|
| /Linux-v5.4/Documentation/devicetree/bindings/mmc/ |
| D | brcm,sdhci-brcmstb.txt | 7 on Device Tree properties to enable them for SoC/Board combinations
8 that support them.
|
| /Linux-v5.4/drivers/media/usb/ttusb-dec/ |
| D | Kconfig | 19 download/extract them, and then copy them to /usr/lib/hotplug/firmware
|
| /Linux-v5.4/tools/testing/selftests/tc-testing/plugin-lib/ |
| D | README-PLUGINS | 14 tdc.py will find them and use them.
|
| /Linux-v5.4/Documentation/ABI/stable/ |
| D | sysfs-firmware-opal-elog | 18 but not explicitly acknowledged them to firmware and
24 entries, read them out and acknowledge them.
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-firmware-efi-runtime-map | 12 can reassemble them and pass them into the kexec kernel.
|
| /Linux-v5.4/Documentation/input/ |
| D | gamepad.rst | 45 differently labeled on most devices so we define them as NORTH,
57 Analog-sticks may also provide a digital button if you press them.
60 Not all devices provide them, but the upper buttons are normally named
74 Legacy drivers often don't comply to these rules. As we cannot change them
76 user-space yourself. Some of them might also provide module-options that
85 and one analog stick. It reports them as if it were a gamepad with only one
|
| /Linux-v5.4/tools/power/pm-graph/ |
| D | README | 333 It is possible to add new function calls to the timeline by adding them to
335 the config so that you can override and edit them. Place them in the
340 custom calls, or leave it false to append them to the internal ones.
350 them.
407 It is possible to add new function calls to the dev timeline by adding them
409 functions into the config so that you can override and edit them. Place them
414 custom calls, or leave it false to append them to the internal ones.
425 them.
439 perform a quick check to see if you formatted them correctly and if the system
440 actually supports them. To do this, run the tool with your config file
[all …]
|
| /Linux-v5.4/Documentation/core-api/ |
| D | boot-time-mm.rst | 34 macros. Some of them are actually internal, but since they are
35 documented it would be silly to omit them. Besides, reading the
|
| /Linux-v5.4/drivers/memstick/core/ |
| D | Kconfig | 13 normal behaviour is to remove them at suspend and
14 redetecting them at resume. Breaking this assumption will
|
| /Linux-v5.4/drivers/staging/ |
| D | Kconfig | 8 them. Please note that these drivers are under heavy
17 If you wish to work on these drivers, to help improve them, or
18 to report problems you have with them, please see the
|
| /Linux-v5.4/Documentation/driver-api/acpi/ |
| D | scan_handlers.rst | 28 information from the device objects represented by them and populating them with
29 appropriate data, but some of them require additional handling after they have
56 to match a scan handler against each of them using the ids arrays of the
|
| /Linux-v5.4/Documentation/parisc/ |
| D | registers.rst | 113 r1,r2,r19-r26,r28,r29 & r31 can be used without saving them first. And of
114 course, you need to save them if you care about them, before calling
136 these are arg3-arg0, i.e. you can use them if you
|
| /Linux-v5.4/Documentation/admin-guide/pm/ |
| D | cpuidle.rst | 23 Since part of the processor hardware is not used in idle states, entering them
39 (program) from memory and executing them, but it need not work this way
49 work physically in parallel with each other, so if each of them executes only
63 instructions from multiple locations in memory and execute them in the same time
70 by one of them, the hardware thread (or CPU) that asked for it is stopped, but
81 *idle* by the Linux kernel when there are no tasks to run on them except for the
99 to allow them to make some progress over time.]
163 and ``ladder``. Which of them is used by default depends on the configuration
181 decision on which one of them to use has to be made early (on Intel platforms
196 allow them to make reasonable progress in a given time frame is to make them
[all …]
|
| /Linux-v5.4/tools/perf/Documentation/ |
| D | db-export.txt | 31 before using them. e.g. function IsSelectable() in exported-sql-viewer.py
39 before calling them. The scripting engine can also test for the support of new
|
| /Linux-v5.4/Documentation/block/ |
| D | null_blk.rst | 12 It does not execute any read/write operation, just mark them as complete in
23 - Directly accepts bio data structure and returns them.
25 All of them have a completion queue for each core in the system.
|
12345678910>>...43
