Searched +full:we +full:- +full:on +full:- +full:ns (Results 1 – 25 of 28) sorted by relevance
12
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | ti,gpmc-child.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/memory-controllers/ti,gpmc-child.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Tony Lindgren <tony@atomide.com>
11 - Roger Quadros <rogerq@kernel.org>
24 gpmc,sync-clk-ps:
28 # Chip-select signal timings corresponding to GPMC_CONFIG2:
29 gpmc,cs-on-ns:
33 gpmc,cs-rd-off-ns:
[all …]
|
| D | atmel,ebi.txt | 5 The EBI provides a glue-less interface to asynchronous memories through the SMC
10 - compatible: "atmel,at91sam9260-ebi"
11 "atmel,at91sam9261-ebi"
12 "atmel,at91sam9263-ebi0"
13 "atmel,at91sam9263-ebi1"
14 "atmel,at91sam9rl-ebi"
15 "atmel,at91sam9g45-ebi"
16 "atmel,at91sam9x5-ebi"
17 "atmel,sama5d3-ebi"
18 "microchip,sam9x60-ebi"
[all …]
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-rk3x.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/i2c/i2c-rk3x.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
14 - $ref: /schemas/i2c/i2c-controller.yaml#
17 - Heiko Stuebner <heiko@sntech.de>
23 - const: rockchip,rv1108-i2c
24 - const: rockchip,rk3066-i2c
25 - const: rockchip,rk3188-i2c
26 - const: rockchip,rk3228-i2c
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | amlogic,meson-dwmac.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/net/amlogic,meson-dwmac.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Neil Armstrong <neil.armstrong@linaro.org>
12 - Martin Blumenstingl <martin.blumenstingl@googlemail.com>
14 # We need a select here so we don't match all nodes with 'snps,dwmac'
20 - amlogic,meson6-dwmac
21 - amlogic,meson8b-dwmac
22 - amlogic,meson8m2-dwmac
[all …]
|
| /Documentation/userspace-api/ |
| D | mfd_noexec.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Introduction of non-executable mfd
17 However, in a secure-by-default system, such as ChromeOS, (where all
25 On the other hand, executable memfd has its legit use: runc uses memfd’s
27 execute them. For such a system, we need a solution to differentiate runc's
31 - Let memfd_create() set X bit at creation time.
32 - Let memfd be sealed for modifying X bit when NX is set.
33 - Add a new pid namespace sysctl: vm.memfd_noexec to help applications in
34 migrating and enforcing non-executable MFD.
60 - 0: MEMFD_NOEXEC_SCOPE_EXEC
[all …]
|
| D | landlock.rst | 1 .. SPDX-License-Identifier: GPL-2.0
2 .. Copyright © 2017-2020 Mickaël Salaün <mic@digikod.net>
3 .. Copyright © 2019-2020 ANSSI
4 .. Copyright © 2021-2022 Microsoft Corporation
16 new security layers in addition to the existing system-wide access-controls.
21 We can quickly make sure that Landlock is enabled in the running system by
23 ``dmesg | grep landlock || journalctl -kb -g landlock`` .
26 If Landlock is not currently supported, we need to
32 A Landlock rule describes an action on an object which the process intends to
48 ----------------------------------------
[all …]
|
| /Documentation/devicetree/bindings/i3c/ |
| D | i3c.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Alexandre Belloni <alexandre.belloni@bootlin.com>
11 - Miquel Raynal <miquel.raynal@bootlin.com>
15 and a set of child nodes for each I2C or I3C slave on the bus. Each of them
20 pattern: "^i3c@[0-9a-f]+$"
22 "#address-cells":
31 described in the device tree, which in turn means we have to describe
35 this I3C device has a static I2C address and we want to assign it a
[all …]
|
| /Documentation/filesystems/nfs/ |
| D | localio.rst | 9 server to reliably handshake to determine if they are on the same
26 But unlike the LOCALIO protocol, the sockaddr-based matching didn't
42 - With LOCALIO:
48 - Without LOCALIO:
55 - With LOCALIO:
61 - Without LOCALIO:
72 a. Workloads where the NFS client and server are on the same host
75 running on the same host as the knfsd server being used for
93 deciding if the NFS client and server are co-located on the same
96 Since one of the main use cases is containerised workloads, we cannot
[all …]
|
| D | nfs41-server.rst | 7 by reading this file will contain either "+4.1" or "-4.1"
11 It can be disabled at run time by writing the string "-4.1" to
16 (Warning: older servers will interpret "+4.1" and "-4.1" as "+4" and
17 "-4", respectively. Therefore, code meant to work on both new and old
18 kernels must turn 4.1 on or off *before* turning support for version 4
19 on or off; rpc.nfsd does this correctly.)
22 on RFC 5661.
25 focuses on the mandatory-to-implement NFSv4.1 Sessions, providing
37 - **pNFS** Parallel NFS
38 - **FDELG** File Delegations
[all …]
|
| /Documentation/sound/ |
| D | utimers.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Userspace-driven timers
12 This document describes the userspace-driven timers: virtual ALSA timers
15 stream with timer sources which we don't have ALSA timers exported for
17 two virtual sound devices using ``snd-aloop`` (for instance, when
18 we have a network application sending frames to one snd-aloop device,
19 and another sound application listening on the other end of snd-aloop).
21 Enabling userspace-driven timers
24 The userspace-driven timers could be enabled in the kernel using the
25 ``CONFIG_SND_UTIMER`` configuration option. It depends on the
[all …]
|
| /Documentation/hwmon/ |
| D | smsc47b397.rst | 6 * SMSC LPC47B397-NC
8 * SMSC SCH5307-NS
20 - Mark M. Hoffman <mhoffman@lightlink.com>
21 - Utilitek Systems, Inc.
25 The following specification describes the SMSC LPC47B397-NC [1]_ sensor chip
27 provided by Craig Kelly (In-Store Broadcast Network) and edited/corrected
30 .. [1] And SMSC SCH5307-NS and SCH5317, which have different device IDs but are
33 -------------------------------------------------------------------------
35 Methods for detecting the HP SIO and reading the thermal data on a dc7100
36 -------------------------------------------------------------------------
[all …]
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | arm,mhu.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jassi Brar <jaswinder.singh@linaro.org>
13 The ARM's Message-Handling-Unit (MHU) is a mailbox controller that has 3
15 are hardwired on a platform. A link raises interrupt for any received data.
19 be a 'Secure' resource, hence can't be used by Linux running NS.
22 interrupt signal using a 32-bit register, with all 32-bits logically ORed
28 interrupt. Each of the 32-bits can be used as "doorbell" to alert the remote
31 # We need a select here so we don't match all nodes with 'arm,primecell'
[all …]
|
| /Documentation/kernel-hacking/ |
| D | locking.rst | 17 Linux Kernel, everyone hacking on the kernel needs to know the
37 +------------------------------------+------------------------------------+
41 +------------------------------------+------------------------------------+
43 +------------------------------------+------------------------------------+
45 +------------------------------------+------------------------------------+
47 +------------------------------------+------------------------------------+
49 +------------------------------------+------------------------------------+
51 +------------------------------------+------------------------------------+
57 +------------------------------------+------------------------------------+
61 +------------------------------------+------------------------------------+
[all …]
|
| /Documentation/gpu/ |
| D | i915.rst | 17 ------------------------
19 .. kernel-doc:: drivers/gpu/drm/i915/intel_runtime_pm.c
22 .. kernel-doc:: drivers/gpu/drm/i915/intel_runtime_pm.c
25 .. kernel-doc:: drivers/gpu/drm/i915/intel_uncore.c
29 ------------------
31 .. kernel-doc:: drivers/gpu/drm/i915/i915_irq.c
34 .. kernel-doc:: drivers/gpu/drm/i915/i915_irq.c
37 .. kernel-doc:: drivers/gpu/drm/i915/i915_irq.c
40 .. kernel-doc:: drivers/gpu/drm/i915/i915_irq.c
43 Intel GVT-g Guest Support(vGPU)
[all …]
|
| /Documentation/trace/ |
| D | histogram.rst | 11 aggregate trace event data into histograms. For information on
19 aggregates event hits into a hash table keyed on one or more trace
33 numeric fields - on an event hit, the value(s) will be added to a
35 in place of an explicit value field - this is simply a count of
45 useful for providing more fine-grained summaries of event data.
69 numeric fields are displayed as base-10 integers. This can be
76 .sym-offset display an address as a symbol and offset
83 .graph display a bar-graph of a value
91 - only the 'hex' modifier can be used for values (because values
94 - the 'execname' modifier can only be used on a 'common_pid'. The
[all …]
|
| /Documentation/devicetree/bindings/usb/ |
| D | snps,dwc3.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Felipe Balbi <balbi@kernel.org>
14 be presented as a standalone DT node with an optional vendor-specific
18 - $ref: usb-drd.yaml#
19 - if:
25 - dr_mode
29 $ref: usb-xhci.yaml#
35 - const: snps,dwc3
[all …]
|
| /Documentation/networking/ |
| D | ip-sysctl.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 ip_forward - BOOLEAN
11 - 0 - disabled (default)
12 - not 0 - enabled
20 ip_default_ttl - INTEGER
25 ip_no_pmtu_disc - INTEGER
27 fragmentation-required ICMP is received, the PMTU to this
30 to raise min_pmtu to the smallest interface MTU on your system
35 implicitly setting IP_PMTUDISC_DONT on every created socket.
38 accept fragmentation-needed errors if the underlying protocol
[all …]
|
| D | pktgen.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 Enable CONFIG_NET_PKTGEN to compile and build pktgen either in-kernel
13 On a dual CPU::
31 overload type of benchmarking, as this could hurt the normal use-case.
35 # ethtool -G ethX tx 1024
44 ring-buffers for various performance reasons, and packets stalling
49 and the cleanup interval is affected by the ethtool --coalesce setting
50 of parameter "rx-usecs".
54 # ethtool -C ethX rx-usecs 30
72 * add_device DEVICE@NAME -- adds a single device
[all …]
|
| D | timestamping.rst | 1 .. SPDX-License-Identifier: GPL-2.0
18 based on the architecture type and time_t representation of libc.
27 based on the architecture type and time_t representation of libc.
32 IP_MULTICAST_LOOP + SO_TIMESTAMP[NS]
37 Generates timestamps on reception, transmission or both. Supports
43 -------------------------------------------------------------
45 This socket option enables timestamping of datagrams on the reception
56 on 32 bit machines.
59 -------------------------------------------------------------------
62 Its struct timespec allows for higher resolution (ns) timestamps than the
[all …]
|
| /Documentation/RCU/ |
| D | rcubarrier.rst | 10 struct placed within the RCU-protected data structure and another pointer
16 call_rcu(&p->rcu, p_callback);
30 -------------------------------------
34 If we unload the module while some RCU callbacks are pending,
37 http://lwn.net/images/ns/kernel/rcu-drop.jpg.
39 We could try placing a synchronize_rcu() in the module-exit code path,
43 One might be tempted to try several back-to-back synchronize_rcu()
45 heavy RCU-callback load, then some of the callbacks might be deferred in
52 -------------
61 Pseudo-code using rcu_barrier() is as follows:
[all …]
|
| /Documentation/scheduler/ |
| D | sched-deadline.rst | 12 3. Scheduling Real-Time Tasks
18 4.1 System-wide settings
33 system behavior. As for -rt (group) scheduling, it is assumed that root users
50 ------------------
59 scheduled using EDF[1] on these scheduling deadlines (the task with the
70 with the "traditional" real-time task model (see Section 3) can effectively
76 - Each SCHED_DEADLINE task is characterized by the "runtime",
79 - The state of the task is described by a "scheduling deadline", and
82 - When a SCHED_DEADLINE task wakes up (becomes ready for execution),
86 ---------------------------------- > ---------
[all …]
|
| /Documentation/admin-guide/mm/damon/ |
| D | start.rst | 1 .. SPDX-License-Identifier: GPL-2.0
18 ------
20 You should first ensure your system is running on a kernel built with
25 ---------------
27 For the demonstration, we will use the default user space tool for DAMON,
29 https://github.com/damonitor/damo. The examples below assume that ``damo`` is on
44 $ sudo damo start "./masim ./configs/stairs.cfg --quiet"
51 5 addr [127.649 TiB , 127.649 TiB) (8.000 KiB ) access 60 % age 0 ns
83 $ sudo damo record -o damon.data $(pidof masim)
96 (x-axis) got accessed when (y-axis) and how frequently (number).::
[all …]
|
| /Documentation/scsi/ |
| D | ChangeLog.lpfc | 2 * Please read the associated RELEASE-NOTES file !!!
8 * Fixed build warning for 2.6.12-rc2 kernels: mempool_alloc now
17 to luns on nodes in NPR or other relevant states (PLOGI,
19 * Removed FC_TRANSPORT_PATCHESxxx defines. They're in 2.6.12-rc1.
26 * Added PCI ID for LP10000-S.
27 * Changes in lpfc_abort_handler(): Return SUCCESS if we did not
29 if we timed out waiting for command to complete after abort was
31 * Zero-out response sense length in lpfc_scsi_prep_cmnd to prevent
33 - was causing spurious 0710 messages.
55 - stop using volatile. if you need special ordering use memory
[all …]
|
| /Documentation/arch/m68k/ |
| D | kernel-options.rst | 9 Author: Roman.Hodek@informatik.uni-erlangen.de (Roman Hodek)
11 Update: jds@kom.auc.dk (Jes Sorensen) and faq@linux-m68k.org (Chris Lawrence)
29 The kernel knows three kinds of options on its command line:
58 ----------
65 on it.
76 /dev/ram: -> 0x0100 (initial ramdisk)
77 /dev/hda: -> 0x0300 (first IDE disk)
78 /dev/hdb: -> 0x0340 (second IDE disk)
79 /dev/sda: -> 0x0800 (first SCSI disk)
80 /dev/sdb: -> 0x0810 (second SCSI disk)
[all …]
|
| /Documentation/admin-guide/ |
| D | cgroup-v2.rst | 1 .. _cgroup-v2:
10 This is the authoritative documentation on the design, interface and
11 conventions of cgroup v2. It describes all userland-visible aspects
14 v1 is available under :ref:`Documentation/admin-guide/cgroup-v1/index.rst <cgroup-v1>`.
19 1-1. Terminology
20 1-2. What is cgroup?
22 2-1. Mounting
23 2-2. Organizing Processes and Threads
24 2-2-1. Processes
25 2-2-2. Threads
[all …]
|
12