Home
last modified time | relevance | path

Searched full:which (Results 1 – 25 of 5658) sorted by relevance

12345678910>>...227

/Linux-v6.1/drivers/staging/greybus/
Dgpio.c60 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 …]
Dpwm.c42 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-v6.1/tools/perf/pmu-events/arch/arm64/arm/cortex-a76-n1/
Dcache.json3 "PublicDescription": "This event counts any instruction fetch which misses in the cache.",
11 …re operation or page table walk access which causes data to be read from outside the L1, including…
15 …store operation or page table walk access which looks up in the L1 data cache. In particular, any …
23 …or Level 0 Macro-op cache access. This event counts any instruction fetch which accesses the L1 in…
31 …"PublicDescription": "This event counts any transaction from L1 which looks up in the L2 cache, an…
35 …L2 data cache refill. This event counts any cacheable transaction from L1 which causes data to be …
39 …which return data, regardless of whether they cause an invalidation. Invalidations from the L2 whi…
43 …line write into the L2 cache which does not cause a linefill, including write-backs from L1 to L2 …
47 …"PublicDescription": "This event counts any load or store operation which accesses the data L1 TLB…
52 …"PublicDescription": "This event counts any instruction fetch which accesses the instruction L1 TL…
[all …]
/Linux-v6.1/Documentation/process/
D4.Coding.rst8 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 …]
D1.Intro.rst27 :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 …]
Dlicense-rules.rst19 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 …]
D3.Early-stage.rst32 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-v6.1/tools/perf/pmu-events/arch/arm64/arm/cortex-a55/
Dbranch.json18 … "Predicted conditional branch executed.This event counts when any branch which can be predicted b…
21 … "Predicted conditional branch executed.This event counts when any branch which can be predicted b…
24 …"Indirect branch mis-predicted.This event counts when any indirect branch which can be predicted b…
27 …"Indirect branch mis-predicted.This event counts when any indirect branch which can be predicted b…
30 …ted due to address mis-compare.This event counts when any indirect branch which can be predicted b…
33 …ted due to address mis-compare.This event counts when any indirect branch which can be predicted b…
36 …which can be predicted by the conditional predictor is retired, and has mis-predicted the conditio…
39 …which can be predicted by the conditional predictor is retired, and has mis-predicted the conditio…
42 …ith predicted address executed.This event counts when any indirect branch which can be predicted b…
45 …ith predicted address executed.This event counts when any indirect branch which can be predicted b…
[all …]
/Linux-v6.1/tools/testing/kunit/test_data/
Dtest_is_test_passed-no_tests_run_no_header.log39 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 …]
Dtest_output_isolated_correctly.log61 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-v6.1/Documentation/dev-tools/
Dktap.rst11 which don't align with the original TAP specification. Thus, a "Kernel TAP"
16 KTAP test results describe a series of tests (which may be nested: i.e., test
17 can have subtests), each of which can contain both diagnostic data -- e.g., log
31 a couple of places (notably the "Subtest" header), which are described where
37 All KTAP-formatted results begin with a "version line" which specifies which
45 Note that, in KTAP, subtests also begin with a version line, which denotes the
46 start of the nested test results. This differs from TAP14, which uses a
62 which case the test plan may be omitted -- it is strongly recommended one is
75 The result can be either "ok", which indicates the test case passed,
76 or "not ok", which indicates that the test case failed.
[all …]
/Linux-v6.1/tools/perf/pmu-events/arch/powerpc/power10/
Dpipeline.json30 "BriefDescription": "Cycles in which an instruction reload is pending to satisfy a demand miss."
45 …"BriefDescription": "Cycles in which the oldest instruction in the pipeline finished at dispatch a…
60 …"BriefDescription": "Cycles in which the oldest instruction in the pipeline was a lwsync waiting t…
80 …"BriefDescription": "Cycles in which the oldest instruction in the pipeline was dispatched but not…
95 …"BriefDescription": "Cycles in which the oldest instruction in the pipeline required special handl…
100 …"BriefDescription": "Cycles in which the oldest instruction in the pipeline was waiting for a load…
115 …"BriefDescription": "Cycles in which the oldest instruction in the pipeline was executing in the V…
120 …"BriefDescription": "Cycles in which the oldest instruction in the pipeline was a stcx waiting for…
125 …"BriefDescription": "Cycles in which the oldest instruction in the pipeline was executing in any u…
135 …"BriefDescription": "Cycles in which the oldest instruction in the pipeline (NTC) finishes. Note t…
[all …]
Dcache.json5 …"BriefDescription": "Cycles in which the oldest instruction in the pipeline was waiting for a load…
10 …"BriefDescription": "Cycles in which the oldest instruction in the pipeline was waiting for a load…
15 …"BriefDescription": "Cycles in which the oldest instruction in the pipeline was waiting for a load…
20 …which the oldest instruction in the pipeline was finishing a load after its data was reloaded from…
35 …"BriefDescription": "Cycles in which the oldest instruction in the pipeline was waiting for a load…
40 …"BriefDescription": "Cycles in which the oldest instruction in the pipeline was a load instruction…
45 …"BriefDescription": "Cycles in which the oldest instruction in the pipeline was a PTESYNC instruct…
Dfrontend.json5 …"BriefDescription": "Cycles in which the oldest instruction in the pipeline suffered a TLB miss or…
10 …"BriefDescription": "Cycles in which the NTC instruction is held at dispatch for any other reason."
35 …"BriefDescription": "Cycles in which the NTC instruction is held at dispatch because of power mana…
40 …"BriefDescription": "Cycles in which the NTC instruction is held at dispatch because the STF mappe…
65 "BriefDescription": "Cycles in which at least one instruction is completed by this thread."
80 …"BriefDescription": "Cycles in which the NTC instruction is held at dispatch due to Issue queue fu…
90 …"BriefDescription": "Cycles in which the oldest instruction in the pipeline was executing in the L…
115 …"BriefDescription": "Cycles in which the NTC instruction is held at dispatch because the XVFC mapp…
155 …"BriefDescription": "Cycles in which the oldest instruction in the pipeline was a store instructio…
160 …"BriefDescription": "Cycles in which the NTC instruction is held at dispatch while waiting on the …
[all …]
/Linux-v6.1/drivers/mtd/chips/
DKconfig22 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
79 some other configuration options which would allow you to reduce
82 which are supported by the current code will be enabled.
88 If you wish to support CFI devices on a physical bus which is
95 If you wish to support CFI devices on a physical bus which is
102 If you wish to support CFI devices on a physical bus which is
[all …]
/Linux-v6.1/net/bridge/netfilter/
DKconfig96 This option adds the among match, which allows matching the MAC source
105 This option adds the ARP match, which allows ARP and RARP header field
113 This option adds the IP match, which allows basic IP header field
122 This option adds the IP6 match, which allows basic IPV6 header field
130 This option adds the limit match, which allows you to control
131 the rate at which a rule can be matched. This match is the
140 This option adds the mark match, which allows matching frames based on
150 This option adds the packet type match, which allows matching on the
160 This option adds the Spanning Tree Protocol match, which
168 This option adds the 802.1Q vlan match, which allows the filtering of
[all …]
/Linux-v6.1/net/netfilter/ipset/
DKconfig32 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-v6.1/tools/testing/selftests/timers/
Dposix_timers.c77 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-v6.1/Documentation/x86/
Dmds.rst17 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-v6.1/tools/perf/pmu-events/arch/arm64/arm/cortex-a73/
Dpipeline.json15 "PublicDescription": "Duration for which all slots in the Load-Store Unit are busy",
18 "BriefDescription": "Duration for which all slots in the Load-Store Unit are busy"
21 "PublicDescription": "Duration for which all slots in the load-store issue queue are busy",
24 "BriefDescription": "Duration for which all slots in the load-store issue queue are busy"
27 … "PublicDescription": "Duration for which all slots in the data processing issue queue are busy",
30 … "BriefDescription": "Duration for which all slots in the data processing issue queue are busy"
33 "PublicDescription": "Duration for which all slots in the Data Engine issue queue are busy",
36 "BriefDescription": "Duration for which all slots in the Data Engine issue queue are busy"
/Linux-v6.1/Documentation/filesystems/
Dext2.rst49 resuid=n The user ID which may use the reserved blocks.
50 resgid=n The group ID which may use the reserved blocks.
88 which is decided when the filesystem is created. Smaller blocks mean
100 bitmap and the inode usage bitmap which show which blocks and inodes
107 in the same block group as the inode which contains them.
129 and which OS created it.
144 structure contains pointers to the filesystem blocks which contain the
151 There are some reserved fields which are currently unused in the inode
152 structure and several which are overloaded. One field is reserved for the
156 by the HURD to reference the inode of a program which will be used to
[all …]
/Linux-v6.1/Documentation/timers/
Dhighres.rst6 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-v6.1/include/linux/
Ddevm-helpers.h6 * Functions which do automatically cancel operations or release resources upon
10 * management which can be source of annoying, rarely occurring,
22 * and schedule a work item which won't be cancelled because remove() was
36 * @dev: Device which lifetime work is bound to
40 * Initialize delayed work which is automatically cancelled when driver is
41 * detached. A few drivers need delayed work which must be cancelled before
61 * @dev: Device which lifetime work is bound to
65 * Initialize work which is automatically cancelled when driver is detached.
66 * A few drivers need to queue work which must be cancelled before driver
/Linux-v6.1/include/trace/events/
Dtimer.h230 * @now: pointer to variable which contains current time of the
302 * @which: name of the interval timer
309 TP_PROTO(int which, const struct itimerspec64 *const value,
312 TP_ARGS(which, value, expires),
315 __field( int, which )
324 __entry->which = which;
332 TP_printk("which=%d expires=%llu it_value=%ld.%06ld it_interval=%ld.%06ld",
333 __entry->which, __entry->expires,
340 * @which: type of the interval timer
341 * @pid: pid of the process which owns the timer
[all …]
/Linux-v6.1/Documentation/admin-guide/
Dcgroup-v2.rst117 although there are utility controllers which serve purposes other than
130 processes which belong to the cgroups consisting the inclusive
149 controllers which support v2 and are not bound to a v1 hierarchy are
151 Controllers which are not in active use in the v2 hierarchy can be
220 Initially, only the root cgroup exists to which all processes belong.
227 "cgroup.procs". When read, it lists the PIDs of all processes which
245 A cgroup which doesn't have any children or live processes can be
246 destroyed by removing the directory. Note that a cgroup which doesn't
275 process belong to the same cgroup, which also serves as the resource
276 domain to host resource consumptions which are not specific to a
[all …]

12345678910>>...227