child\-node\-with\-own\-schema (full) in projects: linux

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched +full:child +full:- +full:node +full:- +full:with +full:- +full:own +full:- +full:schema (Results 1 – 12 of 12) sorted by relevance

/linux/Documentation/devicetree/bindings/
H A D	example-schema.yaml	1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 4 --- 5 # All the top-level keys are standard json-schema keywords except for 10 $id: http://devicetree.org/schemas/example-schema.yaml# 11 # $schema is the meta-schema this schema should be validated with. 12 $schema: http://devicetree.org/meta-schemas/core.yaml# 17 - Rob Herring <robh@kernel.org> 20 A more detailed multi-line description of the binding. 24 Literal blocks are marked with the '\|' at the beginning. The end is marked by 26 begin with a tab character. [all …]
H A D	writing-bindings.rst	1 .. SPDX-License-Identifier: GPL-2.0 7 This is a list of common review feedback items focused on binding design. With 11 Documentation/devicetree/bindings/submitting-patches.rst 17 - DO attempt to make bindings complete even if a driver doesn't support some 21 - DON'T refer to Linux or "device driver" in bindings. Bindings should be 24 - DO use node names matching the class of the device. Many standard names are 27 - DO check that the example matches the documentation especially after making 30 - DON'T create nodes just for the sake of instantiating drivers. Multi-function 31 devices only need child nodes when the child nodes have their own DT 32 resources. A single node can be multiple providers (e.g. clocks and resets). [all …]
/linux/Documentation/devicetree/bindings/power/
H A D	power-domain.yaml	1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/power/power-domain.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Rafael J. Wysocki <rafael@kernel.org> 11 - Kevin Hilman <khilman@kernel.org> 12 - Ulf Hansson <ulf.hansson@linaro.org> 20 This device tree binding can be used to bind PM domain consumer devices with 22 represented by any node in the device tree and can provide one or more PM 23 domains. A consumer node can refer to the provider by a phandle and a set of [all …]
/linux/Documentation/devicetree/bindings/memory-controllers/
H A D	ti,gpmc-child.yaml	1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/memory-controllers/ti,gpmc-child.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Texas Instruments GPMC Bus Child Nodes 10 - Tony Lindgren <tony@atomide.com> 11 - Roger Quadros <rogerq@kernel.org> 14 This binding is meant for the child nodes of the GPMC node. The node 23 # GPMC Timing properties for child nodes. All are optional and default to 0. 24 gpmc,sync-clk-ps: [all …]
/linux/Documentation/devicetree/bindings/leds/
H A D	common.yaml	`1 # SPDX-License-Identifier: GPL-2.0-only 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Jacek Anaszewski <jacek.anaszewski@gmail.com> 11 - Pavel Machek <pavel@ucw.cz> 15 regulators, but extended with LED and flash LED specific features like 21 have to be tightly coupled with the LED device binding. They are represented 22 by child nodes of the parent LED device binding. 25 led-sources: 30 $ref: /schemas/types.yaml#/definitions/uint32-array [all …]`
/linux/Documentation/devicetree/bindings/media/
H A D	renesas,drif.yaml	1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Renesas R-Car Gen3 Digital Radio Interface Controller (DRIF) 10 - Ramesh Shanmugasundaram <rashanmu@gmail.com> 11 - Fabrizio Castro <fabrizio.castro.jz@renesas.com> 14 R-Car Gen3 DRIF is a SPI like receive only slave device. A general 15 representation of DRIF interfacing with a master device is shown below. 17 +---------------------+ +---------------------+ 18 \| \|-----SCK------->\|CLK \| [all …]
/linux/Documentation/devicetree/bindings/phy/
H A D	nvidia,tegra186-xusb-padctl.yaml	1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/phy/nvidia,tegra186-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> 14 The Tegra XUSB pad controller manages a set of I/O lanes (with differential 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 [all …]
H A D	nvidia,tegra124-xusb-padctl.yaml	1 # 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> 14 The Tegra XUSB pad controller manages a set of I/O lanes (with differential 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 [all …]
H A D	nvidia,tegra194-xusb-padctl.yaml	1 # 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> 14 The Tegra XUSB pad controller manages a set of I/O lanes (with differential 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 [all …]
H A D	nvidia,tegra210-xusb-padctl.yaml	1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/phy/nvidia,tegra210-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> 14 The Tegra XUSB pad controller manages a set of I/O lanes (with differential 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 [all …]
/linux/drivers/gpio/
H A D	gpiolib-of.c	1 // SPDX-License-Identifier: GPL-2.0+ 5 * Copyright (c) 2007-2008 MontaVista Software, Inc. 26 #include "gpiolib-of.h" 29 * This is Linux-specific flags. By default controllers' and Linux' mapping 30 * match, but GPIO controllers are free to translate their own flags to 31 * Linux-specific in their .xlate callback. Though, 1:1 mapping is recommended. 44 * of_gpio_named_count() - Count GPIOs for a device 45 * @np: device node to count GPIOs for 48 * The function returns the count of GPIOs specified for a node. 53 * * %-EINVAL for an incorrectly formed "gpios" property, or [all …]
/linux/kernel/sched/
H A D	core.c	1 // SPDX-License-Identifier: GPL-2.0-only 7 * Copyright (C) 1991-2002 Linus Torvalds 8 * Copyright (C) 1998-2024 Ingo Molnar, Red Hat 73 # include <linux/irq-entry-common.h> 97 #include "../../io_uring/io-wq.h" 106 * associated with them) to allow external modules to probe them. 155 * If SCHED_DEBUG is disabled, each compilation unit has its own copy of 178 * Limited because this is done with IRQs disabled. 191 if (p->sched_class == &stop_sched_class) /* trumps deadline */ in __task_prio() 192 return -2; in __task_prio() [all …]