| /Linux-v5.10/drivers/staging/greybus/ |
| D | gpio.c | 60 static int gb_gpio_activate_operation(struct gb_gpio_controller *ggc, u8 which) in gb_gpio_activate_operation() argument
70 request.which = which; in gb_gpio_activate_operation()
78 ggc->lines[which].active = true; in gb_gpio_activate_operation()
84 u8 which) in gb_gpio_deactivate_operation() argument
91 request.which = which; in gb_gpio_deactivate_operation()
95 dev_err(dev, "failed to deactivate gpio %u\n", which); in gb_gpio_deactivate_operation()
99 ggc->lines[which].active = false; in gb_gpio_deactivate_operation()
106 u8 which) in gb_gpio_get_direction_operation() argument
114 request.which = which; in gb_gpio_get_direction_operation()
124 which, direction); in gb_gpio_get_direction_operation()
[all …]
|
| D | pwm.c | 42 u8 which) in gb_pwm_activate_operation() argument
48 if (which > pwmc->pwm_max) in gb_pwm_activate_operation()
51 request.which = which; in gb_pwm_activate_operation()
67 u8 which) in gb_pwm_deactivate_operation() argument
73 if (which > pwmc->pwm_max) in gb_pwm_deactivate_operation()
76 request.which = which; in gb_pwm_deactivate_operation()
92 u8 which, u32 duty, u32 period) in gb_pwm_config_operation() argument
98 if (which > pwmc->pwm_max) in gb_pwm_config_operation()
101 request.which = which; in gb_pwm_config_operation()
119 u8 which, u8 polarity) in gb_pwm_set_polarity_operation() argument
[all …]
|
| /Linux-v5.10/Documentation/process/ |
| D | 4.Coding.rst | 8 code. It is the code which will be examined by other developers and merged
9 (or not) into the mainline tree. So it is the quality of this code which
13 number of ways in which kernel developers can go wrong. Then the focus
14 will shift toward doing things right and the tools which can help in that
28 which does not meet the coding style guidelines. The presence of that code
46 The other trap is to assume that code which is already in the kernel is
56 The coding style document also should not be read as an absolute law which
58 style (a line which becomes far less readable if split to fit within the
81 At a simple level, consider a function which has an argument which is
84 provides. By that time, though, chances are good that the code which
[all …]
|
| D | 1.Intro.rst | 27 :ref:`development_coding` is about the coding process; several pitfalls which
30 which can help to ensure that kernel patches are correct.
56 kernel has evolved into a best-of-breed operating system component which
75 offer this kind of openness, which is a characteristic of the free software
84 evolved its own distinct ways of operating which allow it to function
132 - Code which has been merged into the mainline kernel is available to all
133 Linux users. It will automatically be present on all distributions which
148 Code which is in the mainline, instead, does not require this work as the
151 which has been merged into the mainline has significantly lower
154 - Beyond that, code which is in the kernel will often be improved by other
[all …]
|
| D | license-rules.rst | 19 which is required to be compatible with the GPL-2.0::
32 The User-space API (UAPI) header files, which describe the interface of
35 which does not extend the GPL requirements to any software which uses it to
37 into any source files which create an executable running on the Linux
43 tools which are used in the context of license compliance.
48 under which the content of the file is contributed. SPDX license
64 possible line in a file which can contain a comment. For the majority
65 of files this is the first line, except for scripts which require the
84 appropriate comment mechanism which the tool accepts shall be used. This
88 there are still older assembler tools which cannot handle C++ style
[all …]
|
| D | 3.Early-stage.rst | 32 misuse of the LSM framework (which is not intended to confer privileges
33 onto processes which they would not otherwise have) and a risk to system
61 - What, exactly, is the problem which needs to be solved?
63 - Who are the users affected by this problem? Which use cases should the
78 - It may well be that the problem is addressed by the kernel in ways which
80 features and capabilities which are not immediately obvious. Not all
83 driver which duplicated an existing driver that the new author had been
84 unaware of. Code which reinvents existing wheels is not only wasteful;
87 - There may be elements of the proposed solution which will not be
96 clear lesson: kernel code which is designed and developed behind closed
[all …]
|
| /Linux-v5.10/tools/perf/pmu-events/arch/arm64/arm/cortex-a76-n1/ |
| D | cache.json | 3 …n": "L1 instruction cache refill. This event counts any instruction fetch which misses in the cach…
15 …re operation or page table walk access which causes data to be read from outside the L1, including…
21 …store operation or page table walk access which looks up in the L1 data cache. In particular, any …
33 …or Level 0 Macro-op cache access. This event counts any instruction fetch which accesses the L1 in…
45 …"PublicDescription": "L2 data cache access. This event counts any transaction from L1 which looks …
51 …L2 data cache refill. This event counts any cacheable transaction from L1 which causes data to be …
57 …which return data, regardless of whether they cause an invalidation. Invalidations from the L2 whi…
63 …line write into the L2 cache which does not cause a linefill, including write-backs from L1 to L2 …
69 …: "Level 1 data TLB access. This event counts any load or store operation which accesses the data …
75 … "Level 1 instruction TLB access. This event counts any instruction fetch which accesses the instr…
[all …]
|
| /Linux-v5.10/tools/testing/kunit/test_data/ |
| D | test_is_test_passed-no_tests_run.log | 39 Using a channel type which is configured out of UML
41 Using a channel type which is configured out of UML
43 Using a channel type which is configured out of UML
45 Using a channel type which is configured out of UML
47 Using a channel type which is configured out of UML
49 Using a channel type which is configured out of UML
51 Using a channel type which is configured out of UML
53 Using a channel type which is configured out of UML
55 Using a channel type which is configured out of UML
57 Using a channel type which is configured out of UML
[all …]
|
| D | test_output_isolated_correctly.log | 61 Using a channel type which is configured out of UML
63 Using a channel type which is configured out of UML
65 Using a channel type which is configured out of UML
67 Using a channel type which is configured out of UML
69 Using a channel type which is configured out of UML
71 Using a channel type which is configured out of UML
73 Using a channel type which is configured out of UML
75 Using a channel type which is configured out of UML
77 Using a channel type which is configured out of UML
79 Using a channel type which is configured out of UML
[all …]
|
| /Linux-v5.10/drivers/mtd/chips/ |
| D | Kconfig | 22 This option enables JEDEC-style probing of flash chips which are not
24 CFI-targeted flash drivers for any chips which are identified which
40 configuration options which allow you to do so.
49 This option defines the way in which the CPU attempts to arrange
51 'NO', which is the default when CONFIG_MTD_CFI_ADV_OPTIONS isn't
77 some other configuration options which would allow you to reduce
80 which are supported by the current code will be enabled.
86 If you wish to support CFI devices on a physical bus which is
93 If you wish to support CFI devices on a physical bus which is
100 If you wish to support CFI devices on a physical bus which is
[all …]
|
| /Linux-v5.10/net/bridge/netfilter/ |
| D | Kconfig | 98 This option adds the among match, which allows matching the MAC source
107 This option adds the ARP match, which allows ARP and RARP header field
115 This option adds the IP match, which allows basic IP header field
124 This option adds the IP6 match, which allows basic IPV6 header field
132 This option adds the limit match, which allows you to control
133 the rate at which a rule can be matched. This match is the
142 This option adds the mark match, which allows matching frames based on
152 This option adds the packet type match, which allows matching on the
162 This option adds the Spanning Tree Protocol match, which
170 This option adds the 802.1Q vlan match, which allows the filtering of
[all …]
|
| /Linux-v5.10/net/netfilter/ipset/ |
| D | Kconfig | 32 This option adds the bitmap:ip set type support, by which one
41 This option adds the bitmap:ip,mac set type support, by which one
50 This option adds the bitmap:port set type support, by which one
59 This option adds the hash:ip set type support, by which one
69 This option adds the hash:ip,mark set type support, by which one
78 This option adds the hash:ip,port set type support, by which one
87 This option adds the hash:ip,port,ip set type support, by which
97 This option adds the hash:ip,port,net set type support, by which
107 This option adds the hash:ip,mac set type support, by which
116 This option adds the hash:mac set type support, by which
[all …]
|
| /Linux-v5.10/tools/testing/selftests/timers/ |
| D | posix_timers.c | 77 static int check_itimer(int which) in check_itimer() argument
87 if (which == ITIMER_VIRTUAL) in check_itimer()
89 else if (which == ITIMER_PROF) in check_itimer()
91 else if (which == ITIMER_REAL) in check_itimer()
98 if (which == ITIMER_VIRTUAL) in check_itimer()
100 else if (which == ITIMER_PROF) in check_itimer()
102 else if (which == ITIMER_REAL) in check_itimer()
111 err = setitimer(which, &val, NULL); in check_itimer()
117 if (which == ITIMER_VIRTUAL) in check_itimer()
119 else if (which == ITIMER_PROF) in check_itimer()
[all …]
|
| /Linux-v5.10/Documentation/x86/ |
| D | mds.rst | 17 MSBDS leaks Store Buffer Entries which can be speculatively forwarded to a
20 memory address, which can be exploited under certain conditions. Store
23 buffer is repartitioned which can expose data from one thread to the other.
26 L1 miss situations and to hold data which is returned or sent in response
29 deallocated it can retain the stale data of the preceding operations which
30 can then be forwarded to a faulting or assisting load operation, which can
37 contain stale data from a previous operation which can be forwarded to
38 faulting or assisting loads under certain conditions, which again can be
56 - to have a disclosure gadget which exposes the speculatively accessed
59 - to control the pointer through which the disclosure gadget exposes the
[all …]
|
| /Linux-v5.10/Documentation/admin-guide/ |
| D | cgroup-v2.rst | 111 although there are utility controllers which serve purposes other than
124 processes which belong to the cgroups consisting the inclusive
143 controllers which support v2 and are not bound to a v1 hierarchy are
145 Controllers which are not in active use in the v2 hierarchy can be
209 Initially, only the root cgroup exists to which all processes belong.
216 "cgroup.procs". When read, it lists the PIDs of all processes which
234 A cgroup which doesn't have any children or live processes can be
235 destroyed by removing the directory. Note that a cgroup which doesn't
264 process belong to the same cgroup, which also serves as the resource
265 domain to host resource consumptions which are not specific to a
[all …]
|
| /Linux-v5.10/Documentation/filesystems/ |
| D | ext2.rst | 48 resuid=n The user ID which may use the reserved blocks.
49 resgid=n The group ID which may use the reserved blocks.
89 which is decided when the filesystem is created. Smaller blocks mean
101 bitmap and the inode usage bitmap which show which blocks and inodes
108 in the same block group as the inode which contains them.
130 and which OS created it.
145 structure contains pointers to the filesystem blocks which contain the
152 There are some reserved fields which are currently unused in the inode
153 structure and several which are overloaded. One field is reserved for the
157 by the HURD to reference the inode of a program which will be used to
[all …]
|
| /Linux-v5.10/Documentation/timers/ |
| D | highres.rst | 6 and beyond". The paper is part of the OLS 2006 Proceedings Volume 1, which can
13 The slides contain five figures (pages 2, 15, 18, 20, 22), which illustrate the
37 The main differences to the timer wheel, which holds the armed timer_list type
51 sources, which are registered in the framework and selected on a quality based
53 initializes data structures, which are used by the generic time keeping code to
91 service handler, which is almost inherently hardware dependent.
114 a function pointer in the device description structure, which has to be called
125 The framework adds about 700 lines of code which results in a 2KB increase of
153 which inform hrtimers about availability of new hardware. hrtimers validates
155 switching to high resolution mode. This ensures also that a kernel which is
[all …]
|
| /Linux-v5.10/Documentation/i2c/ |
| D | instantiating-devices.rst | 6 level. Instead, the software must know which devices are connected on each
16 for many embedded systems. On such systems, each I2C bus has a number which
18 which live on this bus.
54 additional properties which might be needed to set up the device, please refer
62 which is currently located at :doc:`../firmware-guide/acpi/enumeration`.
71 struct i2c_board_info which is registered by calling
129 The above code instantiates 1 I2C device on the I2C bus which is on the
133 present or not (for example for an optional feature which is not present
159 The above code instantiates up to 1 I2C device on the I2C bus which is on
164 The driver which instantiated the I2C device is responsible for destroying
[all …]
|
| /Linux-v5.10/drivers/staging/media/atomisp/pci/ |
| D | atomisp_subdev.h | 100 * it is used to indicate which parameter it has applied.
105 * non-zero value to indicate which parameter it needs to applu
196 /* Indicates which parameters need to be updated. */
283 /* FIXME: should keep book which maps are currently used
285 * which are in use. Implement by reference counting.
345 /* The list of metadata buffers which have been en-queued to CSS */
347 /* The list of metadata buffers which are ready for userspace to get */
352 /* The list of s3a stat buffers which have been en-queued to CSS */
354 /* The list of s3a stat buffers which are ready for userspace to get */
365 /* This field specifies which camera (v4l2 input) is selected. */
[all …]
|
| /Linux-v5.10/include/trace/events/ |
| D | timer.h | 227 * @now: pointer to variable which contains current time of the
299 * @which: name of the interval timer
306 TP_PROTO(int which, const struct itimerspec64 *const value,
309 TP_ARGS(which, value, expires),
312 __field( int, which )
321 __entry->which = which;
329 TP_printk("which=%d expires=%llu it_value=%ld.%06ld it_interval=%ld.%06ld",
330 __entry->which, __entry->expires,
337 * @which: type of the interval timer
338 * @pid: pid of the process which owns the timer
[all …]
|
| /Linux-v5.10/Documentation/devicetree/bindings/clock/ |
| D | exynos5433-clock.txt | 10 which generates clocks for IMEM/FSYS/G3D/GSCL/HEVC/MSCL/G2D/MFC/PERIC/PERIS
13 which generates clocks for LLI (Low Latency Interface) IP.
15 which generates clocks for DRAM Memory Controller domain.
17 which generates clocks for UART/I2C/SPI/I2S/PCM/SPDIF/PWM/SLIMBUS IPs.
19 which generates clocks for PMU/TMU/MCT/WDT/RTC/SECKEY/TZPC IPs.
21 which generates clocks for USB/UFS/SDMMC/TSI/PDMA IPs.
23 which generates clocks for G2D/MDMA IPs.
25 which generates clocks for Display (DECON/HDMI/DSIM/MIXER) IPs.
27 which generates clocks for Cortex-A5/BUS/AUDIO clocks.
30 which generates global data buses clock and global peripheral buses clock.
[all …]
|
| /Linux-v5.10/arch/x86/math-emu/ |
| D | README | 26 which was my 80387 emulator for early versions of djgpp (gcc under
27 msdos); wm-emu387 was in turn based upon emu387 which was written by
61 is not the obvious one which most people seem to use, but is designed
64 seen it. It is based upon one of those ideas which one carries around
74 a value of pi which is accurate to more than 128 bits. As a consequence,
78 80486, which uses a value of pi which is accurate to 66 bits.
87 variables. The code which accesses user memory is confined to five
97 form of re-entrancy which is required by the Linux kernel.
103 are fewer than those which applied to the 1.xx series of the emulator.
139 able to find the instruction which caused the device-not-present
[all …]
|
| /Linux-v5.10/tools/perf/pmu-events/arch/arm64/hisilicon/hip08/ |
| D | uncore-hha.json | 33 "BriefDescription": "The number of read operations sent by HHA to DDRC which size is 64 bytes",
34 "PublicDescription": "The number of read operations sent by HHA to DDRC which size is 64bytes",
40 … "BriefDescription": "The number of write operations sent by HHA to DDRC which size is 64 bytes",
41 … "PublicDescription": "The number of write operations sent by HHA to DDRC which size is 64 bytes",
47 … "BriefDescription": "The number of read operations sent by HHA to DDRC which size is 128 bytes",
48 … "PublicDescription": "The number of read operations sent by HHA to DDRC which size is 128 bytes",
54 … "BriefDescription": "The number of write operations sent by HHA to DDRC which size is 128 bytes",
55 … "PublicDescription": "The number of write operations sent by HHA to DDRC which size is 128 bytes",
|
| /Linux-v5.10/tools/objtool/Documentation/ |
| D | stack-validation.txt | 9 objtool which runs at compile time. It has a "check" subcommand which
18 .altinstructions, __jump_table, and __ex_table, which can add
21 which gcc sometimes uses jump tables.
23 (Objtool also has an 'orc generate' subcommand which generates debuginfo
48 hand, which most people don't do. So the end result is that
52 functions which call other functions must first create a stack frame
108 Livepatch has an optional "consistency model", which is needed for
125 callable code which should be annotated accordingly.
130 2. Conversely, each section of code which is *not* callable should *not*
137 3. Each callable function which calls another function must have the
[all …]
|
| /Linux-v5.10/Documentation/devicetree/bindings/iommu/ |
| D | mediatek,iommu.txt | 54 smi-common. GALS can been seen as a "asynchronous fifo" which could help
59 "mediatek,mt2701-m4u" for mt2701 which uses generation one m4u HW.
60 "mediatek,mt2712-m4u" for mt2712 which uses generation two m4u HW.
61 "mediatek,mt6779-m4u" for mt6779 which uses generation two m4u HW.
62 "mediatek,mt7623-m4u", "mediatek,mt2701-m4u" for mt7623 which uses
64 "mediatek,mt8167-m4u" for mt8167 which uses generation two m4u HW.
65 "mediatek,mt8173-m4u" for mt8173 which uses generation two m4u HW.
66 "mediatek,mt8183-m4u" for mt8183 which uses generation two m4u HW.
72 Here is the list which require this "bclk":
74 Note that m4u use the EMI clock which always has been enabled before kernel
|
