Home
last modified time | relevance | path

Searched +full:max +full:- +full:functions (Results 1 – 25 of 99) sorted by relevance

1234

/Documentation/devicetree/bindings/pci/
Dpci-ep.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pci/pci-ep.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
13 - Kishon Vijay Abraham I <kishon@kernel.org>
14 - Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
18 pattern: "^pcie-ep@"
20 max-functions:
21 description: Maximum number of functions that can be configured
27 max-virtual-functions:
[all …]
Drcar-pci-ep.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
2 # Copyright (C) 2020 Renesas Electronics Europe GmbH - https://www.renesas.com/eu/en/
4 ---
5 $id: http://devicetree.org/schemas/pci/rcar-pci-ep.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: Renesas R-Car PCIe Endpoint
11 - Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
12 - Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
17 - enum:
18 - renesas,r8a774a1-pcie-ep # RZ/G2M
[all …]
Drcar-gen4-pci-ep.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
2 # Copyright (C) 2022-2023 Renesas Electronics Corp.
4 ---
5 $id: http://devicetree.org/schemas/pci/rcar-gen4-pci-ep.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: Renesas R-Car Gen4 PCIe Endpoint
11 - Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
14 - $ref: snps,dw-pcie-ep.yaml#
19 - enum:
20 - renesas,r8a779f0-pcie-ep # R-Car S4-8
[all …]
Dti,j721e-pci-ep.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
2 # Copyright (C) 2020 Texas Instruments Incorporated - http://www.ti.com/
4 ---
5 $id: http://devicetree.org/schemas/pci/ti,j721e-pci-ep.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Kishon Vijay Abraham I <kishon@ti.com>
16 - const: ti,j721e-pcie-ep
17 - const: ti,j784s4-pcie-ep
18 - description: PCIe EP controller in AM64
20 - const: ti,am64-pcie-ep
[all …]
Dcdns,cdns-pcie-ep.yaml1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/pci/cdns,cdns-pcie-ep.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Tom Joseph <tjoseph@cadence.com>
13 - $ref: cdns-pcie-ep.yaml#
17 const: cdns,cdns-pcie-ep
22 reg-names:
24 - const: reg
25 - const: mem
[all …]
Drockchip,rk3399-pcie-ep.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pci/rockchip,rk3399-pcie-ep.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Shawn Lin <shawn.lin@rock-chips.com>
13 - $ref: /schemas/pci/pci-ep.yaml#
14 - $ref: rockchip,rk3399-pcie-common.yaml#
18 const: rockchip,rk3399-pcie-ep
22 reg-names:
24 - const: apb-base
[all …]
Dsnps,dw-pcie-ep.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/pci/snps,dw-pcie-ep.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jingoo Han <jingoohan1@gmail.com>
11 - Gustavo Pimentel <gustavo.pimentel@synopsys.com>
16 # Please create a separate DT-schema for your DWC PCIe Endpoint controller
17 # and make sure it's assigned with the vendor-specific compatible string.
21 const: snps,dw-pcie-ep
23 - compatible
[all …]
/Documentation/misc-devices/
Dmrvl_cn10k_dpi.rst1 .. SPDX-License-Identifier: GPL-2.0
11 DPI hardware comprises a physical function (PF), its virtual functions,
15 requests from its VF functions and provisions DMA engine resources to
16 it's VF functions.
21 /dev/mrvl-cn10k-dpi node to set DMA engine and PEM (PCIe interface) port
37 ioctl that sets max payload size & max read request size parameters of
42 ioctl that sets DMA engine's fifo sizes & max outstanding load request
49 vfio-pci driver. Below is a sample dpi dma application to demonstrate on
52 https://github.com/MarvellEmbeddedProcessors/dpi-sample-app
/Documentation/devicetree/bindings/mfd/
Dmarvell,88pm886-a1.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mfd/marvell,88pm886-a1.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Karel Balej <balejk@matfyz.cz>
13 Marvell 88PM886 is a PMIC providing several functions such as onkey,
18 const: marvell,88pm886-a1
26 wakeup-source: true
32 "^(ldo(1[0-6]|[1-9])|buck[1-5])$":
39 - compatible
[all …]
Dmotorola-cpcap.txt4 - compatible : One or both of "motorola,cpcap" or "ste,6556002"
5 - reg : SPI chip select
6 - interrupts : The interrupt line the device is connected to
7 - interrupt-controller : Marks the device node as an interrupt controller
8 - #interrupt-cells : The number of cells to describe an IRQ, should be 2
9 - #address-cells : Child device offset number of cells, should be 1
10 - #size-cells : Child device size number of cells, should be 0
11 - spi-max-frequency : Typically set to 3000000
12 - spi-cs-high : SPI chip select direction
16 The sub-functions of CPCAP get their own node with their own compatible values,
[all …]
/Documentation/devicetree/bindings/iio/addac/
Dadi,ad74413r.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Cosmin Tanislav <cosmin.tanislav@analog.com>
13 The AD74412R and AD74413R are quad-channel software configurable input/output
18 The devices feature a 16-bit ADC and four configurable 13-bit DACs to provide
19 four configurable input/output channels and a suite of diagnostic functions.
20 The AD74413R differentiates itself from the AD74412R by being HART-compatible.
27 - adi,ad74412r
28 - adi,ad74413r
[all …]
/Documentation/ABI/testing/
Dconfigfs-usb-gadget-uac11 What: /config/usb-gadget/gadget/functions/uac1.name
9 c_srate list of capture sampling rates (comma-separated)
15 c_volume_max capture volume control max value
20 p_srate list of playback sampling rates (comma-separated)
26 p_volume_max playback volume control max value
30 req_number the number of pre-allocated requests
Dconfigfs-usb-gadget-uac21 What: /config/usb-gadget/gadget/functions/uac2.name
9 c_srate list of capture sampling rates (comma-separated)
11 c_hs_bint capture bInterval for HS/SS (1-4: fixed, 0: auto)
18 c_volume_max capture volume control max value
24 p_srate list of playback sampling rates (comma-separated)
26 p_hs_bint playback bInterval for HS/SS (1-4: fixed, 0: auto)
31 p_volume_max playback volume control max value
35 req_number the number of pre-allocated requests
Dconfigfs-usb-gadget-midi21 What: /config/usb-gadget/gadget/functions/midi2.name
13 What: /config/usb-gadget/gadget/functions/midi2.name/ep.number
33 What: /config/usb-gadget/gadget/functions/midi2.name/ep.number/block.number
45 first_group The first UMP Group number (0-15)
46 num_groups The number of groups in this FB (1-16)
47 midi1_first_group The first UMP Group number for MIDI 1.0 (0-15)
48 midi1_num_groups The number of groups for MIDI 1.0 (0-16)
50 midi_ci_verison Supported MIDI-CI version number (8 bit)
52 sysex8_streams Max number of SysEx8 streams (8 bit)
/Documentation/driver-api/media/
Ddtv-common.rst1 .. SPDX-License-Identifier: GPL-2.0
3 Digital TV Common functions
4 ---------------------------
9 Those functions are responsible for handling the DVB device nodes.
11 .. kernel-doc:: include/media/dvbdev.h
25 .. code-block:: c
34 /* read min. 1000, max. @bufsize: bytes */
48 .. kernel-doc:: include/media/dvb_ringbuffer.h
53 .. kernel-doc:: include/media/dvb_vb2.h
/Documentation/userspace-api/netlink/
Dintro-specs.rst1 .. SPDX-License-Identifier: BSD-3-Clause
21 - ``--spec`` - point to the spec file
22 - ``--do $name`` / ``--dump $name`` - issue request ``$name``
23 - ``--json $attrs`` - provide attributes for the request
24 - ``--subscribe $group`` - receive notifications from ``$group``
30 $ ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/ethtool.yaml \
31 --do rings-get \
32 --json '{"header":{"dev-index": 18}}'
33 {'header': {'dev-index': 18, 'dev-name': 'eni1np1'},
35 'rx-jumbo': 0,
[all …]
/Documentation/devicetree/bindings/sound/
Dst,sta350.txt7 - compatible: "st,sta350"
8 - reg: the I2C address of the device for I2C
9 - reset-gpios: a GPIO spec for the reset pin. If specified, it will be
12 - power-down-gpios: a GPIO spec for the power down pin. If specified,
16 - vdd-dig-supply: regulator spec, providing 3.3V
17 - vdd-pll-supply: regulator spec, providing 3.3V
18 - vcc-supply: regulator spec, providing 5V - 26V
22 - st,output-conf: number, Selects the output configuration:
23 0: 2-channel (full-bridge) power, 2-channel data-out
24 1: 2 (half-bridge). 1 (full-bridge) on-board power
[all …]
/Documentation/devicetree/bindings/regulator/
Dti,tps65219.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jerome Neanne <jerome.neanne@baylibre.com>
18 - ti,tps65219
23 system-power-controller:
29 description: Short-circuit, over-current, under-voltage for regulators, PB interrupts.
32 interrupt-controller: true
34 '#interrupt-cells':
36 include/dt-bindings/interrupt-controller/irq.h
[all …]
/Documentation/core-api/
Drbtree.rst2 Red-black Trees (rbtree) in Linux
9 What are red-black trees, and what are they for?
10 ------------------------------------------------
12 Red-black trees are a type of self-balancing binary search tree, used for
19 Red-black trees are similar to AVL trees, but provide faster real-time bounded
26 There are a number of red-black trees in use in the kernel.
29 The high-resolution timer code uses an rbtree to organize outstanding
31 red-black tree. Virtual memory areas (VMAs) are tracked with red-black
38 Linux Weekly News article on red-black trees
41 Wikipedia entry on red-black trees
[all …]
/Documentation/devicetree/bindings/leds/
Dleds-spi-byte.txt4 - one LED is controlled by a single byte on MOSI
5 - the value of the byte gives the brightness between two values (lowest to
7 - no return value is necessary (no MISO signal)
12 Depending on the compatible string some special functions (like hardware
16 configured in a sub-node in the device node.
19 - compatible: should be one of
20 * "ubnt,acb-spi-led" microcontroller (SONiX 8F26E611LA) based device
23 Property rules described in Documentation/devicetree/bindings/spi/spi-bus.txt
26 LED sub-node properties:
27 - label:
[all …]
/Documentation/devicetree/bindings/power/supply/
Dbq2515x.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: TI bq2515x 500-mA Linear charger family
11 - Andrew Davis <afd@ti.com>
15 integrates the most common functions for wearable devices, namely a charger,
17 push-button controller.
26 - ti,bq25150
27 - ti,bq25155
33 ac-detect-gpios:
[all …]
/Documentation/admin-guide/media/
Dsi4713.rst1 .. SPDX-License-Identifier: GPL-2.0
14 ----------------------------
19 The Si4713 integrates transmit functions for FM broadcast stereo transmission.
29 -------------------------
34 The I2C device driver exports a v4l2-subdev interface to the kernel.
36 using the v4l2-subdev calls (g_ext_ctrls, s_ext_ctrls).
48 ----------------------
51 Here is an output from v4l2-ctl util:
53 .. code-block:: none
55 / # v4l2-ctl -d /dev/radio0 --all -L
[all …]
/Documentation/timers/
Dtimers-howto.rst2 delays - Information on the various kernel delay / sleep mechanisms
14 ----------------
21 You must use the `*delay` family of functions. These
22 functions use the jiffy estimation of clock speed
30 udelay is the generally preferred API; ndelay-level
31 precision may not actually exist on many non-PC devices.
38 NON-ATOMIC CONTEXT:
39 You should use the `*sleep[_range]` family of functions.
45 -- Backed by busy-wait loop:
49 -- Backed by hrtimers:
[all …]
/Documentation/networking/
Dcdc_mbim.rst1 .. SPDX-License-Identifier: GPL-2.0
4 cdc_mbim - Driver for CDC MBIM Mobile Broadband modems
19 behaviour for NCM 1.0 backwards compatible MBIM functions (an
24 -----------
26 :Valid Range: N/Y (0-1)
29 This parameter sets the system policy for NCM/MBIM functions. Such
30 functions will be handled by either the cdc_ncm driver or the cdc_mbim
32 makes the cdc_mbim driver ignore these functions and lets the cdc_ncm
37 functions bound to the "wrong" driver
43 MBIM functions are inactive when unmanaged. The cdc_mbim driver only
[all …]
/Documentation/devicetree/bindings/tpm/
Dgoogle,cr50.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Andrey Pronin <apronin@chromium.org>
15 https://www.osfc.io/2018/talks/google-secure-microcontroller-and-ccd-closed-case-debugging/
17 The chip provides several functions, including TPM 2.0 like functionality.
20 https://trustedcomputinggroup.org/resource/pc-client-platform-tpm-profile-ptp-specification/
27 - $ref: tpm-common.yaml#
30 - $ref: /schemas/spi/spi-peripheral-props.yaml#
31 - $ref: tcg,tpm-tis-i2c.yaml#/properties/reg
[all …]

1234