| /kernel/linux/linux-6.6/arch/arm/boot/dts/marvell/ |
| D | armada-385-turris-omnia.dts | 1 // SPDX-License-Identifier: (GPL-2.0 OR MIT)
5 * Copyright (C) 2016 Uwe Kleine-König <uwe@kleine-koenig.org>
8 * Schematic available at https://www.turris.cz/doc/_media/rtrom01-schema.pdf
11 /dts-v1/;
13 #include <dt-bindings/gpio/gpio.h>
14 #include <dt-bindings/input/input.h>
15 #include <dt-bindings/leds/common.h>
16 #include "armada-385.dtsi"
20 compatible = "cznic,turris-omnia", "marvell,armada385", "marvell,armada380";
23 stdout-path = &uart0;
[all …]
|
| /kernel/linux/linux-5.10/Documentation/s390/ |
| D | pci.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 - Pierre Morel
17 -----------------------
25 Ignore the RID field and force use of one PCI domain per PCI function.
28 ---------------
36 - /sys/kernel/debug/s390dbf/pci_msg/sprintf
52 The slot entries are set up using the function identifier (FID) of the
53 PCI function.
55 - /sys/bus/pci/slots/XXXXXXXX/power
57 A physical function that currently supports a virtual function cannot be
[all …]
|
| /kernel/linux/linux-6.6/Documentation/arch/s390/ |
| D | pci.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 - Pierre Morel
17 -----------------------
25 Ignore the RID field and force use of one PCI domain per PCI function.
28 ---------------
36 - /sys/kernel/debug/s390dbf/pci_msg/sprintf
52 The slot entries are set up using the function identifier (FID) of the
53 PCI function. The format depicted as XXXXXXXX above is 8 hexadecimal digits
56 - /sys/bus/pci/slots/XXXXXXXX/power
58 A physical function that currently supports a virtual function cannot be
[all …]
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | xz.h | 5 * Igor Pavlov <https://7-zip.org/>
28 * enum xz_mode - Operation mode
30 * @XZ_SINGLE: Single-call mode. This uses less RAM than
31 * multi-call modes, because the LZMA2
36 * @XZ_PREALLOC: Multi-call mode with preallocated LZMA2
40 * @XZ_DYNALLOC: Multi-call mode. The LZMA2 dictionary is
59 * enum xz_ret - Return codes
62 * return code is possible only in multi-call mode
66 * is still possible in multi-call mode by simply
81 * only in multi-call mode (XZ_PREALLOC or
[all …]
|
| D | cpuhotplug.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
8 * CPU-up CPU-down
15 * BRINGUP_CPU->AP_OFFLINE BRINGUP_CPU <- AP_IDLE_DEAD (idle thread/play_dead)
17 * v (IRQ-off) ,---------------^
19 * | TEARDOWN_CPU <- AP_ONLINE_IDLE
30 * CPU_ONLINE - 1 down to CPUHP_OFFLINE.
52 * for the @state argument of the setup function.
54 * See Documentation/core-api/cpu_hotplug.rst for further information and
58 CPUHP_INVALID = -1,
276 * cpuhp_setup_state - Setup hotplug state callbacks with calling the @startup
[all …]
|
| /kernel/liteos_a/kernel/ |
| D | Kconfig | 9 int "Multi-processing Core Numbers"
13 This represents the number of multi-processing cores.
30 bool "Enable Function call cross Multi-core"
34 This option will enable function call on multi-core.
|
| /kernel/linux/linux-6.6/arch/powerpc/boot/dts/ |
| D | turris1x.dts | 1 // SPDX-License-Identifier: GPL-2.0+
5 * Copyright 2013 - 2022 CZ.NIC z.s.p.o. (http://www.nic.cz/)
8 * and available at: https://docs.turris.cz/hw/turris-1x/turris-1x/
11 #include <dt-bindings/gpio/gpio.h>
12 #include <dt-bindings/interrupt-controller/irq.h>
13 #include <dt-bindings/leds/common.h>
14 /include/ "fsl/p2020si-pre.dtsi"
41 gpio-controller@18 {
45 #gpio-cells = <2>;
46 gpio-controller;
[all …]
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| D | xarray.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
15 next or previous entry in a cache-efficient manner. In contrast to a
17 order to grow the array. It is more memory-efficient, parallelisable
18 and cache friendly than a doubly-linked list. It takes advantage of
28 Normal pointers may be stored in the XArray directly. They must be 4-byte
30 alloc_page(). It isn't true for arbitrary user-space pointers,
31 nor for function pointers. You can store pointers to statically allocated
54 the range. Storing to any index will store to all of them. Multi-index
63 allocated ones. A freshly-initialised XArray contains a ``NULL``
82 returns ``-EBUSY`` if the entry is not empty.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/core-api/ |
| D | xarray.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
15 next or previous entry in a cache-efficient manner. In contrast to a
17 order to grow the array. It is more memory-efficient, parallelisable
18 and cache friendly than a doubly-linked list. It takes advantage of
28 Normal pointers may be stored in the XArray directly. They must be 4-byte
30 alloc_page(). It isn't true for arbitrary user-space pointers,
31 nor for function pointers. You can store pointers to statically allocated
54 the range. Storing to any index will store to all of them. Multi-index
63 allocated ones. A freshly-initialised XArray contains a ``NULL``
82 returns ``-EBUSY`` if the entry is not empty.
[all …]
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | cpuhotplug.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
8 * CPU-up CPU-down
15 * BRINGUP_CPU->AP_OFFLINE BRINGUP_CPU <- AP_IDLE_DEAD (idle thread/play_dead)
17 * v (IRQ-off) ,---------------^
19 * | TEARDOWN_CPU <- AP_ONLINE_IDLE
26 CPUHP_INVALID = -1,
216 * cpuhp_setup_state - Setup hotplug state callbacks with calling the callbacks
219 * @startup: startup callback function
220 * @teardown: teardown callback function
243 * cpuhp_setup_state_nocalls - Setup hotplug state callbacks without calling the
[all …]
|
| D | xz.h | 5 * Igor Pavlov <https://7-zip.org/>
28 * enum xz_mode - Operation mode
30 * @XZ_SINGLE: Single-call mode. This uses less RAM than
31 * multi-call modes, because the LZMA2
36 * @XZ_PREALLOC: Multi-call mode with preallocated LZMA2
40 * @XZ_DYNALLOC: Multi-call mode. The LZMA2 dictionary is
59 * enum xz_ret - Return codes
62 * return code is possible only in multi-call mode
66 * is still possible in multi-call mode by simply
81 * only in multi-call mode (XZ_PREALLOC or
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/leds/ |
| D | cznic,turris-omnia-leds.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/leds/cznic,turris-omnia-leds.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Marek Behún <marek.behun@nic.cz>
20 const: cznic,turris-omnia-leds
26 "#address-cells":
29 "#size-cells":
33 "^multi-led@[0-9a-b]$":
36 - $ref: leds-class-multicolor.yaml#
[all …]
|
| D | leds-lp50xx.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/leds/leds-lp50xx.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Dan Murphy <dmurphy@ti.com>
13 The LP50XX is multi-channel, I2C RGB LED Drivers that can group RGB LEDs into
27 - ti,lp5009
28 - ti,lp5012
29 - ti,lp5018
30 - ti,lp5024
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/leds/ |
| D | cznic,turris-omnia-leds.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/leds/cznic,turris-omnia-leds.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Marek Behún <kabel@kernel.org>
20 const: cznic,turris-omnia-leds
26 "#address-cells":
29 "#size-cells":
33 "^multi-led@[0-9a-b]$":
35 $ref: leds-class-multicolor.yaml#
[all …]
|
| D | leds-lp50xx.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/leds/leds-lp50xx.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Andrew Davis <afd@ti.com>
13 The LP50XX is multi-channel, I2C RGB LED Drivers that can group RGB LEDs into
27 - ti,lp5009
28 - ti,lp5012
29 - ti,lp5018
30 - ti,lp5024
[all …]
|
| /kernel/linux/linux-5.10/Documentation/networking/device_drivers/ethernet/neterion/ |
| D | vxge.rst | 1 .. SPDX-License-Identifier: GPL-2.0
23 - Single function mode
24 - Multi function mode
25 - SRIOV mode
26 - MRIOV mode
28 The functions share a 10GbE link and the pci-e bus, but hardly anything else
31 supported independently on each function.
38 i) Single function mode (up to 17 queues)
40 ii) Multi function mode (up to 17 functions)
42 iii) PCI-SIG's I/O Virtualization
[all …]
|
| /kernel/linux/linux-6.6/fs/ntfs/ |
| D | mst.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * mst.c - NTFS multi sector transfer protection handling code. Part of the
4 * Linux-NTFS project.
6 * Copyright (c) 2001-2004 Anton Altaparmakov
12 * post_read_mst_fixup - deprotect multi sector transfer protected data
16 * Perform the necessary post read multi sector transfer fixup and detect the
17 * presence of incomplete multi sector transfers. - In that case, overwrite the
21 * Return 0 on success and -EINVAL on error ("BAAD" magic will be present).
34 usa_ofs = le16_to_cpu(b->usa_ofs); in post_read_mst_fixup()
36 usa_count = le16_to_cpu(b->usa_count) - 1; in post_read_mst_fixup()
[all …]
|
| /kernel/linux/linux-5.10/fs/ntfs/ |
| D | mst.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * mst.c - NTFS multi sector transfer protection handling code. Part of the
4 * Linux-NTFS project.
6 * Copyright (c) 2001-2004 Anton Altaparmakov
12 * post_read_mst_fixup - deprotect multi sector transfer protected data
16 * Perform the necessary post read multi sector transfer fixup and detect the
17 * presence of incomplete multi sector transfers. - In that case, overwrite the
21 * Return 0 on success and -EINVAL on error ("BAAD" magic will be present).
34 usa_ofs = le16_to_cpu(b->usa_ofs); in post_read_mst_fixup()
36 usa_count = le16_to_cpu(b->usa_count) - 1; in post_read_mst_fixup()
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/mfd/ |
| D | retu.txt | 1 * Device tree bindings for Nokia Retu and Tahvo multi-function device
3 Retu and Tahvo are a multi-function devices found on Nokia Internet
9 - compatible: "nokia,retu" or "nokia,tahvo"
10 - reg: Specifies the CBUS slave address of the ASIC chip
11 - interrupts: The interrupt line the device is connected to
16 compatible = "i2c-cbus-gpio";
20 interrupt-parent = <&gpio4>;
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/ |
| D | retu.txt | 1 * Device tree bindings for Nokia Retu and Tahvo multi-function device
3 Retu and Tahvo are a multi-function devices found on Nokia Internet
9 - compatible: "nokia,retu" or "nokia,tahvo"
10 - reg: Specifies the CBUS slave address of the ASIC chip
11 - interrupts: The interrupt line the device is connected to
16 compatible = "i2c-cbus-gpio";
20 interrupt-parent = <&gpio4>;
|
| 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-5.10/drivers/isdn/hardware/mISDN/ |
| D | hfc_multi_8xx.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
20 const char *function, int line) in HFC_outb_embsd() argument
25 hc->immap->im_ioport.iop_padat |= PA_XHFC_A0; in HFC_outb_embsd()
26 writeb(reg, hc->xhfc_memaddr); in HFC_outb_embsd()
27 hc->immap->im_ioport.iop_padat &= ~(PA_XHFC_A0); in HFC_outb_embsd()
28 writeb(val, hc->xhfc_memdata); in HFC_outb_embsd()
32 HFC_inb_embsd(struct hfc_multi *hc, u_char reg, const char *function, int line) in HFC_inb_embsd() argument
37 hc->immap->im_ioport.iop_padat |= PA_XHFC_A0; in HFC_inb_embsd()
38 writeb(reg, hc->xhfc_memaddr); in HFC_inb_embsd()
39 hc->immap->im_ioport.iop_padat &= ~(PA_XHFC_A0); in HFC_inb_embsd()
[all …]
|
| /kernel/linux/linux-6.6/drivers/isdn/hardware/mISDN/ |
| D | hfc_multi_8xx.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
20 const char *function, int line) in HFC_outb_embsd() argument
25 hc->immap->im_ioport.iop_padat |= PA_XHFC_A0; in HFC_outb_embsd()
26 writeb(reg, hc->xhfc_memaddr); in HFC_outb_embsd()
27 hc->immap->im_ioport.iop_padat &= ~(PA_XHFC_A0); in HFC_outb_embsd()
28 writeb(val, hc->xhfc_memdata); in HFC_outb_embsd()
32 HFC_inb_embsd(struct hfc_multi *hc, u_char reg, const char *function, int line) in HFC_inb_embsd() argument
37 hc->immap->im_ioport.iop_padat |= PA_XHFC_A0; in HFC_inb_embsd()
38 writeb(reg, hc->xhfc_memaddr); in HFC_inb_embsd()
39 hc->immap->im_ioport.iop_padat &= ~(PA_XHFC_A0); in HFC_inb_embsd()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pinctrl/ |
| D | atmel,at91-pinctrl.txt | 10 Please refer to pinctrl-bindings.txt in this directory for details of the
15 used for a specific device or function. This node represents both mux and config
16 of the pins in that group. The 'pins' selects the function mode(also named pin
18 such as pull-up, multi drive, etc.
21 - compatible: "atmel,at91rm9200-pinctrl" or "atmel,at91sam9x5-pinctrl"
22 or "atmel,sama5d3-pinctrl" or "microchip,sam9x60-pinctrl"
23 - atmel,mux-mask: array of mask (periph per bank) to describe if a pin can be
45 From the datasheet Table 10-2.
83 - atmel,pins: 4 integers array, represents a group of pins mux and config
90 MULTIDRIVE (1 << 1): indicate this pin needs to be configured as multi-drive.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/pinctrl/ |
| D | atmel,at91-pinctrl.txt | 10 Please refer to pinctrl-bindings.txt in this directory for details of the
15 used for a specific device or function. This node represents both mux and config
16 of the pins in that group. The 'pins' selects the function mode(also named pin
18 such as pull-up, multi drive, etc.
21 - compatible: "atmel,at91rm9200-pinctrl" or "atmel,at91sam9x5-pinctrl"
22 or "atmel,sama5d3-pinctrl" or "microchip,sam9x60-pinctrl"
23 - atmel,mux-mask: array of mask (periph per bank) to describe if a pin can be
45 From the datasheet Table 10-2.
83 - atmel,pins: 4 integers array, represents a group of pins mux and config
90 MULTIDRIVE (1 << 1): indicate this pin needs to be configured as multi-drive.
[all …]
|