| /kernel/linux/linux-5.10/include/linux/pinctrl/ |
| D | pinconf-generic.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
5 * Copyright (C) 2011 ST-Ericsson SA
6 * Written on behalf of Linaro for ST-Ericsson
21 * enum pin_config_param - possible pin configuration parameters
28 * transition from say pull-up to pull-down implies that you disable
29 * pull-up in the process, this setting disables all biasing.
31 * mode, also know as "third-state" (tristate) or "high-Z" or "floating".
36 * @PIN_CONFIG_BIAS_PULL_DOWN: the pin will be pulled down (usually with high
37 * impedance to GROUND). If the argument is != 0 pull-down is enabled,
38 * if it is 0, pull-down is total, i.e. the pin is connected to GROUND.
[all …]
|
| /kernel/linux/linux-6.6/include/linux/pinctrl/ |
| D | pinconf-generic.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
5 * Copyright (C) 2011 ST-Ericsson SA
6 * Written on behalf of Linaro for ST-Ericsson
24 * enum pin_config_param - possible pin configuration parameters
31 * transition from say pull-up to pull-down implies that you disable
32 * pull-up in the process, this setting disables all biasing.
34 * mode, also know as "third-state" (tristate) or "high-Z" or "floating".
39 * @PIN_CONFIG_BIAS_PULL_DOWN: the pin will be pulled down (usually with high
40 * impedance to GROUND). If the argument is != 0 pull-down is enabled,
43 * @PIN_CONFIG_BIAS_PULL_PIN_DEFAULT: the pin will be pulled up or down based
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/sound/ |
| D | everest,es7241.txt | 4 - compatible : "everest,es7241"
5 - VDDP-supply: regulator phandle for the VDDA supply
6 - VDDA-supply: regulator phandle for the VDDP supply
7 - VDDD-supply: regulator phandle for the VDDD supply
10 - reset-gpios: gpio connected to the reset pin
11 - m0-gpios : gpio connected to the m0 pin
12 - m1-gpios : gpio connected to the m1 pin
13 - everest,sdout-pull-down:
15 the sdout. If the sdout is pulled down, leftj format is used.
16 If this property is not provided, sdout is assumed to pulled
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/sound/ |
| D | everest,es7241.txt | 4 - compatible : "everest,es7241"
5 - VDDP-supply: regulator phandle for the VDDA supply
6 - VDDA-supply: regulator phandle for the VDDP supply
7 - VDDD-supply: regulator phandle for the VDDD supply
10 - reset-gpios: gpio connected to the reset pin
11 - m0-gpios : gpio connected to the m0 pin
12 - m1-gpios : gpio connected to the m1 pin
13 - everest,sdout-pull-down:
15 the sdout. If the sdout is pulled down, leftj format is used.
16 If this property is not provided, sdout is assumed to pulled
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/iio/light/ |
| D | veml6030.yaml | 1 # SPDX-License-Identifier: GPL-2.0+
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Rishi Gupta <gupt21@gmail.com>
28 - vishay,veml6030
34 - 0x10 # ADDR pin pulled down
35 - 0x48 # ADDR pin pulled up
40 Refer to interrupt-controller/interrupts.txt for generic
45 - compatible
46 - reg
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/iio/light/ |
| D | veml6030.yaml | 1 # SPDX-License-Identifier: GPL-2.0+
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Rishi Gupta <gupt21@gmail.com>
28 - vishay,veml6030
34 - 0x10 # ADDR pin pulled down
35 - 0x48 # ADDR pin pulled up
40 Refer to interrupt-controller/interrupts.txt for generic
45 - compatible
46 - reg
[all …]
|
| /kernel/linux/linux-6.6/Documentation/process/ |
| D | 7.AdvancedTopics.rst | 12 -------------------------
30 wish to come up to speed with git will find more information at:
32 https://git-scm.com/
34 https://www.kernel.org/pub/software/scm/git/docs/user-manual.html
40 available to others. A git-using developer should be able to obtain a copy
45 remote branches, the index, fast-forward merges, pushes and pulls, detached
50 exercise while coming up to speed.
52 When you are ready to start putting up git trees for others to look at, you
53 will, of course, need a server that can be pulled from. Setting up such a
54 server with git-daemon is relatively straightforward if you have a system
[all …]
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | 7.AdvancedTopics.rst | 12 -------------------------
30 wish to come up to speed with git will find more information at:
32 https://git-scm.com/
34 https://www.kernel.org/pub/software/scm/git/docs/user-manual.html
40 available to others. A git-using developer should be able to obtain a copy
45 remote branches, the index, fast-forward merges, pushes and pulls, detached
50 exercise while coming up to speed.
52 When you are ready to start putting up git trees for others to look at, you
53 will, of course, need a server that can be pulled from. Setting up such a
54 server with git-daemon is relatively straightforward if you have a system
[all …]
|
| /kernel/linux/linux-5.10/arch/powerpc/boot/dts/fsl/ |
| D | p1023rdb.dts | 4 * Copyright 2013 - 2014 Freescale Semiconductor Inc.
37 /include/ "p1023si-pre.dtsi"
42 #address-cells = <2>;
43 #size-cells = <2>;
44 interrupt-parent = <&mpic>;
50 reserved-memory {
51 #address-cells = <2>;
52 #size-cells = <2>;
55 bman_fbpr: bman-fbpr {
59 qman_fqd: qman-fqd {
[all …]
|
| /kernel/linux/linux-6.6/arch/powerpc/boot/dts/fsl/ |
| D | p1023rdb.dts | 4 * Copyright 2013 - 2014 Freescale Semiconductor Inc.
37 /include/ "p1023si-pre.dtsi"
42 #address-cells = <2>;
43 #size-cells = <2>;
44 interrupt-parent = <&mpic>;
50 reserved-memory {
51 #address-cells = <2>;
52 #size-cells = <2>;
55 bman_fbpr: bman-fbpr {
59 qman_fqd: qman-fqd {
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/ |
| D | samsung,sec-core.txt | 1 Binding for Samsung S2M and S5M family multi-function device
4 This is a part of device tree bindings for S2M and S5M family multi-function
8 of multi-function devices which include voltage and current regulators, RTC,
9 charger controller, clock outputs and other sub-blocks. It is interfaced
10 to the host controller using an I2C interface. Each sub-block is usually
14 This document describes bindings for main device node. Optional sub-blocks
15 must be a sub-nodes to it. Bindings for them can be found in:
16 - bindings/regulator/samsung,s2mpa01.txt
17 - bindings/regulator/samsung,s2mps11.txt
18 - bindings/regulator/samsung,s5m8767.txt
[all …]
|
| /kernel/linux/linux-6.6/drivers/net/ethernet/intel/fm10k/ |
| D | fm10k_mbx.c | 1 // SPDX-License-Identifier: GPL-2.0
2 /* Copyright(c) 2013 - 2019 Intel Corporation. */
7 * fm10k_fifo_init - Initialize a message FIFO
10 * @size: maximum message size to store in FIFO, must be 2^n - 1
14 fifo->buffer = buffer; in fm10k_fifo_init()
15 fifo->size = size; in fm10k_fifo_init()
16 fifo->head = 0; in fm10k_fifo_init()
17 fifo->tail = 0; in fm10k_fifo_init()
21 * fm10k_fifo_used - Retrieve used space in FIFO
28 return fifo->tail - fifo->head; in fm10k_fifo_used()
[all …]
|
| /kernel/linux/linux-5.10/drivers/net/ethernet/intel/fm10k/ |
| D | fm10k_mbx.c | 1 // SPDX-License-Identifier: GPL-2.0
2 /* Copyright(c) 2013 - 2019 Intel Corporation. */
7 * fm10k_fifo_init - Initialize a message FIFO
10 * @size: maximum message size to store in FIFO, must be 2^n - 1
14 fifo->buffer = buffer; in fm10k_fifo_init()
15 fifo->size = size; in fm10k_fifo_init()
16 fifo->head = 0; in fm10k_fifo_init()
17 fifo->tail = 0; in fm10k_fifo_init()
21 * fm10k_fifo_used - Retrieve used space in FIFO
28 return fifo->tail - fifo->head; in fm10k_fifo_used()
[all …]
|
| /kernel/linux/linux-5.10/include/linux/mfd/wm8994/ |
| D | pdata.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 * include/linux/mfd/wm8994/pdata.h -- Platform data for WM8994
39 * panel provided by the WISCE - see http://www.wolfsonmicro.com/wisce/
52 * control panel in WISCE - see http://www.wolfsonmicro.com/wisce/
64 * WISCE - see http://www.wolfsonmicro.com/wisce/
78 * multiband compressor configuration panel in WISCE - see
89 * multiband compressor configuration panel in WISCE - see
100 * the multiband compressor configuration panel in WISCE - see
129 * Default values for GPIOs if non-zero, WM8994_CONFIGURE_GPIO
160 /* Power up delays to add after microphone bias power up (ms) */
[all …]
|
| /kernel/linux/linux-6.6/include/linux/mfd/wm8994/ |
| D | pdata.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 * include/linux/mfd/wm8994/pdata.h -- Platform data for WM8994
39 * panel provided by the WISCE - see http://www.wolfsonmicro.com/wisce/
52 * control panel in WISCE - see http://www.wolfsonmicro.com/wisce/
64 * WISCE - see http://www.wolfsonmicro.com/wisce/
78 * multiband compressor configuration panel in WISCE - see
89 * multiband compressor configuration panel in WISCE - see
100 * the multiband compressor configuration panel in WISCE - see
129 * Default values for GPIOs if non-zero, WM8994_CONFIGURE_GPIO
160 /* Power up delays to add after microphone bias power up (ms) */
[all …]
|
| /kernel/linux/linux-6.6/Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 Git source-code management system. Git is a powerful tool with a lot of
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
49 should usually not be changed. Others may have pulled a copy of your
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
62 have pulled changes from another developer's repository, you are now a
67 - Do not reparent a tree without a good reason to do so. Just being on a
[all …]
|
| D | pull-requests.rst | 9 experienced maintainer) primarily from comments made by Greg Kroah-Hartman
20 -------------
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
36 named ``char-misc-next``, you would be using the following command::
38 git tag -s char-misc-4.15-rc1 char-misc-next
40 that will create a signed tag called ``char-misc-4.15-rc1`` based on the
41 last commit in the ``char-misc-next`` branch, and sign it with your gpg key
42 (see Documentation/maintainer/configure-git.rst).
50 any, testing has been done. All of this information will end up in the tag
[all …]
|
| /kernel/linux/linux-6.6/tools/power/pm-graph/config/ |
| D | custom-timeline-functions.cfg | 7 # sudo ./sleepgraph.py -config thisfile.txt
58 output-dir: suspend-{hostname}-{date}-{time}-custom
63 override-timeline-functions: true
68 override-dev-timeline-functions: true
78 # The args are pulled directly from the stack using this architecture's registers
89 # minimum required for an entry, it will show up as the function
143 # The args are pulled directly from the stack using this architecture's registers
154 # minimum required for an entry, it will show up as the function
|
| /kernel/linux/linux-5.10/tools/power/pm-graph/config/ |
| D | custom-timeline-functions.cfg | 7 # sudo ./sleepgraph.py -config thisfile.txt
58 output-dir: suspend-{hostname}-{date}-{time}-custom
63 override-timeline-functions: true
68 override-dev-timeline-functions: true
78 # The args are pulled directly from the stack using this architecture's registers
89 # minimum required for an entry, it will show up as the function
143 # The args are pulled directly from the stack using this architecture's registers
154 # minimum required for an entry, it will show up as the function
|
| /kernel/linux/linux-6.6/Documentation/power/ |
| D | charger-manager.rst | 7 Charger Manager provides in-kernel battery charger management that
8 requires temperature monitoring during suspend-to-RAM state
12 Charger Manager is a platform_driver with power-supply-class entries.
13 An instance of Charger Manager (a platform-device created with Charger-Manager)
26 own power-supply-class and each power-supply-class can provide
28 aggregates charger-related information from multiple sources and
29 shows combined information as a single power-supply-class.
31 * Support for in suspend-to-RAM polling (with suspend_again callback)
32 While the battery is being charged and the system is in suspend-to-RAM,
34 battery temperature. We can accomplish this by waking up the system
[all …]
|
| /kernel/linux/linux-5.10/Documentation/power/ |
| D | charger-manager.rst | 7 Charger Manager provides in-kernel battery charger management that
8 requires temperature monitoring during suspend-to-RAM state
12 Charger Manager is a platform_driver with power-supply-class entries.
13 An instance of Charger Manager (a platform-device created with Charger-Manager)
26 own power-supply-class and each power-supply-class can provide
28 aggregates charger-related information from multiple sources and
29 shows combined information as a single power-supply-class.
31 * Support for in suspend-to-RAM polling (with suspend_again callback)
32 While the battery is being charged and the system is in suspend-to-RAM,
34 battery temperature. We can accomplish this by waking up the system
[all …]
|
| /kernel/linux/linux-5.10/drivers/mtd/maps/ |
| D | scb2_flash.c | 1 // SPDX-License-Identifier: GPL-2.0-only
19 * * A20 and A21 pulled up
20 * * D8-D15 ignored
25 * logical address 0 hit higher-address sections of the chip, not physical 0.
29 * This driver assumes the chip is not write-protected by an external signal.
33 * updates for this board include 10 related (*.bio - &.bi9) binary files and
40 * offset 0x00000 to 0x4ffff (320k): unknown - SCSI BIOS, etc?
76 struct map_info *map = mtd->priv; in scb2_fixup_mtd()
77 struct cfi_private *cfi = map->fldrv_priv; in scb2_fixup_mtd()
80 if (cfi->cfiq->InterfaceDesc != CFI_INTERFACE_X16_ASYNC) { in scb2_fixup_mtd()
[all …]
|
| /kernel/linux/linux-6.6/drivers/mtd/maps/ |
| D | scb2_flash.c | 1 // SPDX-License-Identifier: GPL-2.0-only
19 * * A20 and A21 pulled up
20 * * D8-D15 ignored
25 * logical address 0 hit higher-address sections of the chip, not physical 0.
29 * This driver assumes the chip is not write-protected by an external signal.
33 * updates for this board include 10 related (*.bio - &.bi9) binary files and
40 * offset 0x00000 to 0x4ffff (320k): unknown - SCSI BIOS, etc?
76 struct map_info *map = mtd->priv; in scb2_fixup_mtd()
77 struct cfi_private *cfi = map->fldrv_priv; in scb2_fixup_mtd()
80 if (cfi->cfiq->InterfaceDesc != CFI_INTERFACE_X16_ASYNC) { in scb2_fixup_mtd()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/maintainer/ |
| D | pull-requests.rst | 11 experienced maintainer) primarily from comments made by Greg Kroah-Hartman
22 -------------
36 drivers/char, to be applied at the Kernel version 4.15-rc1 could be named
37 as ``char-misc-4.15-rc1``. If such tag would be produced from a branch
38 named ``char-misc-next``, you would be using the following command::
40 git tag -s char-misc-4.15-rc1 char-misc-next
42 that will create a signed tag called ``char-misc-4.15-rc1`` based on the
43 last commit in the ``char-misc-next`` branch, and sign it with your gpg key
44 (see :ref:`Documentation/maintainer/configure-git.rst <configuregit>`).
52 any, testing has been done. All of this information will end up in the tag
[all …]
|
| D | rebasing-and-merging.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 Git source-code management system. Git is a powerful tool with a lot of
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
49 should usually not be changed. Others may have pulled a copy of your
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
62 have pulled changes from another developer's repository, you are now a
67 - Do not reparent a tree without a good reason to do so. Just being on a
[all …]
|