Home
last modified time | relevance | path

Searched full:schema (Results 1 – 25 of 4145) sorted by relevance

12345678910>>...166

/kernel/linux/linux-6.6/Documentation/devicetree/bindings/
Dwriting-schema.rst3 Writing Devicetree Bindings in json-schema
6 Devicetree bindings are written using json-schema vocabulary. Schema files are
11 Also see :ref:`example-schema`.
13 Schema Contents
16 Each schema doc is a structured json-schema which is defined by a set of
18 top-level json-schema properties used are:
21 A json-schema unique identifier string. The string must be a valid
22 URI typically containing the binding's filename and path. For DT schema, it must
24 references to other files specified in schema "$ref" properties. A $ref value
27 components of the current schema file's '$id' value. A URL is used even for
[all …]
Dexample-schema.yaml5 # 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#
29 # 'select' is a schema applied to a DT node to determine if this binding
30 # schema should be applied to the node. It is optional and by default the
33 # In this case, a 'false' schema will never match.
36 # A dictionary of DT properties for this binding schema
38 # More complicated schema can use oneOf (XOR), anyOf (OR), or allOf (AND)
42 # The boolean schema must be a list of schemas.
[all …]
DMakefile4 DT_MK_SCHEMA ?= dt-mk-schema
29 -name 'processed-schema*' \)
43 quiet_cmd_mk_schema = SCHEMA $@
67 $(obj)/processed-schema.json: $(DT_DOCS) $(src)/.yamllint check_dtschema_version FORCE
70 always-y += processed-schema.json
79 dt_compatible_check: $(obj)/processed-schema.json
Dwriting-bindings.rst56 https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/property-units.yaml
72 - Properties without schema types (e.g. without standard suffix or not defined
73 by schema) need the type, even if this is an enum.
75 - If schema includes other schema (e.g. /schemas/i2c/i2c-controller.yaml) use
Dsubmitting-patches.rst22 2) DT binding files are written in DT schema format using json-schema
28 See Documentation/devicetree/bindings/writing-schema.rst for more details
29 about schema and tools setup.
D.gitignore3 /processed-schema*.yaml
4 /processed-schema*.json
/kernel/linux/linux-5.10/Documentation/devicetree/
Dwriting-schema.rst3 Writing DeviceTree Bindings in json-schema
6 Devicetree bindings are written using json-schema vocabulary. Schema files are
11 Schema Contents
14 Each schema doc is a structured json-schema which is defined by a set of
16 top-level json-schema properties used are:
19 A json-schema unique identifier string. The string must be a valid
20 URI typically containing the binding's filename and path. For DT schema, it must
22 references to other files specified in schema "$ref" properties. A $ref value
25 of the current schema file's '$id' value. A URL is used even for local files,
28 $schema
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/
Dexample-schema.yaml5 # 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#
14 title: An example schema annotated with jsonschema details
29 # 'select' is a schema applied to a DT node to determine if this binding
30 # schema should be applied to the node. It is optional and by default the
33 # In this case, a 'false' schema will never match.
36 # A dictionary of DT properties for this binding schema
38 # More complicated schema can use oneOf (XOR), anyOf (OR), or allOf (AND)
[all …]
DMakefile4 DT_MK_SCHEMA ?= dt-mk-schema
23 DT_TMP_SCHEMA := $(obj)/processed-schema-examples.json
26 -name 'processed-schema*' ! \
37 quiet_cmd_mk_schema = SCHEMA $@
58 $(obj)/processed-schema-examples.json: $(DT_DOCS) $(src)/.yamllint check_dtschema_version FORCE
63 # Unless DT_SCHEMA_FILES is specified, use the full schema for dtbs_check too.
64 # Just copy processed-schema-examples.json
66 $(obj)/processed-schema.json: $(obj)/processed-schema-examples.json FORCE
73 # If DT_SCHEMA_FILES is specified, use it for processed-schema.json
75 $(obj)/processed-schema.json: DT_MK_SCHEMA_FLAGS := -u
[all …]
Dsubmitting-patches.rst22 2) DT binding files are written in DT schema format using json-schema
28 See ../writing-schema.rst for more details about schema and tools setup.
D.gitignore3 processed-schema*.yaml
4 processed-schema*.json
/kernel/linux/linux-6.6/tools/net/ynl/
Dcli.py15 parser.add_argument('--schema', dest='schema', type=str)
16 parser.add_argument('--no-schema', action='store_true')
33 args.schema = ''
39 ynl = YnlFamily(args.spec, args.schema)
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/
Dallwinner,sun8i-a23-prcm.yaml5 $schema: http://devicetree.org/meta-schemas/core.yaml#
50 # Already checked in the main schema
84 # Already checked in the main schema
115 # Already checked in the main schema
134 # Already checked in the main schema
Dallwinner,sun6i-a31-prcm.yaml5 $schema: http://devicetree.org/meta-schemas/core.yaml#
48 # Already checked in the main schema
82 # Already checked in the main schema
113 # Already checked in the main schema
146 # Already checked in the main schema
/kernel/linux/linux-6.6/Documentation/userspace-api/netlink/
Dspecs.rst24 This document describes details of the schema.
34 There are four schema levels for Netlink specs, from the simplest used
42 customization of define and enum type and value names; this schema should
45 - ``genetlink-legacy`` - Generic Netlink catch all schema supporting quirks of
47 - ``netlink-raw`` - catch all schema supporting pre-Generic Netlink protocols
53 Schema structure
56 YAML schema has the following conceptual sections:
64 Most properties in the schema accept (or in fact require) a ``doc``
68 schema. See the documentation of :doc:`genetlink-c <c-code-gen>`
97 The schema level, default is ``genetlink``, which is the only value
/kernel/linux/linux-6.6/arch/x86/kernel/cpu/resctrl/
Dctrlmondata.c464 static void show_doms(struct seq_file *s, struct resctrl_schema *schema, int closid) in show_doms() argument
466 struct rdt_resource *r = schema->res; in show_doms()
471 seq_printf(s, "%*s:", max_name_width, schema->name); in show_doms()
480 schema->conf_type); in show_doms()
492 struct resctrl_schema *schema; in rdtgroup_schemata_show() local
500 list_for_each_entry(schema, &resctrl_schema_all, list) { in rdtgroup_schemata_show()
501 seq_printf(s, "%s:uninitialized\n", schema->name); in rdtgroup_schemata_show()
516 list_for_each_entry(schema, &resctrl_schema_all, list) { in rdtgroup_schemata_show()
517 if (closid < schema->num_closid) in rdtgroup_schemata_show()
518 show_doms(s, schema, closid); in rdtgroup_schemata_show()
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/clock/
Dclock-bindings.txt1 This file has moved to the clock binding schema:
2 https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/clock/clock.yaml
/kernel/linux/linux-6.6/Documentation/netlink/
Dgenetlink.yaml5 $schema: https://json-schema.org/draft-07/schema
17 # Schema for specs
34 description: Schema compatibility level. Default is "genetlink".
Dgenetlink-c.yaml5 $schema: https://json-schema.org/draft-07/schema
17 # Schema for specs
34 description: Schema compatibility level. Default is "genetlink".
Dgenetlink-legacy.yaml5 $schema: https://json-schema.org/draft-07/schema
17 # Schema for specs
34 description: Schema compatibility level. Default is "genetlink".
/kernel/linux/linux-6.6/tools/perf/scripts/python/
Dgecko.py199 # And a schema for interpreting each index.
200 # Schema:
209 "schema": {
222 "schema": {
232 "schema": {
248 "schema": {
314 …# Schema: https://github.com/firefox-devtools/profiler/blob/53970305b51b9b472e26d7457fee1d66cd4e27…
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/pci/
Dpci-ep.yaml5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: PCI Endpoint Controller Schema
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/input/
Dinput.yaml5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Common input schema binding
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/memory-controllers/
Dmc-peripheral-props.yaml5 $schema: http://devicetree.org/meta-schemas/core.yaml#
16 should go in their own separate schema that should be referenced
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/reset/
Dallwinner,sun6i-a31-clock-reset.yaml5 $schema: http://devicetree.org/meta-schemas/core.yaml#
25 # PRCM's schema. Make sure we only validate standalone nodes.

12345678910>>...166