| /linux-6.15/block/partitions/ |
| H A D | Kconfig | 10 Say Y here if you would like to use hard disks under Linux which
31 Say Y here if you would like to use hard disks under Linux which
44 Say Y here if you would like to use hard disks under Linux which
77 Say Y here if you would like to be able to read the hard disk
89 Say Y here if you would like to use hard disks under Linux which
110 Say Y here if you would like to be able to read the hard disk
170 Linux box via a removable medium like magneto-optical, ZIP or
217 Say Y here if you would like to be able to read the hard disk
224 Say Y here if you would like to be able to read the hard disk
262 Say Y here if you would like to be able to read the hard disk
[all …]
|
| /linux-6.15/tools/memory-model/Documentation/ |
| H A D | README | 8 depending on what you know and what you would like to learn. Please note
17 like an overview of the types of low-level concurrency primitives
26 o You would like to access lock-protected shared variables without
30 like a detailed intuitive understanding of LKMM, including
33 o You would like a detailed understanding of what your compiler can
36 o You would like to mark concurrent normal accesses to shared
42 LKMM, and would like a quick reference: cheatsheet.txt
45 of LKMM, and would like to learn about LKMM's requirements,
|
| /linux-6.15/Documentation/core-api/ |
| H A D | entry.rst | 16 exceptions`_, `NMI and NMI-like exceptions`_.
64 invoked from low-level assembly code looks like this:
88 and then invokes the various entry work functions like ptrace, seccomp, audit,
94 returning to user space like tracing, audit, signals, task work etc. After
197 NMI and NMI-like exceptions
200 NMIs and NMI-like exceptions (machine checks, double faults, debug
206 in kernel mode (code patching). From user-space, they are treated like
207 interrupts, while from kernel mode they are treated like NMIs.
209 NMIs and other NMI-like exceptions handle state transitions without
229 Architecture-specific code looks like this:
[all …]
|
| H A D | asm-annotations.rst | 12 Some code like entries, trampolines, or boot code needs to be written in
21 Over time, the Linux kernel has adopted macros from various projects (like
42 annotated objects like this, tools can be run on them to generate more useful
76 1. ``SYM_FUNC_*`` -- to annotate C-like functions. This means functions with
83 Checking tools like ``objtool`` should ensure such marked functions conform
85 debugging information (like *ORC data*) automatically.
93 this code needs hints like ``UNWIND_HINT_REGS`` provided by developers.
124 So in most cases, developers should write something like in the following
|
| /linux-6.15/Documentation/trace/coresight/ |
| H A D | coresight-perf.rst | 13 can log such data with a perf record command like::
20 readable text with a command like::
24 You should find some sections of this file have AUX data blocks like::
68 enabled like::
87 kernel tree. Some tests will check some internal perf support like:
95 tests are in the same directory. These will all look like:
109 directory (e.g. tools/perf) and will be named stats-\*.csv like:
138 test like::
144 directory for later inspection like::
|
| /linux-6.15/Documentation/userspace-api/media/v4l/ |
| H A D | libv4l-introduction.rst | 72 applications work with v4l2 devices. These functions work exactly like
113 Those functions operate just like the gcc function ``dup()`` and
121 operates like the :c:func:`open()` function.
125 operates like the :c:func:`close()` function.
129 operates like the libc ``dup()`` function, duplicating a file handler.
133 operates like the :c:func:`ioctl()` function.
137 operates like the :c:func:`read()` function.
141 operates like the :c:func:`mmap()` function.
145 operates like the :c:func:`munmap()` function.
|
| /linux-6.15/Documentation/devicetree/bindings/i2c/ |
| H A D | google,cros-ec-i2c-tunnel.yaml | 17 other side of the EC (like a battery and PMIC). To get access to
20 The node for this device should be under a cros-ec node like
31 description: The EC bus we'd like to talk to.
|
| /linux-6.15/drivers/platform/arm64/ |
| H A D | Kconfig | 3 # EC-like Drivers for aarch64 based devices.
12 for arm64 based devices, primarily EC-like device drivers.
29 monitoring as well as some misc functions like the lid sensor
48 as some misc functions like the lid sensor and temperature sensors,
|
| /linux-6.15/Documentation/i2c/busses/ |
| H A D | i2c-sis630.rst | 38 If you see something like this::
43 or like this::
48 or like this::
|
| /linux-6.15/Documentation/ABI/stable/ |
| H A D | sysfs-devices-system-cpu | 64 The format is like 0-3, 8-11, 14,17.
75 The format is like 0-3, 8-11, 14,17.
85 The format is like 0-3, 8-11, 14,17.
94 The format is like 0-3, 8-11, 14,17.
105 The format is like 0-3, 8-11, 14,17. it's only used on s390.
116 The format is like 0-3, 8-11, 14,17. it's only used on s390.
|
| /linux-6.15/arch/arm/mach-mstar/ |
| H A D | Kconfig | 12 based on Armv7 cores like the Cortex A7 and share the same
13 basic hardware like the infinity and mercury series.
|
| /linux-6.15/Documentation/admin-guide/laptops/ |
| H A D | asus-laptop.rst | 15 events (like keyboards).
53 see some lines like this :
65 Hotkeys are also reported as input keys (like keyboards) you can check
82 kernel triggers like disk-activity or heartbeat.
179 like::
183 will usually do the trick ($arg is the 0000006n-like event passed to acpid).
191 Some models like the W1N have a LED display that can be used to display
239 - 0x5 like 0x1 or 0x4
|
| /linux-6.15/arch/arm64/boot/dts/rockchip/ |
| H A D | rk3588-turing-rk1.dts | 4 * "compute node" system, where the carrier board is functioning more like a
6 * like a device that the SoM is meant to enable.
|
| /linux-6.15/Documentation/arch/powerpc/ |
| H A D | vmemmap_dedup.rst | 22 Here's how things look like on device-dax after the sections are populated::
50 Here's how things look like on device-dax after the sections are populated::
79 Here's how things look like on device-dax after the sections are populated::
|
| /linux-6.15/Documentation/fb/ |
| H A D | cmap_xfbdev.rst | 24 - X11 apps do something like the following when trying to use grayscale::
36 There's also named equivalents like gray1..x provided you have an rgb.txt.
54 that the app wants to match to. The above code is doing what looks like a least
|
| /linux-6.15/sound/oss/dmasound/ |
| H A D | Kconfig | 8 Y to this question. This will provide a Sun-like /dev/audio,
22 Y to this question. This will provide a Sun-like /dev/audio,
36 Y to this question. This will provide a Sun-like /dev/audio,
|
| /linux-6.15/Documentation/ |
| H A D | atomic_t.txt | 64 (which implies -fwrapv) and defines signed overflow to behave like
73 With this we also conform to the C/C++ _Atomic behaviour and things like
174 Except of course when a successful operation has an explicit ordering like:
184 subsequent. Therefore a fully ordered primitive is like having an smp_mb()
193 ordering inherent to the op. These barriers act almost like a full smp_mb():
220 Further, while something like:
228 as well. Similarly, something like:
283 compact code. The functions relate like:
336 which on LL/SC becomes something like:
|
| /linux-6.15/drivers/dma/bestcomm/ |
| H A D | Kconfig | 14 optional for some drivers (like ATA), but required for
15 others (like FEC).
|
| /linux-6.15/Documentation/devicetree/bindings/powerpc/opal/ |
| H A D | sensor-groups.txt | 17 operations like clearing the min/max history of all
26 sensor groups like clearing min/max, enabling/disabling sensor
|
| /linux-6.15/drivers/platform/x86/intel/int1092/ |
| H A D | Kconfig | 10 driver to obtain information like the device mode, Antenna index, baseband index,
11 SAR table index and use available communication like MBIM interface to enable
|
| /linux-6.15/Documentation/kbuild/ |
| H A D | kconfig-macro-language.rst | 14 can write a makefile like follows::
24 and handles as if the source file were input like follows::
33 file like this::
145 Kconfig adopts Make-like macro language, but the function call syntax is
148 A function call in Make looks like this::
156 to make "info" function print " hello", you can write like follows::
173 'call', like this::
241 Instead, you can do like follows so that any function call is statically
|
| /linux-6.15/drivers/net/can/c_can/ |
| H A D | Kconfig | 14 boards from ST Microelectronics (http://www.st.com) like the
16 boards like am335x, dm814x, dm813x and dm811x.
|
| /linux-6.15/Documentation/sound/designs/ |
| H A D | oss-emulation.rst | 29 ``alias sound-slot-0 snd-card-0`` doesn't work any more like the old
65 (NOTE: Some distributions have the device files like /dev/midi0 and
90 define like this:
97 device on the second card to /dev/adsp1, define like below:
125 This will lead to some problems for some applications like quake or
168 quake, send a command via echo like the following:
191 for OSS devices, define like the following:
209 and restore it like
271 file, /proc/asound/cardX/oss_mixer, which will be like the following
288 send the command like the following:
|
| /linux-6.15/Documentation/ABI/testing/ |
| H A D | sysfs-firmware-opal-sensor-groups | 8 like power, temperature, frequency, current, etc. They
10 different owners like CSM, Profiler, Job-Scheduler
|
| /linux-6.15/Documentation/doc-guide/ |
| H A D | kernel-doc.rst | 44 the comment is formatted like a normal multi-line comment with a column
234 It is possible to document nested structs and unions, like::
288 on a line of their own, like all other kernel-doc comments::
344 Object-like macro documentation
347 Object-like macros are distinct from function-like macros. They are
349 left parenthesis ('(') for function-like macros or not followed by one
350 for object-like macros.
352 Function-like macros are handled like functions by ``scripts/kernel-doc``.
353 They may have a parameter list. Object-like macros have do not have a
356 The general format of an object-like macro kernel-doc comment is::
[all …]
|