Searched full:like (Results 1 – 25 of 1068) sorted by relevance
12345678910>>...43
| /Documentation/kbuild/ |
| 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::
53 Like in Make, a variable in Kconfig works as a macro variable. A macro
96 Like Make, Kconfig provides several built-in functions. Every function takes a
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
|
| /Documentation/devicetree/bindings/arc/ |
| D | archs-pct.txt | 4 CPU and cache events like cache misses and hits. Like conventional PCT there
|
| D | pct.txt | 4 CPU and cache events like cache misses and hits. Like conventional PCT there
|
| /Documentation/userspace-api/media/v4l/ |
| 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:`munmap()` function.
145 operates like the :c:func:`munmap()` function.
|
| /Documentation/ |
| 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
75 1. ``SYM_FUNC_*`` -- to annotate C-like functions. This means functions with
82 Checking tools like ``objtool`` should ensure such marked functions conform
84 debugging information (like *ORC data*) automatically.
92 this code needs hints like ``UNWIND_HINT_REGS`` provided by developers.
110 conventions -- global and local. Like in C, they both align the functions to
123 So in most cases, developers should write something like in the following
|
| 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 an 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:
|
| /Documentation/core-api/ |
| D | packing.rst | 51 1. Normally (no quirks), we would do it like this:
67 2. If QUIRK_MSB_ON_THE_RIGHT is set, we do it like this:
80 3. If QUIRK_LITTLE_ENDIAN is set, we do it like this:
94 like this:
104 5. If just QUIRK_LSW32_IS_FIRST is set, we do it like this:
118 6. If QUIRK_LSW32_IS_FIRST and QUIRK_MSB_ON_THE_RIGHT are set, we do it like
129 7. If QUIRK_LSW32_IS_FIRST and QUIRK_LITTLE_ENDIAN are set, it looks like
141 are set, it looks like this:
|
| /Documentation/sound/designs/ |
| 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:
[all …]
|
| /Documentation/devicetree/bindings/i2c/ |
| D | google,cros-ec-i2c-tunnel.yaml | 18 other side of the EC (like a battery and PMIC). To get access to
21 The node for this device should be under a cros-ec node like
32 description: The EC bus we'd like to talk to.
|
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-opal-sensor-groups | 8 like power, temperature, frequency, current, etc. They
10 different owners like CSM, Profiler, Job-Scheduler
|
| /Documentation/devicetree/bindings/powerpc/opal/ |
| D | sensor-groups.txt | 17 operations like clearing the min/max history of all
26 sensor groups like clearing min/max, enabling/disabling sensor
|
| /Documentation/networking/device_drivers/cable/ |
| D | sb1000.rst | 107 root to do this. It's better to use a utility like sudo to execute
108 frequently used commands like this with root permissions if possible. If you
110 driver message like this at the console::
123 11. If you can't get site names (like www.yahoo.com) to resolve into
124 IP addresses (like 204.71.200.67), be sure your /etc/resolv.conf file
126 If this doesn't help, try something like ``ping -c 5 204.71.200.67`` to
137 interface. It looks like I'm connected but I can't even ping any
203 and try setting the delay to something like 60 microseconds with:
205 it out. If it still doesn't work or you like playing with the driver, you may
|
| /Documentation/process/ |
| D | botching-up-ioctls.rst | 19 only cover technicalities and not the big-picture issues like what the command
20 submission ioctl exactly should look like. Learning these lessons is probably
31 the kernel has special types like __u32, __s64. Use them.
47 diminishes the checking tools like sparse can provide. The macro
117 killable. GPUs just die and your users won't like you more if you hang their
137 derived from different clock domains like your main system clock (provided
154 Especially if your reference clock is something really slow like the display
187 that the per-device modeset objects like connectors share a namespace with
215 per-device settings, or for child objects with fairly static lifetimes (like
|
| /Documentation/devicetree/bindings/board/ |
| D | fsl-board.txt | 52 Some Freescale boards like BSC9132QDS have on board FPGA connected on
69 Some Freescale boards like T1040RDB have an on board CPLD connected.
72 - compatible: Should be a board-specific string like "fsl,<board>-cpld"
|
| /Documentation/gpu/ |
| D | introduction.rst | 8 make use of DRM functions to make tasks like memory management,
64 have formal kerneldoc comments. Use normal C comments if you feel like a comment
83 Mostly the DRM subsystem works like any other kernel subsystem, see :ref:`the
96 After that point only bugfixes (like after the upstream merge window has closed
103 blackout period. As an example, drm-misc works like that.
|
| /Documentation/i2c/ |
| D | i2c-stub.rst | 22 operations. This allows for continuous byte reads like those supported by
33 The typical use-case is like this:
66 something like relayfs.
|
| /Documentation/networking/device_drivers/appletalk/ |
| D | cops.rst | 37 Use modprobe like this: /sbin/modprobe cops.o (IO #) (IRQ #)
46 Or in lilo.conf put something like this::
50 Then bring up the interface with ifconfig. It will look something like this::
61 You will need to configure atalkd with something like the following to make
|
| /Documentation/vm/ |
| D | z3fold.rst | 19 To keep the determinism and simplicity, z3fold, just like zbud, always
24 Unlike zbud (but like zsmalloc for that matter) z3fold_alloc() does not
|
| /Documentation/fb/ |
| 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
|
| /Documentation/i2c/busses/ |
| D | i2c-sis630.rst | 38 If you see something like this::
43 or like this::
48 or like this::
|
| /Documentation/power/ |
| D | swsusp-dmcrypt.rst | 24 the key(s) from an external device like a pcmcia flash disk
34 it will always look like the following::
44 modify. For lilo the simplest setup looks like the following
58 like the following::
123 for init like "single" or "emergency" as boot parameters.
|
| /Documentation/devicetree/bindings/arm/ |
| D | vexpress-scc.txt | 10 (like silicon temperature sensors) and as interface to other subsystems
11 like platform configuration control and power management.
|
| /Documentation/firmware-guide/acpi/ |
| D | enumeration.rst | 64 If the driver needs to perform more complex initialization like getting and
73 like to be accessible to slave devices via generic API call
74 dma_request_chan() must register itself at the end of the probe function like
83 could look like::
153 Here is what the ACPI namespace for a SPI slave might look like::
190 Note that this driver actually needs more information like page size of the
192 passing those. One idea is to return this in _DSM method like::
212 ACPI handle like::
232 The slaves behind I2C bus controller only need to add the ACPI IDs like
322 a code like this::
[all …]
|
| /Documentation/dev-tools/kunit/ |
| D | index.rst | 47 dependencies outside of the test's control like hardware.
60 like ARM or x86, which compiles the kernel as a Linux executable. KUnit
61 can be used with UML either by building with ``ARCH=um`` (like any other
65 several dozen tests in only 10 to 20 seconds; this might not sound like a big
|
| /Documentation/spi/ |
| D | spi-summary.rst | 28 Unlike serial busses like USB or SMBus, even low level protocols for
30 (except for commodities like SPI memory chips).
44 - Sometimes SPI is used to daisy-chain devices, like shift registers.
79 sensors and codecs, to memory, to peripherals like USB controllers
138 for those calls, including ones for common transaction types like writing
155 data to filesystems stored on SPI flash like DataFlash; and others might
219 like the physical address of the controller's first register and its IRQ.
228 So for example arch/.../mach-*/board-*.c files might have code like::
245 And SOC-specific utility code might look something like::
285 small handful.) That might look like::
[all …]
|
12345678910>>...43