Home
last modified time | relevance | path

Searched +full:in +full:- +full:and +full:- +full:around (Results 1 – 25 of 318) sorted by relevance

12345678910>>...13

/Documentation/mm/
Dz3fold.rst8 ratio keeping the simplicity and determinism of its predecessor.
10 The main differences between z3fold and zbud are:
13 * z3fold can hold up to 3 compressed pages in its page
14 * z3fold doesn't export any API itself and is thus intended to be used
17 To keep the determinism and simplicity, z3fold, just like zbud, always
20 compression ratio goes to around 2.7x while zbud's one is around 1.7x.
27 depend on MMU enabled and provides more predictable reclaim behavior
28 which makes it a better fit for small and response-critical systems.
/Documentation/process/
D6.Followthrough.rst6 At this point, you have followed the guidelines given so far and, with the
9 developers can make is to conclude that their work is now done. In truth,
15 and, as a result, is heavily oriented toward the improvement of posted
18 standards. A failure to participate in this process is quite likely to
23 ----------------------
25 A patch of any significance will result in a number of comments from other
28 process. Life can be made much easier, though, if you keep a few things in
31 - If you have explained your patch well, reviewers will understand its
32 value and why you went to the trouble of writing it. But that value
34 like to maintain a kernel with this code in it five or ten years later?
[all …]
/Documentation/devicetree/bindings/phy/
Dmediatek,mt7988-xfi-tphy.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/phy/mediatek,mt7988-xfi-tphy.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: MediaTek MT7988 XFI T-PHY
10 - Daniel Golle <daniel@makrotopia.org>
13 The MediaTek XFI SerDes T-PHY provides the physical SerDes lanes
14 used by the (10G/5G) USXGMII PCS and (1G/2.5G) LynxI PCS found in
15 MediaTek's 10G-capabale MT7988 SoC.
16 In MediaTek's SDK sources, this unit is referred to as "pextp".
[all …]
/Documentation/devicetree/bindings/net/
Dmdio.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Andrew Lunn <andrew@lunn.ch>
11 - Florian Fainelli <f.fainelli@gmail.com>
12 - Heiner Kallweit <hkallweit1@gmail.com>
17 bus. These should follow the generic ethernet-phy.yaml document, or
22 pattern: '^mdio(-(bus|external))?(@.+|-([0-9]+))?$'
24 "#address-cells":
27 "#size-cells":
[all …]
/Documentation/timers/
Dtimekeeping.rst2 Clock sources, Clock events, sched_clock() and delay timers
6 abstractions. It partly pertains to the drivers usually found in
7 drivers/clocksource in the kernel tree, but the code may be spread out
10 If you grep through the kernel source you will find a number of architecture-
11 specific implementations of clock sources, clockevents and several likewise
12 architecture-specific overrides of the sched_clock() function and some
17 on this timeline, providing facilities such as high-resolution timers.
18 sched_clock() is used for scheduling and timestamping, and delay timers
23 -------------
26 tells you where you are in time. For example issuing the command 'date' on
[all …]
/Documentation/driver-api/usb/
Derror-codes.rst1 .. _usb-error-codes:
6 :Revised: 2004-Oct-21
8 This is the documentation of (hopefully) all possible error codes (and
13 behave the same except for transfer speed dependent behaviors and the
20 Non-USB-specific:
26 ``-ENOMEM`` no memory for allocation of internal structures
29 USB-specific:
32 ``-EBUSY`` The URB is already active.
34 ``-ENODEV`` specified USB-device or bus doesn't exist
36 ``-ENOENT`` specified interface or endpoint does not exist or
[all …]
/Documentation/accounting/
Dtaskstats-struct.rst7 There are three different groups of fields in the struct taskstats:
9 1) Common and basic accounting fields
10 If CONFIG_TASKSTATS is set, the taskstats interface is enabled and
11 the common fields and basic accounting fields are collected for
18 and::
28 and::
34 4) Per-task and per-thread context switch count statistics
40 Future extension should add fields to the end of the taskstats struct, and
47 1) Common and basic accounting fields::
50 * TAKSTATS_VERSION, which is defined in <linux/taskstats.h>.
[all …]
/Documentation/admin-guide/media/
Davermedia.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Avermedia DVB-T on BT878 Release Notes
12 broader and updated content about that, please check:
16 The Avermedia DVB-T
19 The Avermedia DVB-T is a budget PCI DVB card. It has 3 inputs:
23 * SVIDEO Input (Mini-DIN)
27 Frontend of the Avermedia DVB-T is a Microtune 7202D. A timely
28 post to the linux-dvb mailing list ascertained that the
30 found in the dvb-hw CVS module.
32 The DVB-T card is based around the BT878 chip which is a very
[all …]
/Documentation/filesystems/
Dsplice.rst2 splice and pipes
8 splice is a method for moving blocks of data around inside the kernel,
9 without continually transferring them between the kernel and user space.
11 .. kernel-doc:: fs/splice.c
16 Pipe interfaces are all for in-kernel (builtin image) use. They are not
19 .. kernel-doc:: include/linux/pipe_fs_i.h
22 .. kernel-doc:: fs/pipe.c
/Documentation/driver-api/driver-model/
Ddesign-patterns.rst5 This document describes a few common design patterns found in device drivers.
18 that the device the driver binds to will appear in several instances. This
19 means that the probe() function and all callbacks need to be reentrant.
35 return -ENOMEM;
36 spin_lock_init(&foo->lock);
40 This will create an instance of struct foo in memory every time probe() is
43 state around to all functions that need access to the state and its members.
46 pass around a pointer to struct foo like this::
62 This way you always get a pointer back to the correct instance of foo in
89 queue_work(foo->wq, &foo->offload);
[all …]
/Documentation/devicetree/bindings/iio/
Dmount-matrix.txt2 * is the definition of +/- values practical or counterintuitive?
3 * are the definitions unambiguous and easy to follow?
13 that produce three-dimensional data in relation to the world where it is
18 defined in linear algebra.
22 and thus implying that the component should be mounted in a certain orientation
29 screen and (z) being depth, the axis perpendicular to the screen.
33 and (z) depth to be negative under the screen and positive in front of it,
36 A sensor can be mounted in any angle along the axes relative to the frame of
37 reference. This means that the sensor may be flipped upside-down, left-right,
43 to this world. When using the mounting matrix, the sensor and device orientation
[all …]
/Documentation/scsi/
Dscsi-changer.rst1 .. SPDX-License-Identifier: GPL-2.0
8 with "Type: Medium Changer" in /proc/scsi/scsi.
11 common small CD-ROM changers, neither one-lun-per-slot SCSI changers
19 -------------------
23 and one for the device which actually reads and writes the data. The
24 later may be anything, a MOD, a CD-ROM, a tape or whatever. For the
25 changer device this is a "don't care", he *only* shuffles around the
29 The SCSI changer model is complex, compared to - for example - IDE-CD
34 media transport this one shuffles around the media, i.e. the
39 fill in and remove media from the changer.
[all …]
DChangeLog.sym53c8xx1 Sat May 12 12:00 2001 Gerard Roudier (groudier@club-internet.fr)
2 * version sym53c8xx-1.7.3c
3 - Ensure LEDC bit in GPCNTL is cleared when reading the NVRAM.
4 Fix sent by Stig Telfer <stig@api-networks.com>.
5 - Backport from SYM-2 the work-around that allows to support
7 - Check that we received at least 8 bytes of INQUIRY response
9 - Define scsi_set_pci_device() as nil for kernel < 2.4.4.
10 - + A couple of minor changes.
12 Sat Apr 7 19:30 2001 Gerard Roudier (groudier@club-internet.fr)
13 * version sym53c8xx-1.7.3b
[all …]
/Documentation/usb/
Dohci.rst5 23-Aug-2002
7 The "ohci-hcd" driver is a USB Host Controller Driver (HCD) that is derived
8 from the "usb-ohci" driver from the 2.4 kernel series. The "usb-ohci" code
16 from vendors other than Intel and VIA generally use OHCI.
20 - improved robustness; bugfixes; and less overhead
21 - supports the updated and simplified usbcore APIs
22 - interrupt transfers can be larger, and can be queued
23 - less code, by using the upper level "hcd" framework
24 - supports some non-PCI implementations of OHCI
25 - ... more
[all …]
/Documentation/devicetree/bindings/clock/
Dfsl,plldig.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Wen He <wen.he_1@nxp.com>
14 interface in the display core, as implemented in TSMC CLN28HPM PLL.
15 which generate and offers pixel clocks to Display.
19 const: fsl,ls1028a-plldig
27 '#clock-cells':
30 fsl,vco-hz:
31 description: Optional for VCO frequency of the PLL in Hertz. The VCO frequency
[all …]
/Documentation/ABI/testing/
Dsysfs-bus-iio-adc-envelope-detector12 input +------>-------|+ \
14 .-------. | }---.
16 | dac|-->--|- / |
20 | irq|------<-------'
22 '-------'
25 input signal is centered around the maximum value of the
27 from below in this case and will also invert the result.
37 Number of milliseconds to wait for the comparator in each
Dsysfs-bus-intel_th-devices-msc1 What: /sys/bus/intel_th/devices/<intel_th_id>-msc<msc-id>/wrap
7 What: /sys/bus/intel_th/devices/<intel_th_id>-msc<msc-id>/mode
13 - "single", for contiguous buffer mode (high-order alloc);
14 - "multi", for multiblock mode;
15 - "ExI", for DCI handler mode;
16 - "debug", for debug mode;
17 - any of the currently loaded buffer sinks.
20 provided there are no active users and tracing is not enabled,
23 What: /sys/bus/intel_th/devices/<intel_th_id>-msc<msc-id>/nr_pages
29 In single mode, this is a single number of pages, has to be
[all …]
/Documentation/userspace-api/media/dvb/
Dlegacy_dvb_decoder_api.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later OR GPL-2.0
14 This API has originally been designed for DVB only and is therefore limited to
15 the :ref:`legacy_dvb_decoder_formats` used in such digital TV-broadcastsystems.
20 Nevertheless there have been projects build around this API.
23 .. attention:: Do **not** use this API in new drivers!
25 For audio and video use the :ref:`V4L2 <v4l2spec>` and ALSA APIs.
30 knows which decoder is in use or it is specially written for one decoder type.
39 The API has been designed for DVB and compatible broadcastsystems.
40 Because of that fact the only supported data formats are ISO/IEC 13818-1
44 Timestamps are always MPEG PTS as defined in ITU T-REC-H.222.0 /
[all …]
/Documentation/core-api/irq/
Dirqflags-tracing.rst2 IRQ-flags state tracing
7 The "irq-flags tracing" feature "traces" hardirq and softirq state, in
9 every hardirqs-off/hardirqs-on, softirqs-off/softirqs-on event that
10 happens in the kernel.
13 and CONFIG_PROVE_RW_LOCKING to be offered by the generic lock debugging
14 code. Otherwise only CONFIG_PROVE_MUTEX_LOCKING and
15 CONFIG_PROVE_RWSEM_LOCKING will be offered on an architecture - these
16 are locking APIs that are not used in IRQ context. (the one exception
17 for rwsems is worked around)
19 Architecture support for this is certainly not in the "trivial"
[all …]
/Documentation/driver-api/firmware/
Dfirmware-usage-guidelines.rst10 Drivers that use firmware from linux-firmware should follow the rules in
15 * Firmware files shall be designed in a way that it allows checking for
18 the firmware files in linux-firmware be named with some device
19 specific name, and just the major version. The firmware version should
20 be stored in the firmware header, or as an exception, as part of the
21 firmware file name, in order to let the driver detact any non-ABI
22 fixes/changes. The firmware files in linux-firmware should be
33 non-optionally.
35 * If a security fix needs lockstep firmware and kernel fixes in order to
36 be successful, then all supported major versions in the linux-firmware
[all …]
/Documentation/dev-tools/
Dclang-format.rst3 clang-format
6 ``clang-format`` is a tool to format C/C++/... code according to
7 a set of rules and heuristics. Like most tools, it is not perfect
10 ``clang-format`` can be used for several purposes:
12 - Quickly reformat a block of code to the kernel style. Specially useful
13 when moving code around and aligning/sorting. See clangformatreformat_.
15 - Spot style mistakes, typos and possible improvements in files
18 - Help you follow the coding style rules, specially useful for those
19 new to kernel development or working at the same time in several
22 Its configuration file is ``.clang-format`` in the root of the kernel tree.
[all …]
/Documentation/locking/
Dpreempt-locking.rst2 Proper Locking Under a Preemptible Kernel: Keeping Kernel Code Preempt-Safe
13 those under SMP: concurrency and reentrancy. Thankfully, the Linux preemptible
17 This document is for all kernel hackers. Developing code in the kernel
21 RULE #1: Per-CPU data structures need explicit protection
32 First, since the data is per-CPU, it may not have explicit SMP locking, but
35 protect these situations by disabling preemption around them.
37 You can also use put_cpu() and get_cpu(), which will disable preemption.
44 Under preemption, the state of the CPU must be protected. This is arch-
45 dependent, but includes CPU structures and state not preserved over a context
46 switch. For example, on x86, entering and exiting FPU mode is now a critical
[all …]
/Documentation/sphinx/
Dautomarkup.py1 # SPDX-License-Identifier: GPL-2.0
4 # Apply kernel-specific tweaks after the initial document processing
29 RE_function = re.compile(r'\b(([a-zA-Z_]\w+)\(\))', flags=ascii_p3)
32 # Sphinx 2 uses the same :c:type role for struct, union, enum and typedef
34 RE_generic_type = re.compile(r'\b(struct|union|enum|typedef)\s+([a-zA-Z_]\w+)',
38 # Sphinx 3 uses a different C role for each one of struct, union, enum and
41 RE_struct = re.compile(r'\b(struct)\s+([a-zA-Z_]\w+)', flags=ascii_p3)
42 RE_union = re.compile(r'\b(union)\s+([a-zA-Z_]\w+)', flags=ascii_p3)
43 RE_enum = re.compile(r'\b(enum)\s+([a-zA-Z_]\w+)', flags=ascii_p3)
44 RE_typedef = re.compile(r'\b(typedef)\s+([a-zA-Z_]\w+)', flags=ascii_p3)
[all …]
/Documentation/devicetree/bindings/display/panel/
Dsony,acx424akp.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
9 description: The Sony ACX424AKP and ACX424AKM are panels built around
11 the AKM is configured to use 10 pixels less in the Y axis than the
15 - Linus Walleij <linus.walleij@linaro.org>
18 - $ref: panel-common.yaml#
23 - sony,acx424akp
24 - sony,acx424akm
29 reset-gpios: true
[all …]
/Documentation/hwmon/
Dsysfs-interface.rst1 Naming and data format standards for sysfs files
5 through the sysfs interface. Since lm-sensors 3.0.0, libsensors is
6 completely chip-independent. It assumes that all the kernel drivers
7 implement the standard sysfs interface described in this document.
9 libsensors, and applications using it, do not need to be modified.
10 This is a major improvement compared to lm-sensors 2.
12 Note that motherboards vary widely in the connections to sensor chips.
17 voltages between 0 and +4V. Other voltages are scaled back into that
20 hard coded into the driver and have to be done in user space.
22 For this reason, even if we aim at a chip-independent libsensors, it will
[all …]

12345678910>>...13