Home
last modified time | relevance | path

Searched +full:use +full:- +full:push +full:- +full:pull (Results 1 – 23 of 23) sorted by relevance

/Documentation/devicetree/bindings/mfd/
Dst,stmfx.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: STMicroelectonics Multi-Function eXpander (STMFX)
9 description: ST Multi-Function eXpander (STMFX) is a slave controller using I2C for
15 - Amelie Delaunay <amelie.delaunay@foss.st.com>
19 const: st,stmfx-0300
27 drive-open-drain: true
29 vdd-supply: true
36 const: st,stmfx-0300-pinctrl
[all …]
/Documentation/devicetree/bindings/net/
Dsmsc,lan9115.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Smart Mixed-Signal Connectivity (SMSC) LAN911x/912x Controller
10 - Shawn Guo <shawnguo@kernel.org>
13 - $ref: ethernet-controller.yaml#
18 - const: smsc,lan9115
19 - items:
20 - enum:
21 - smsc,lan89218
[all …]
/Documentation/maintainer/
Dpull-requests.rst1 Creating Pull Requests
4 This chapter describes how maintainers can create and submit pull requests
9 experienced maintainer) primarily from comments made by Greg Kroah-Hartman
20 -------------
23 the pull request on a separate branch. Typically you will base this branch
24 off of a branch in the developers tree whom you intend to send the pull
27 In order to create the pull request you must first tag the branch that you
33 Greg offers the following. A pull request with miscellaneous stuff for
34 drivers/char, to be applied at the Kernel version 4.15-rc1 could be named
35 as ``char-misc-4.15-rc1``. If such tag would be produced from a branch
[all …]
Drebasing-and-merging.rst1 .. SPDX-License-Identifier: GPL-2.0
8 Git source-code management system. Git is a powerful tool with a lot of
10 ways to use those features. This document looks in particular at the use
11 of rebasing and merging. Maintainers often get in trouble when they use
30 - Changing the parent (starting) commit upon which a series of patches is
36 - Changing the history of a set of patches by fixing (or deleting) broken
48 - History that has been exposed to the world beyond your private system
54 That said, there are always exceptions. Some trees (linux-next being
61 - Do not rebase a branch that contains history created by others. If you
67 - Do not reparent a tree without a good reason to do so. Just being on a
[all …]
/Documentation/devicetree/bindings/i2c/
Di2c-mt65xx.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/i2c/i2c-mt65xx.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
14 - $ref: /schemas/i2c/i2c-controller.yaml#
17 - Qii Wang <qii.wang@mediatek.com>
22 - const: mediatek,mt2712-i2c
23 - const: mediatek,mt6577-i2c
24 - const: mediatek,mt6589-i2c
25 - const: mediatek,mt7622-i2c
[all …]
/Documentation/devicetree/bindings/pinctrl/
Datmel,at91-pio4-pinctrl.txt7 - compatible:
8 "atmel,sama5d2-pinctrl"
9 "microchip,sama7g5-pinctrl"
10 - reg: base address and length of the PIO controller.
11 - interrupts: interrupt outputs from the controller, one for each bank.
12 - interrupt-controller: mark the device node as an interrupt controller.
13 - #interrupt-cells: should be two.
14 - gpio-controller: mark the device node as a gpio controller.
15 - #gpio-cells: should be two.
17 Please refer to ../gpio/gpio.txt and ../interrupt-controller/interrupts.txt for
[all …]
Dcypress,cy8c95x0.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Patrick Rudolph <patrick.rudolph@9elements.com>
14 Pin function configuration is performed on a per-pin basis.
19 - cypress,cy8c9520
20 - cypress,cy8c9540
21 - cypress,cy8c9560
26 gpio-controller: true
28 '#gpio-cells':
[all …]
Dpincfg-node.yaml1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/pincfg-node.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
14 and generic. Pin control bindings should use the properties defined below
21 bias-disable:
25 bias-high-impedance:
27 description: high impedance mode ("third-state", "floating")
29 bias-bus-hold:
[all …]
Dawinic,aw9523-pinctrl.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/awinic,aw9523-pinctrl.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - AngeloGioacchino Del Regno <angelogioacchino.delregno@somainline.org>
13 The Awinic AW9523/AW9523B I2C GPIO Expander featuring 16 multi-function
18 const: awinic,aw9523-pinctrl
23 '#gpio-cells':
26 include/dt-bindings/gpio/gpio.h
29 gpio-controller: true
[all …]
Dqcom,pmic-gpio.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/qcom,pmic-gpio.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Bjorn Andersson <bjorn.andersson@linaro.org>
19 - enum:
20 - qcom,pm2250-gpio
21 - qcom,pm660-gpio
22 - qcom,pm660l-gpio
23 - qcom,pm6125-gpio
[all …]
/Documentation/process/
D7.AdvancedTopics.rst12 -------------------------
14 The use of distributed version control for the kernel began in early 2002,
27 teach the reader how to use git; that would be sufficient material for a
32 https://git-scm.com/
34 https://www.kernel.org/pub/software/scm/git/docs/user-manual.html
39 understanding of how git works before trying to use it to make patches
40 available to others. A git-using developer should be able to obtain a copy
42 the tree, use branches, etc. An understanding of git's tools for the
45 remote branches, the index, fast-forward merges, pushes and pulls, detached
54 server with git-daemon is relatively straightforward if you have a system
[all …]
/Documentation/devicetree/bindings/gpio/
Dgpio.txt5 -----------------
7 GPIO properties should be named "[<name>-]gpios", with <name> being the purpose
8 of this GPIO for the device. While a non-existent <name> is considered valid
10 for new bindings. Also, GPIO properties named "[<name>-]gpio" are valid and old
11 bindings use it, but are only supported for compatibility reasons and should not
24 and bit-banged data signals:
27 gpio-controller;
28 #gpio-cells = <2>;
32 data-gpios = <&gpio1 12 0>,
44 recommended to use the two-cell approach.
[all …]
/Documentation/driver-api/gpio/
Ddriver.rst19 GPIO chip. The use case is the indicative: certain lines in a system may be
26 between 0 and n-1, n being the number of GPIOs managed by the chip.
29 example if a system uses a memory-mapped set of I/O-registers where 32 GPIO
30 lines are handled by one bit per line in a 32-bit register, it makes sense to
31 use hardware offsets 0..31 for these, corresponding to bits 0..31 in the
44 So for example one platform could use global numbers 32-159 for GPIOs, with a
46 global numbers 0..63 with one set of GPIO controllers, 64-79 with another type
47 of GPIO controller, and on one particular board 80-95 with an FPGA. The legacy
48 numbers need not be contiguous; either of those platforms could also use numbers
49 2000-2063 to identify GPIO lines in a bank of I2C GPIO expanders.
[all …]
/Documentation/devicetree/bindings/leds/
Dnxp,pca963x.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Laurent Pinchart <laurent.pinchart@ideasonboard.com>
13 The NXP PCA963x are I2C-controlled LED drivers optimized for
19 - https://www.nxp.com/docs/en/data-sheet/PCA9632.pdf
20 - https://www.nxp.com/docs/en/data-sheet/PCA9633.pdf
21 - https://www.nxp.com/docs/en/data-sheet/PCA9634.pdf
22 - https://www.nxp.com/docs/en/data-sheet/PCA9635.pdf
27 - nxp,pca9632
[all …]
/Documentation/admin-guide/gpio/
Dgpio-virtuser.rst1 .. SPDX-License-Identifier: GPL-2.0-only
8 consumer devices can be instantiated from device-tree or over configfs.
10 A virtual consumer uses the driver-facing GPIO APIs and allows to cover it with
11 automated tests driven by user-space. The GPIOs are requested using
15 -----------------------
17 The gpio-consumer module registers a configfs subsystem called
18 ``'gpio-virtuser'``. For details of the configfs filesystem, please refer to
25 **Group:** ``/config/gpio-virtuser``
27 This is the top directory of the gpio-consumer configfs tree.
29 **Group:** ``/config/gpio-consumer/example-name``
[all …]
/Documentation/admin-guide/hw-vuln/
Dcore-scheduling.rst1 .. SPDX-License-Identifier: GPL-2.0
15 ----------------
16 A cross-HT attack involves the attacker and victim running on different Hyper
18 full mitigation of cross-HT attacks is to disable Hyper Threading (HT). Core
19 scheduling is a scheduler feature that can mitigate some (not all) cross-HT
21 user-designated trusted group can share a core. This increase in core sharing
27 core involves additional overhead - especially when the system is lightly
29 scheduling to perform more poorly compared to SMT-disabled, where N_CPUS is the
33 -----
35 Using this feature, userspace defines groups of tasks that can be co-scheduled
[all …]
/Documentation/userspace-api/gpio/
Dgpio-get-linehandle-ioctl.rst1 .. SPDX-License-Identifier: GPL-2.0
11 gpio-v2-get-line-ioctl.rst.
16 GPIO_GET_LINEHANDLE_IOCTL - Request a line or lines from the kernel.
51 Requesting a line already in use is an error (**EBUSY**).
55 .. _gpio-get-linehandle-config-rules:
58 -------------------
65 line is requested "as-is" to allow reading of the line value without altering
71 If none are set then the line is assumed push-pull.
80 .. _gpio-get-linehandle-config-support:
83 ---------------------
[all …]
Dgpio-v2-get-line-ioctl.rst1 .. SPDX-License-Identifier: GPL-2.0
12 GPIO_V2_GET_LINE_IOCTL - Request a line or lines from the kernel.
37 :ref:`gpio-v2-line-request`.
41 as possible. e.g. gpio-v2-line-get-values-ioctl.rst will read all the
49 Requesting a line already in use is an error (**EBUSY**).
53 .. _gpio-v2-get-line-config-rules:
56 -------------------
63 and the line is requested "as-is" to allow reading of the line value
69 If none are set then the line is assumed push-pull.
88 applies to both the values returned by gpio-v2-line-get-values-ioctl.rst and
[all …]
/Documentation/gpu/rfc/
Di915_scheduler.rst32 * Convert the i915 to use the DRM scheduler
54 * Remove in-order completion assumptions from DRM scheduler
58 * Pull out i915 priority levels and use DRM priority levels
75 * -1k to -1 Low priority
84 ----------------
86 * https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/chap5.html#devsandqueues-priori…
87 * https://spec.oneapi.com/level-zero/latest/core/api.html#ze-command-queue-priority-t
110 ------------------------------
111 Certain use cases require BBs to be placed on engine instances in logical order
112 (e.g. split-frame on gen11+). The logical mapping of engine instances can change
[all …]
/Documentation/bpf/
Dbpf_devel_QA.rst10 Documentation/process/submitting-patches.rst. This document only describes
21 --------------------------------------------
48 ------------------------------------------------------------------------
49 A: BPF CI is GitHub based and hosted at https://github.com/kernel-patches/bpf.
55 - Create a fork of the aforementioned repository in your own account (one time
58 - Clone the fork locally, check out a new branch tracking either the bpf-next
59 or bpf branch, and apply your to-be-tested patches on top of it
61 - Push the local branch to your fork and create a pull request against
62 kernel-patches/bpf's bpf-next_base or bpf_base branch, respectively
64 Shortly after the pull request has been created, the CI workflow will run. Note
[all …]
/Documentation/driver-api/
Dpin-control.rst9 - Enumerating and naming controllable pins
11 - Multiplexing of pins, pads, fingers (etc) see below for details
13 - Configuration of pins, pads, fingers (etc), such as software-controlled
14 biasing and driving mode specific pins, such as pull-up, pull-down, open drain,
17 Top-level interface
22 - A PIN CONTROLLER is a piece of hardware, usually a set of registers, that
26 - PINS are equal to pads, fingers, balls or whatever packaging input or
30 be sparse - i.e. there may be gaps in the space with numbers where no
60 .. code-block:: c
97 See ``arch/arm/mach-ux500/Kconfig`` for an example.
[all …]
/Documentation/translations/sp_SP/process/
Dmaintainer-kvm-x86.rst1 .. include:: ../disclaimer-sp.rst
3 :Original: Documentation/process/maintainer-kvm-x86.rst
10 --------
21 -----
26 -------
31 x86, ``github.com/kvm-x86/linux.git``.
50 en en camino, y tener que rechazar una solicitud de pull debido a errores
55 decir, cuando se actualiza una rama temática. Como resultado, los push
65 KVM x86. Se envían pull requests (de KVM x86 a KVM main) para cada rama
69 el pull request principal de KVM enviado durante la ventana de fusión de
[all …]
/Documentation/admin-guide/
Dcgroup-v2.rst1 .. _cgroup-v2:
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
26 2-3. [Un]populated Notification
[all …]