Home
last modified time | relevance | path

Searched +full:per +full:- +full:string (Results 1 – 25 of 197) sorted by relevance

12345678

/Documentation/networking/
Dmptcp-sysctl.rst1 .. SPDX-License-Identifier: GPL-2.0
10 add_addr_timeout - INTEGER (seconds)
17 The default value matches TCP_RTO_MAX. This is a per-namespace
22 allow_join_initial_addr_port - BOOLEAN
31 This is a per-namespace sysctl.
35 available_schedulers - STRING
39 blackhole_timeout - INTEGER (seconds)
43 MPTCP is re-enabled and will reset to the initial value when the
50 checksum_enabled - BOOLEAN
54 per-namespace sysctl.
[all …]
Dalias.rst1 .. SPDX-License-Identifier: GPL-2.0
4 IP-Aliasing
7 IP-aliases are an obsolete way to manage multiple IP-addresses/masks
8 per interface. Newer tools such as iproute2 support multiple
9 address/prefixes per interface, but aliases are still supported
12 An alias is formed by adding a colon and a string when running ifconfig.
13 This string is usually numeric, but this is not a must.
24 ~~ -> request alias #0 creation (if not yet exists) for eth0
36 ~~~~~~~~~~ -> will delete alias
39 Alias (re-)configuring
/Documentation/devicetree/bindings/usb/
Dbrcm,usb-pinmap.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/usb/brcm,usb-pinmap.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Al Cooper <alcooperx@gmail.com>
15 - const: brcm,usb-pinmap
22 description: Interrupt for signals mirrored to out-gpios.
24 in-gpios:
29 brcm,in-functions:
30 $ref: /schemas/types.yaml#/definitions/string-array
[all …]
/Documentation/netlink/
Dgenetlink-legacy.yaml1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
3 ---
4 $id: http://kernel.org/schemas/netlink/genetlink-legacy.yaml#
5 $schema: https://json-schema.org/draft-07/schema
12 len-or-define:
13 type: [ string, integer ]
14 pattern: ^[0-9A-Za-z_-]+( - 1)?$
16 len-or-limit:
17 # literal int or limit based on fixed-width type e.g. u8-min, u16-max, etc.
18 type: [ string, integer ]
[all …]
Dnetlink-raw.yaml1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
3 ---
4 $id: http://kernel.org/schemas/netlink/netlink-raw.yaml#
5 $schema: https://json-schema.org/draft-07/schema
12 len-or-define:
13 type: [ string, integer ]
14 pattern: ^[0-9A-Za-z_-]+( - 1)?$
21 required: [ name, doc, attribute-sets, operations ]
26 type: string
28 type: string
[all …]
/Documentation/ABI/testing/
Dconfigfs-usb-gadget1 What: /config/usb-gadget
5 This group contains sub-groups corresponding to created
8 What: /config/usb-gadget/gadget
18 to bind a gadget, empty string "" to unbind.
21 names are super-speed-plus, super-speed,
22 high-speed, full-speed, and low-speed.
34 What: /config/usb-gadget/gadget/configs
40 What: /config/usb-gadget/gadget/configs/config
51 What: /config/usb-gadget/gadget/configs/config/strings
55 This group contains subdirectories for language-specific
[all …]
Dconfigfs-usb-gadget-printer1 What: /config/usb-gadget/gadget/functions/printer.name
8 pnp_string Data to be passed to the host in pnp string
9 q_len Number of requests per endpoint
Dsysfs-kernel-irq8 but in a more machine-friendly format. This directory contains
15 Description: The IRQ action chain. A comma-separated list of zero or more
22 Description: Human-readable chip name supplied by the associated device
36 Description: Human-readable flow handler name as defined by the irq chip
44 is a comma-separated list of counters; one per CPU in CPU id
53 Description: The type of the interrupt. Either the string 'level' or 'edge'.
59 Description: The wakeup state of the interrupt. Either the string
/Documentation/core-api/
Dnetlink.rst1 .. SPDX-License-Identifier: BSD-3-Clause
13 ---------------
21 -------------
31 ---------------
44 ----------
51 ------------------------
54 them - make sure to report dump inconsistency with ``NLM_F_DUMP_INTR``.
65 -------
67 kernel-policy
71 operations of the family, defined for each operation individually - ``per-op``,
[all …]
/Documentation/devicetree/bindings/leds/backlight/
Dqcom-wled.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/leds/backlight/qcom-wled.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Bjorn Andersson <andersson@kernel.org>
11 - Kiran Gunda <quic_kgunda@quicinc.com>
21 - qcom,pm8941-wled
22 - qcom,pmi8950-wled
23 - qcom,pmi8994-wled
24 - qcom,pmi8998-wled
[all …]
Dlm3630a-backlight.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/leds/backlight/lm3630a-backlight.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: TI LM3630A High-Efficiency Dual-String White LED
10 - Lee Jones <lee@kernel.org>
11 - Daniel Thompson <daniel.thompson@linaro.org>
12 - Jingoo Han <jingoohan1@gmail.com>
15 The LM3630A is a current-mode boost converter which supplies the power and
16 controls the current in up to two strings of 10 LEDs per string.
[all …]
/Documentation/devicetree/bindings/media/xilinx/
Dxlnx,video.txt2 -------------------------------
5 ---------------
9 and IP core specific documentation, xlnx,v-*.txt, in this directory. The DT
15 - compatible: Must be "xlnx,video".
17 - dmas, dma-names: List of one DMA specifier and identifier string (as defined
18 in Documentation/devicetree/bindings/dma/dma.txt) per port. Each port
19 requires a DMA channel with the identifier string set to "port" followed by
22 - ports: Video port, using the DT bindings defined in ../video-interfaces.txt.
26 - direction: should be either "input" or "output" depending on the direction
34 dma-names = "port0", "port1";
[all …]
/Documentation/netlink/specs/
Dovs_datapath.yaml1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
5 protocol: genetlink-legacy
6 uapi-header: linux/openvswitch.h
12 -
13 name: ovs-header
16 -
17 name: dp-ifindex
19 -
20 name: user-features
22 name-prefix: ovs-dp-f-
[all …]
Dteam.yaml1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
5 protocol: genetlink-legacy
10 c-family-name: team-genl-name
11 c-version-name: team-genl-version
12 kernel-policy: global
13 uapi-header: linux/if_team.h
16 -
17 name: string-max-len
20 -
21 name: genl-change-event-mc-grp-name
[all …]
/Documentation/devicetree/bindings/input/
Drotary-encoder.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/input/rotary-encoder.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Frank Li <Frank.Li@nxp.com>
13 See Documentation/input/devices/rotary-encoder.rst for more information.
17 const: rotary-encoder
28 rotary-encoder,steps:
36 rotary-encoder,relative-axis:
40 absolute one. Relative axis will only generate +1/-1 events on the input
[all …]
/Documentation/devicetree/bindings/hwmon/
Dfan-common.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/hwmon/fan-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Naresh Solanki <naresh.solanki@9elements.com>
11 - Billy Tsai <billy_tsai@aspeedtech.com>
14 max-rpm:
20 min-rpm:
26 pulses-per-revolution:
28 The number of pulse from fan sensor per revolution.
[all …]
/Documentation/devicetree/bindings/display/
Datmel,lcdc-display.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/display/atmel,lcdc-display.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Nicolas Ferre <nicolas.ferre@microchip.com>
11 - Dharma Balasubiramani <dharma.b@microchip.com>
16 input buffer per layer that fetches pixels through the single bus host
17 interface and a look-up table to allow palletized display configurations. The
18 LCDC is programmable on a per layer basis, and supports different LCD
26 - required: [ 'atmel,dmacon' ]
[all …]
/Documentation/trace/
Dboottime-trace.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Boot-time tracing
12 Boot-time tracing allows users to trace boot-time process including
13 device initialization with full features of ftrace including per-event
14 filter and actions, histograms, kprobe-events and synthetic-events,
27 .. [1] See :ref:`Documentation/admin-guide/bootconfig.rst <bootconfig>`
28 .. [2] See :ref:`Documentation/admin-guide/kernel-parameters.rst <kernelparameters>`
31 ---------------------
37 Output trace-event data on printk buffer too.
53 Add fgraph non-tracing function filters.
[all …]
Dkprobetrace.rst2 Kprobe-based Event Tracing
8 --------
9 These events are similar to tracepoint-based events. Instead of tracepoints,
13 Unlike the tracepoint-based event, this can be added and removed
28 -------------------------
34 -:[GRP/][EVENT] : Clear a probe
50 @SYM[+|-offs] : Fetch memory at SYM +|- offs (SYM should be a data symbol)
56 +|-[u]OFFS(FETCHARG) : Fetch memory at FETCHARG +|- OFFS address.(\*3)(\*4)
62 "string", "ustring", "symbol", "symstr" and bitfield are
72 (\*4) "u" means user-space dereference. See :ref:`user_mem_access`.
[all …]
/Documentation/devicetree/bindings/mtd/
Dnvidia-tegra20-nand.txt4 - compatible: Must be one of:
5 - "nvidia,tegra20-nand"
6 - reg: MMIO address range
7 - interrupts: interrupt output of the NFC controller
8 - clocks: Must contain an entry for each entry in clock-names.
9 See ../clocks/clock-bindings.txt for details.
10 - clock-names: Must include the following entries:
11 - nand
12 - resets: Must contain an entry for each entry in reset-names.
14 - reset-names: Must include the following entries:
[all …]
/Documentation/filesystems/nfs/
Dclient-identifier.rst1 .. SPDX-License-Identifier: GPL-2.0
19 ------------
21 The NFSv4 protocol uses "lease-based file locking". Leases help
48 ------------------------
54 - co_ownerid: An arbitrary but fixed string.
56 - boot verifier: A 64-bit incarnation verifier that enables a
70 "co_ownerid" string has several important properties:
72 - The "co_ownerid" string identifies the client during reboot
73 recovery, therefore the string is persistent across client
75 - The "co_ownerid" string helps servers distinguish the client
[all …]
/Documentation/devicetree/bindings/phy/
Dnvidia,tegra194-xusb-padctl.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/phy/nvidia,tegra194-xusb-padctl.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Thierry Reding <thierry.reding@gmail.com>
11 - Jon Hunter <jonathanh@nvidia.com>
21 Some of the lanes are high-speed lanes, which can be used for PCIe, SATA or
22 super-speed USB. Other lanes are for various types of low-speed, full-speed
23 or high-speed USB (such as UTMI, ULPI and HSIC). The XUSB pad controller
24 contains a software-configurable mux that sits between the I/O controller
[all …]
Dnvidia,tegra124-xusb-padctl.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/phy/nvidia,tegra124-xusb-padctl.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Thierry Reding <thierry.reding@gmail.com>
11 - Jon Hunter <jonathanh@nvidia.com>
21 Some of the lanes are high-speed lanes, which can be used for PCIe, SATA or
22 super-speed USB. Other lanes are for various types of low-speed, full-speed
23 or high-speed USB (such as UTMI, ULPI and HSIC). The XUSB pad controller
24 contains a software-configurable mux that sits between the I/O controller
[all …]
/Documentation/devicetree/bindings/pinctrl/
Dberlin,pinctrl.txt1 * Pin-controller driver for the Marvell Berlin SoCs
4 controller register sets. Pin controller nodes should be a sub-node of
9 A pin-controller node should contain subnodes representing the pin group
10 configurations, one per function. Each subnode has the group name and
14 is called a 'function' in the pin-controller subsystem.
17 - compatible: should be one of:
18 "marvell,berlin2-soc-pinctrl",
19 "marvell,berlin2-system-pinctrl",
20 "marvell,berlin2cd-soc-pinctrl",
21 "marvell,berlin2cd-system-pinctrl",
[all …]
/Documentation/devicetree/bindings/net/pse-pd/
Dpse-controller.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/pse-pd/pse-controller.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 power over twisted pair/ethernet cable. The ethernet-pse nodes should be
12 used to describe PSE controller and referenced by the ethernet-phy node.
15 - Oleksij Rempel <o.rempel@pengutronix.de>
16 - Kory Maincent <kory.maincent@bootlin.com>
20 pattern: "^ethernet-pse(@.*|-([0-9]|[1-9][0-9]+))?$"
22 "#pse-cells":
[all …]

12345678