Searched +full:pre +full:- +full:its (Results 1 – 25 of 115) sorted by relevance
12345
| /Documentation/livepatch/ |
| D | callbacks.rst | 5 Livepatch (un)patch-callbacks provide a mechanism for livepatch modules
10 - Safe updates to global data
12 - "Patches" to init and probe functions
14 - Patching otherwise unpatchable code (i.e. assembly)
25 - Module init/exit code doesn't run when disabling and re-enabling a
28 - A module notifier can't stop a to-be-patched module from loading.
39 * Pre-patch
40 - before a klp_object is patched
42 * Post-patch
43 - after a klp_object has been patched and is active
[all …]
|
| /Documentation/scsi/ |
| D | lpfc.txt | 11 (pre 2.6.10). The 8.0.16 release should be used if the driver is to be
19 The driver now requires a 2.6.12 (if pre-release, 2.6.12-rc1) or later
35 jitter, or a device temporarily loses connectivity (due to its cable
41 errored by the driver, the mid-layer would exhaust its retries, and the
43 re-enable the device.
58 The proposed patch was posted to the linux-scsi mailing list. The patch
59 is contained in the 2.6.10-rc2 (and later) patch kits. As such, this
72 At this time, the driver requires the 2.6.12 (if pre-release, 2.6.12-rc1)
|
| D | ChangeLog.sym53c8xx | 1 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/devicetree/bindings/phy/ |
| D | apm-xgene-phy.txt | 1 * APM X-Gene 15Gbps Multi-purpose PHY nodes
3 PHY nodes are defined to describe on-chip 15Gbps Multi-purpose PHY. Each
4 PHY (pair of lanes) has its own node.
7 - compatible : Shall be "apm,xgene-phy".
8 - reg : PHY memory resource is the SDS PHY access resource.
9 - #phy-cells : Shall be 1 as it expects one argument for setting
14 - status : Shall be "ok" if enabled or "disabled" if disabled.
16 - clocks : Reference to the clock entry.
17 - apm,tx-eye-tuning : Manual control to fine tune the capture of the serial
19 Two set of 3-tuple setting for each (up to 3)
[all …]
|
| /Documentation/devicetree/bindings/ata/ |
| D | sata_highbank.txt | 3 SATA nodes are defined to describe on-chip Serial ATA controllers.
6 Each SATA controller should have its own node.
9 - compatible : compatible list, contains "calxeda,hb-ahci"
10 - interrupts : <interrupt mapping for SATA IRQ>
11 - reg : <registers mapping>
14 - dma-coherent : Present if dma operations are coherent
15 - calxeda,port-phys : phandle-combophy and lane assignment, which maps each
18 - calxeda,sgpio-gpio: phandle-gpio bank, bit offset, and default on or off,
21 - calxeda,led-order : a u32 array that map port numbers to offsets within the
23 - calxeda,tx-atten : a u32 array that contains TX attenuation override
[all …]
|
| /Documentation/networking/ |
| D | framerelay.txt | 3 Data Link Connection Identifier (DLCI) as its hardware address. Usually these
7 Each DLCI is a point-to-point link between your machine and a remote one.
9 net-tools archives is 'dlcicfg'. This program will communicate with the
25 Configuration of the FRAD makes use of another net-tools program, 'fradcfg'.
35 the net-tools distribution. They can be found at ftp.invlogic.com, in
37 use 'cd linux'. v0.10 is for use on pre-2.0.3 and earlier, v0.15 is for
38 pre-2.0.4 and later.
|
| D | vxlan.txt | 17 use of statically-configured forwarding entries.
19 The management of vxlan is done in a manner similar to its two closest
30 the IANA-assigned value of 4789. The Linux implementation of VXLAN
31 pre-dates the IANA's selection of a standard destination port number
32 and uses the Linux-selected value by default to maintain backwards
39 # ip -d link show vxlan0
|
| /Documentation/RCU/Design/Data-Structures/ |
| D | Data-Structures.html | 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
5 <meta HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
16 <li> <a href="#Data-Structure Relationships">
17 Data-Structure Relationships</a>
28 <li> <a href="#RCU-Specific Fields in the task_struct Structure">
29 RCU-Specific Fields in the <tt>task_struct</tt> Structure</a>
34 <h3><a name="Data-Structure Relationships">Data-Structure Relationships</a></h3>
36 <p>RCU is for all intents and purposes a large state machine, and its
55 which results in a three-level <tt>rcu_node</tt> tree.
59 </p><p>The purpose of this combining tree is to allow per-CPU events
[all …]
|
| /Documentation/sound/soc/ |
| D | machine.rst | 12 the following struct:-
24 /* the pre and post PM functions are used to do any PM work before and
33 /* CPU <--> Codec DAI links */
41 ----------------
46 ------------------
47 The machine driver has pre and post versions of suspend and resume to take care
53 -------------------------
62 /* corgi digital audio interface glue - connects codec <--> CPU */
66 .cpu_dai_name = "pxa-is2-dai",
67 .codec_dai_name = "wm8731-hifi",
[all …]
|
| /Documentation/admin-guide/ |
| D | init.rst | 6 Some high-level reasons for failure (listed roughly in order of execution)
23 to be pre-loaded by an initrd)
24 C) Possibly a conflict in ``console= setup`` --> initial console unavailable.
26 missing interrupt-based configuration).
29 ``/lib/ld-linux.so.2`` missing or broken. Use
30 ``readelf -d <INIT>|grep NEEDED`` to find out which libraries are required.
33 In case you tried loading a non-binary file here (shell script?),
34 you should make sure that the script specifies an interpreter in its shebang
35 header line (``#!/...``) that is fully working (including its library
37 non-script binary such as ``/bin/sh`` and confirm its successful execution.
[all …]
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | arm,gic-v3.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/interrupt-controller/arm,gic-v3.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Marc Zyngier <marc.zyngier@arm.com>
15 Software Generated Interrupts (SGI), and Locality-specific Peripheral
19 - $ref: /schemas/interrupt-controller.yaml#
24 - items:
25 - enum:
26 - qcom,msm8996-gic-v3
[all …]
|
| /Documentation/media/v4l-drivers/ |
| D | imx.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 ------------
15 - Image DMA Controller (IDMAC)
16 - Camera Serial Interface (CSI)
17 - Image Converter (IC)
18 - Sensor Multi-FIFO Controller (SMFC)
19 - Image Rotator (IRT)
20 - Video De-Interlacing or Combining Block (VDIC)
26 re-ordering (for example UYVY to YUYV) within the same colorspace, and
27 packed <--> planar conversion. The IDMAC can also perform a simple
[all …]
|
| /Documentation/RCU/Design/Requirements/ |
| D | Requirements.html | 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
5 <meta HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
20 Read-copy update (RCU) is a synchronization mechanism that is often
21 used as a replacement for reader-writer locking.
23 which means that RCU's read-side primitives can be exceedingly fast
33 of as an informal, high-level specification for RCU.
49 <li> <a href="#Fundamental Non-Requirements">Fundamental Non-Requirements</a>
52 <li> <a href="#Quality-of-Implementation Requirements">
53 Quality-of-Implementation Requirements</a>
56 <li> <a href="#Software-Engineering Requirements">
[all …]
|
| /Documentation/media/kapi/ |
| D | dtv-frontend.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 ------------------------
9 The Digital TV Frontend kABI defines a driver-internal interface for
10 registering low-level, hardware specific driver to a hardware independent
29 .name = "foo DVB-T/T2/C driver",
70 .name = "Bar DVB-S/S2 demodulator",
91 /* Satellite-specific */
100 #) For satellite digital TV standards (DVB-S, DVB-S2, ISDB-S), the
128 doesn't fill its field at struct :c:type:`dvb_frontend_ops`, it will default to
129 ``DVBFE_ALGO_SW``, meaning that the dvb-core will do a zigzag when tuning,
[all …]
|
| /Documentation/filesystems/ |
| D | ecryptfs.txt | 22 - David Howells' userspace keyring headers and libraries (version
25 - Libgcrypt
36 MOUNT-WIDE PASSPHRASE
38 Create a new directory into which eCryptfs will write its encrypted
42 mount -t ecryptfs /root/crypt /mnt/crypt
69 mount a directory that has pre-existing files not created by eCryptfs,
|
| D | orangefs.txt | 4 OrangeFS is an LGPL userspace scale-out parallel storage system. It is ideal
58 On Fedora, install orangefs and orangefs-server.
60 dnf -y install orangefs orangefs-server
71 pvfs2-client-core.
75 pvfs2-server -f /etc/orangefs/orangefs.conf
79 systemctl start orangefs-server
83 pvfs2-ping -m /pvfsmnt
88 systemctl start orangefs-client
92 mount -t pvfs2 tcp://localhost:3334/orangefs /pvfsmnt
101 You can omit --prefix if you don't care that things are sprinkled around
[all …]
|
| /Documentation/i2c/ |
| D | i2c-stub.rst | 2 i2c-stub
21 A pointer register with auto-increment is implemented for all byte
33 The typical use-case is like this:
36 2. use i2cset (from the i2c-tools project) to pre-load some data
38 4. observe its behavior in the kernel log
40 There's a script named i2c-stub-from-dump in the i2c-tools package which
|
| /Documentation/devicetree/bindings/mfd/ |
| D | cros-ec.txt | 3 Google's ChromeOS EC is a Cortex-M device which talks to the AP and
8 its own driver which connects to the top level interface-agnostic EC driver.
9 Other Linux driver (such as cros-ec-keyb for the matrix keyboard) connect to
10 the top-level driver.
13 - compatible: "google,cros-ec-i2c"
14 - reg: I2C slave address
17 - compatible: "google,cros-ec-spi"
18 - reg: SPI chip select
21 - compatible: "google,cros-ec-rpmsg"
24 - google,cros-ec-spi-pre-delay: Some implementations of the EC need a little
[all …]
|
| /Documentation/input/ |
| D | gameport-programming.rst | 34 Please also consider enabling the gameport on the card in the ->open()
35 callback if the io is mapped to ISA space - this way it'll occupy the io
37 ->close() callback. You also can select the io address in the ->open()
70 the driver doesn't have to measure them the old way - an ADC is built into
86 return -(mode != GAMEPORT_MODE_COOKED);
97 See analog.c and input.c for handling of fuzz - the fuzz value determines
105 examples 1+2 or 1+3. Gameports can support internal calibration - see below,
107 more than one gameport instance simultaneously, use the ->private member of
144 I/O address for use with raw mode. You have to either set this, or ->read()
179 If the gameport supports cooked mode, it should point this to its cooked
[all …]
|
| /Documentation/RCU/ |
| D | rcubarrier.txt | 5 RCU (read-copy update) is a synchronization mechanism that can be thought
6 of as a replacement for read-writer locking (among other things), but with
7 very low-overhead readers that are immune to deadlock, priority inversion,
8 and unbounded latency. RCU read-side critical sections are delimited
9 by rcu_read_lock() and rcu_read_unlock(), which, in non-CONFIG_PREEMPT
15 pre-existing readers have finished. These old versions are needed because
17 rather expensive, and RCU is thus best suited for read-mostly situations.
22 pre-existing readers have completed. An updater wishing to delete an
30 But the above code cannot be used in IRQ context -- the call_rcu()
32 rcu_head struct placed within the RCU-protected data structure and
[all …]
|
| /Documentation/x86/ |
| D | intel_txt.rst | 6 Technology (Intel(R) TXT), defines platform-level enhancements that
13 - Provides dynamic root of trust for measurement (DRTM)
14 - Data protection in case of improper shutdown
15 - Measurement and verification of launched environment
18 non-vPro systems. It is currently available on desktop systems
30 - LinuxTAG 2008:
31 http://www.linuxtag.org/2008/en/conf/events/vp-donnerstag.html
33 - TRUST2008:
34 http://www.trust-conference.eu/downloads/Keynote-Speakers/
35 3_David-Grawrock_The-Front-Door-of-Trusted-Computing.pdf
[all …]
|
| /Documentation/driver-api/pm/ |
| D | devices.rst | 1 .. SPDX-License-Identifier: GPL-2.0
18 :Copyright: |copy| 2010-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc.
26 management (PM) code is also driver-specific. Most drivers will do very
30 This writeup gives an overview of how drivers interact with system-wide
33 background for the domain-specific work you'd do with any specific driver.
39 Drivers will use one or both of these models to put devices into low-power
44 Drivers can enter low-power states as part of entering system-wide
45 low-power states like "suspend" (also known as "suspend-to-RAM"), or
47 "suspend-to-disk").
50 by implementing various role-specific suspend and resume methods to
[all …]
|
| /Documentation/driver-api/nvdimm/ |
| D | btt.rst | 2 BTT - Block Translation Table
14 using stored energy in capacitors to complete in-flight block writes, or perhaps
15 in firmware. We don't have this luxury with persistent memory - if a write is in
22 device, and reserves a portion of the underlying storage for its metadata. At
23 the heart of it, is an indirection table that re-maps all the blocks on the
35 Each arena follows the same layout for its metadata, and all references in an
37 next arena). The following depicts the "On-disk" metadata layout::
40 Backing Store +-------> Arena
41 +---------------+ | +------------------+
43 | Arena 0 +---+ | 4K |
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-fs-ext4 | 48 will have its blocks allocated out of its own unique
57 algorithm will pre-read into the buffer cache
63 This file is read-only and shows the number of blocks
71 This file is read-only and shows the number of kilobytes
79 This file is read-only and shows the number of
87 Tuning parameter which (if non-zero) controls the goal
117 This file is read-only and shows the pid of journal thread in
118 current pid-namespace or 0 if task is unreachable.
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-io.rst | 2 dm-io
5 Dm-io provides synchronous and asynchronous I/O services. There are three
10 of the I/O. Each io_region indicates a block-device along with the starting
19 Dm-io can read from one io_region or write to one or more io_regions. Writes
38 for the I/O. This service can be handy if the caller has a pre-assembled bio,
65 In the case of an write-I/O to multiple regions, this bitset allows dm-io to
68 Before using any of the dm-io services, the user should call dm_io_get()
70 Dm-io will attempt to resize its mempool to make sure enough pages are
73 When the user is finished using the dm-io services, they should call
|
12345