Home
last modified time | relevance | path

Searched refs:of (Results 1 – 25 of 7264) sorted by relevance

12345678910>>...291

/Linux-v5.4/fs/kernfs/
Dfile.c94 struct kernfs_open_file *of = sf->private; in kernfs_seq_stop_active() local
95 const struct kernfs_ops *ops = kernfs_ops(of->kn); in kernfs_seq_stop_active()
99 kernfs_put_active(of->kn); in kernfs_seq_stop_active()
104 struct kernfs_open_file *of = sf->private; in kernfs_seq_start() local
111 mutex_lock(&of->mutex); in kernfs_seq_start()
112 if (!kernfs_get_active(of->kn)) in kernfs_seq_start()
115 ops = kernfs_ops(of->kn); in kernfs_seq_start()
133 struct kernfs_open_file *of = sf->private; in kernfs_seq_next() local
134 const struct kernfs_ops *ops = kernfs_ops(of->kn); in kernfs_seq_next()
154 struct kernfs_open_file *of = sf->private; in kernfs_seq_stop() local
[all …]
/Linux-v5.4/Documentation/filesystems/caching/
Dfscache.txt70 FS-Cache does not follow the idea of completely loading every netfs file
72 then serving the pages out of that cache rather than the netfs inode because:
76 (2) The size of any accessible file must not be limited to the size of the
79 (3) The combined size of all opened files (this includes mapped libraries)
80 must not be limited to the size of the cache.
83 one-off access of a small portion of it (such as might be done with the
93 explicitly by use of tags.
109 recursive, stack space is limited, and indices can only be children of
113 indicates that page A is at index B of the data-file represented by cookie
131 and pages are kept. Bits of this tree may actually reside in one or more
[all …]
/Linux-v5.4/Documentation/sound/designs/
Dtracepoints.rst12 This subsystem includes two categories of tracepoints; for state of PCM buffer
13 and for processing of PCM hardware parameters. These tracepoints are available
18 Tracepoints for state of PCM buffer
24 Tracepoints for processing of PCM hardware parameters
30 In a design of ALSA PCM core, data transmission is abstracted as PCM substream.
34 interaction between applications and ALSA PCM core. Once decided, runtime of
38 structure includes several types of parameters. Applications set preferable
41 set of parameters. The latter is used for an actual decision of the parameters.
49 Configurable. This type of parameter is described in
50 :c:type:`struct snd_mask` and represent mask values. As of PCM protocol
[all …]
/Linux-v5.4/Documentation/devicetree/bindings/net/
Dmicrel-ksz90x1.txt20 change the driver now because of the many existing device trees that have
21 been created using values that go up in increments of 200.
23 The following table shows the actual skew delay you will get for each of the
48 - rxc-skew-ps : Skew control of RXC pad
49 - rxdv-skew-ps : Skew control of RX CTL pad
50 - txc-skew-ps : Skew control of TXC pad
51 - txen-skew-ps : Skew control of TX CTL pad
52 - rxd0-skew-ps : Skew control of RX data 0 pad
53 - rxd1-skew-ps : Skew control of RX data 1 pad
54 - rxd2-skew-ps : Skew control of RX data 2 pad
[all …]
/Linux-v5.4/Documentation/admin-guide/
Diostats.rst16 is mounted on ``/sys``, although of course it may be mounted anywhere.
20 Here are examples of these different formats::
38 a choice of ``cat /sys/block/hda/stat`` or ``grep 'hda ' /proc/diskstats``.
40 The advantage of one over the other is that the sysfs choice works well
41 if you are watching a known, small set of disks. ``/proc/diskstats`` may
42 be a better choice if you are watching a large number of disks because
43 you'll avoid the overhead of 50, 100, or 500 or more opens/closes with
44 each snapshot of your disk statistics.
47 the above example, the first field of statistics would be 446216.
51 minor device numbers, and device name. Each of these formats provides
[all …]
/Linux-v5.4/Documentation/process/
Dcode-of-conduct-interpretation.rst3 Linux Kernel Contributor Covenant Code of Conduct Interpretation
7 provide a set of rules for almost any open source community. Every
9 Because of this, this document describes how we in the Linux kernel
14 to "traditional" ways of developing software. Your contributions and
19 the best possible solution for the overall success of Linux. This
22 quality of submission and eventual result to ever decrease.
27 The Code of Conduct uses the term "maintainers" numerous times. In the
35 The Code of Conduct mentions rights and responsibilities for
43 behave in the parts of the community where they are active. That
44 responsibility is upon all of us, and ultimately the Code of Conduct
[all …]
D1.Intro.rst9 The rest of this section covers the scope of the kernel development process
10 and the kinds of frustrations that developers and their employers can
14 influence the direction of kernel development. Code contributed to the
18 release cycle, and the mechanics of the merge window. The various phases in
20 discussion of tools and mailing lists. Developers wanting to get started
29 patches are covered, and there is an introduction to some of the tools
32 :ref:`development_posting` talks about the process of posting patches for
40 of the development process; this section offers a number of tips on how to
44 :ref:`development_advancedtopics` introduces a couple of "advanced" topics:
53 The Linux kernel, at over 8 million lines of code and well over 1000
[all …]
Dcode-of-conduct.rst3 Contributor Covenant Code of Conduct
9 In the interest of fostering an open and welcoming environment, we as
11 our community a harassment-free experience for everyone, regardless of age, body
13 expression, level of experience, education, socio-economic status, nationality,
19 Examples of behavior that contributes to creating a positive environment
23 * Being respectful of differing viewpoints and experiences
29 Examples of unacceptable behavior by participants include:
31 * The use of sexualized language or imagery and unwelcome sexual attention or
44 Maintainers are responsible for clarifying the standards of acceptable behavior
46 any instances of unacceptable behavior.
[all …]
/Linux-v5.4/Documentation/devicetree/bindings/display/
Dst,stih4xx.txt6 - reg: Physical base address of the IP registers and length of memory mapped region.
14 - reg: Physical base address of the IP registers and length of memory mapped region.
16 number of clocks may depend of the SoC type.
18 - clock-names: names of the clocks listed in clocks property in the same
22 This device must be the parent of all the sub-components and is responsible
23 of bind them.
26 - ranges: to allow probing of subdevices
29 must be a child of sti-display-subsystem
32 - reg: Physical base address of the IP registers and length of memory mapped region.
34 number of clocks may depend of the SoC type.
[all …]
/Linux-v5.4/Documentation/scheduler/
Dsched-stats.rst5 Version 15 of schedstats dropped counters for some sched_yield:
9 Version 14 of schedstats includes support for sched_domains, which hit the
16 In version 14 of schedstat, there is at least one level of domain
21 sometimes balancing only between pairs of cpus. At this time, there
27 of these will need to start with a baseline observation and then calculate
29 which does this for many of the fields is available at
43 1) # of times sched_yield() was called
49 3) # of times schedule() was called
50 4) # of times schedule() left the processor idle
54 5) # of times try_to_wake_up() was called
[all …]
/Linux-v5.4/Documentation/media/uapi/
Dfdl-appendix.rst2 .. document under the terms of the GNU Free Documentation License,
5 .. and no Back-Cover Texts. A copy of the license is included at
22 The purpose of this License is to make a manual, textbook, or other
23 written document “free” in the sense of freedom: to assure everyone the
30 This License is a kind of “copyleft”, which means that derivative works
31 of the document must themselves be free in the same sense. It
39 used for any textual work, regardless of subject matter or whether it is
54 terms of this License. The “Document”, below, refers to any such manual
55 or work. Any member of the public is a licensee, and is addressed as
61 A “Modified Version” of the Document means any work containing the
[all …]
/Linux-v5.4/Documentation/devicetree/bindings/i2c/
Drenesas,i2c.txt5 "renesas,i2c-r8a7743" if the device is a part of a R8A7743 SoC.
6 "renesas,i2c-r8a7744" if the device is a part of a R8A7744 SoC.
7 "renesas,i2c-r8a7745" if the device is a part of a R8A7745 SoC.
8 "renesas,i2c-r8a77470" if the device is a part of a R8A77470 SoC.
9 "renesas,i2c-r8a774a1" if the device is a part of a R8A774A1 SoC.
10 "renesas,i2c-r8a774c0" if the device is a part of a R8A774C0 SoC.
11 "renesas,i2c-r8a7778" if the device is a part of a R8A7778 SoC.
12 "renesas,i2c-r8a7779" if the device is a part of a R8A7779 SoC.
13 "renesas,i2c-r8a7790" if the device is a part of a R8A7790 SoC.
14 "renesas,i2c-r8a7791" if the device is a part of a R8A7791 SoC.
[all …]
/Linux-v5.4/LICENSES/dual/
DApache-2.025 distribution as defined by Sections 1 through 9 of this document.
30 "Legal Entity" shall mean the union of the acting entity and all other
32 that entity. For the purposes of this definition, "control" means (i) the
33 power, direct or indirect, to cause the direction or management of such
34 entity, whether by contract or otherwise, or (ii) ownership of fifty
35 percent (50%) or more of the outstanding shares, or (iii) beneficial
36 ownership of such entity.
46 or translation of a Source form, including but not limited to compiled
49 "Work" shall mean the work of authorship, whether in Source or Object form,
57 a whole, an original work of authorship. For the purposes of this License,
[all …]
DMPL-1.125 the creation of Modifications.
27 1.2. "Contributor Version" means the combination of the Original
32 combination of the Original Code and Modifications, in each case
37 transfer of data.
47 portions thereof with code not governed by the terms of this License.
52 extent possible, whether at the time of the initial grant or
53 subsequently acquired, any and all of the rights conveyed herein.
56 substance or structure of either the Original Code or any previous
57 Modifications. When Covered Code is released as a series of files, a
59 A. Any addition to or deletion from the contents of a file
[all …]
/Linux-v5.4/Documentation/filesystems/ext4/
Dgroup_descr.rst6 Each block group on the filesystem has one of these descriptors
9 standard configuration is for each block group to contain a full copy of
13 Notice how the group descriptor records the location of both bitmaps and
18 of the groups' bitmaps and inode tables into one long run in the first
19 group of the flex group.
36 checksum is the crc16 of the FS UUID, the group number, and the group
38 checksum is the lower 16 bits of the checksum of the FS UUID, the group
56 - Lower 32-bits of location of block bitmap.
60 - Lower 32-bits of location of inode bitmap.
64 - Lower 32-bits of location of inode table.
[all …]
/Linux-v5.4/Documentation/input/
Dmulti-touch-protocol.rst13 In order to utilize the full power of the new multi-touch and multi-user
17 drivers to report details for an arbitrary number of contacts.
19 The protocol is divided into two types, depending on the capabilities of the
22 devices capable of tracking identifiable contacts (type B), the protocol
32 Contact details are sent sequentially as separate packets of ABS_MT
33 events. Only the ABS_MT events are recognized as part of a contact
35 applications, the MT protocol can be implemented on top of the ST protocol
39 input_mt_sync() at the end of each packet. This generates a SYN_MT_REPORT
44 input_mt_slot(), with a slot as argument, at the beginning of each packet.
46 prepare for updates of the given slot.
[all …]
/Linux-v5.4/arch/mips/include/asm/
Dwar.h82 #error Check setting of R4600_V1_INDEX_ICACHEOP_WAR for your platform
112 #error Check setting of R4600_V1_HIT_CACHEOP_WAR for your platform
128 #error Check setting of R4600_V2_HIT_CACHEOP_WAR for your platform
142 #error Check setting of BCM1250_M3_WAR for your platform
149 #error Check setting of SIBYTE_1956_WAR for your platform
165 #error Check setting of MIPS4K_ICACHE_REFILL_WAR for your platform
184 #error Check setting of MIPS_CACHE_SYNC_WAR for your platform
195 #error Check setting of TX49XX_ICACHE_INDEX_INV_WAR for your platform
205 #error Check setting of ICACHE_REFILLS_WORKAROUND_WAR for your platform
213 #error Check setting of R10000_LLSC_WAR for your platform
[all …]
/Linux-v5.4/Documentation/admin-guide/mm/
Dhugetlbpage.rst10 The intent of this file is to give a brief summary of hugetlbpage support in
11 the Linux kernel. This support is built on top of multiple page size support
15 256M and ppc64 supports 4K and 16M. A TLB is a cache of virtual-to-physical
17 Operating systems try to make best use of limited number of TLB resources.
29 The ``/proc/meminfo`` file provides information about the total number of
31 default huge page size and information about the number of free, reserved
32 and surplus huge pages in the pool of huge pages of default size.
34 size of the arguments to system calls that map huge page regions.
36 The output of ``cat /proc/meminfo`` will include lines like::
48 is the size of the pool of huge pages.
[all …]
/Linux-v5.4/Documentation/driver-api/early-userspace/
Dbuffer-format.rst14 expanded into a ramfs filesystem; this document details the format of
19 archive can be compressed using gzip(1). One valid version of an
22 The full format of the initramfs buffer is defined by the following
25 * is used to indicate "0 or more occurrences of"
28 GZIP() indicates the gzip(1) of the operand
42 In human terms, the initramfs buffer contains a collection of
47 The cpio "TRAILER!!!" entry (cpio end-of-archive) is optional, but is
48 not ignored; see "handling of hard links" below.
50 The structure of the cpio_header is as follows (all fields contain
52 full width of the field, for example, the integer 4780 is represented
[all …]
/Linux-v5.4/arch/x86/math-emu/
DREADME9 | it under the terms of the GNU General Public License version 2 as |
13 | but WITHOUT ANY WARRANTY; without even the implied warranty of |
17 | You should have received a copy of the GNU General Public License |
26 which was my 80387 emulator for early versions of djgpp (gcc under
33 facets of the functioning of the FPU are not well covered in the
36 possible to be sure that all of the peculiarities of the 80486 have
38 in the detailed behaviour of the emulator and a real 80486.
40 wm-FPU-emu does not implement all of the behaviour of the 80486 FPU,
41 but is very close. See "Limitations" later in this file for a list of
56 ----------------------- Internals of wm-FPU-emu -----------------------
[all …]
/Linux-v5.4/Documentation/block/
Dstat.rst5 This file documents the contents of the /sys/block/<dev>/stat file.
7 The stat file provides several statistics about the state of block
16 represent a consistent snapshot of the state of the device. If the
18 each, it would be impossible to guarantee that a set of readings
21 The stat file consists of a single line of text containing 11 decimal
29 read I/Os requests number of read I/Os processed
30 read merges requests number of read I/Os merged with in-queue I/O
31 read sectors sectors number of sectors read
33 write I/Os requests number of write I/Os processed
34 write merges requests number of write I/Os merged with in-queue I/O
[all …]
/Linux-v5.4/Documentation/pcmcia/
Ddriver-changes.rst7 * pcmcia_loop_config() and autoconfiguration (as of 2.6.36)
20 * pcmcia_request_configuration -> pcmcia_enable_device (as of 2.6.36)
26 * pcmcia_request_window changes (as of 2.6.36)
27 Instead of win_req_t, drivers are now requested to fill out
33 * pcmcia_request_io changes (as of 2.6.36)
34 Instead of io_req_t, drivers are now requested to fill out
40 * No dev_info_t, no cs_types.h (as of 2.6.36)
45 * No dev_node_t (as of 2.6.35)
48 * New IRQ request rules (as of 2.6.35)
49 Instead of the old pcmcia_request_irq() interface, drivers may now
[all …]
/Linux-v5.4/LICENSES/preferred/
DLGPL-2.15 To use this license in source code, put one of the following SPDX
21 Everyone is permitted to copy and distribute verbatim copies of this
24 [This is the first released version of the Lesser GPL. It also counts as
25 the successor of the GNU Library Public License, version 2, hence the
36 designated software packages--typically libraries--of the Free Software
42 When we speak of free software, we are referring to freedom of use, not
44 the freedom to distribute copies of free software (and charge for this
46 want it; that you can change the software and use pieces of it in new free
52 you distribute copies of the library or if you modify it.
54 For example, if you distribute copies of the library, whether gratis or for
[all …]
/Linux-v5.4/Documentation/devicetree/bindings/mfd/
Daspeed-lpc.txt5 The LPC bus is a means to bridge a host CPU to a number of low-bandwidth
6 peripheral devices, replacing the use of the ISA bus in the age of PCI[0]. The
7 primary use case of the Aspeed LPC controller is as a slave on the bus
9 conditions it can also take the role of bus master.
12 mix of functionality it provides. The principle split is between the register
13 layout at the start of the I/O space which is, to quote the Aspeed datasheet,
16 collection of functions with a esoteric register layout. "Everything else",
17 here labeled the "host" portion of the controller, includes, but is not limited
23 physical properties of some LPC pins, configuration of serial IRQs, and
27 as LPC firmware hub cycles, configuration of the LPC-to-AHB mapping, UART
[all …]
/Linux-v5.4/Documentation/ABI/testing/
Dsysfs-class-net-statistics6 Indicates the number of collisions seen by this network device.
14 Indicates the number of multicast packets received by this
22 Indicates the number of bytes received by this network device.
23 See the network driver for the exact meaning of when this
31 Indicates the number of compressed packets received by this
40 Indicates the number of packets received with a CRC (FCS) error
49 Indicates the number of packets received by the network device
52 meaning of this value.
59 Indicates the number of receive FIFO errors seen by this
61 meaning of this value.
[all …]

12345678910>>...291