Home
last modified time | relevance | path

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

12345678910>>...126

/linux-6.15/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*' \)
48 quiet_cmd_mk_schema = SCHEMA $@
62 $(obj)/processed-schema.json: $(DT_DOCS) check_dtschema_version FORCE
72 always-y += processed-schema.json
81 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
Dincomplete-devices.yaml5 $schema: http://devicetree.org/meta-schemas/core.yaml#
19 Following list of devices is an incomplete schema with a goal to pass DT schema
253 unlikely to get converted to DT schema.
259 unlikely to get converted to DT schema.
Dsubmitting-patches.rst27 2) DT binding files are written in DT schema format using json-schema
33 See Documentation/devicetree/bindings/writing-schema.rst for more details
34 about schema and tools setup.
D.gitignore3 /processed-schema*.yaml
4 /processed-schema*.json
/linux-6.15/tools/testing/selftests/net/lib/py/
Dynl.py32 # Set schema='' to avoid jsonschema validation, it's slow
37 schema='', recv_size=recv_size)
43 schema='', recv_size=recv_size)
48 schema='', recv_size=recv_size)
53 schema='', recv_size=recv_size)
58 schema='', recv_size=recv_size)
/linux-6.15/tools/net/ynl/pyynl/
Dcli.py23 raise Exception(f"Schema directory {schema_dir} does not exist")
62 parser.add_argument('--schema', dest='schema', type=str)
63 parser.add_argument('--no-schema', action='store_true')
106 args.schema = ''
114 if args.schema is None and spec.startswith(sys_schema_dir):
115 args.schema = '' # disable schema validation when installed
121 ynl = YnlFamily(spec, args.schema, args.process_unknown,
/linux-6.15/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>`
92 The schema level, default is ``genetlink``, which is the only value
/linux-6.15/arch/x86/kernel/cpu/resctrl/
Dctrlmondata.c457 static void show_doms(struct seq_file *s, struct resctrl_schema *schema, int closid) in show_doms() argument
459 struct rdt_resource *r = schema->res; in show_doms()
467 seq_printf(s, "%*s:", max_name_width, schema->name); in show_doms()
476 schema->conf_type); in show_doms()
478 seq_printf(s, schema->fmt_str, dom->hdr.id, ctrl_val); in show_doms()
487 struct resctrl_schema *schema; in rdtgroup_schemata_show() local
495 list_for_each_entry(schema, &resctrl_schema_all, list) { in rdtgroup_schemata_show()
496 seq_printf(s, "%s:uninitialized\n", schema->name); in rdtgroup_schemata_show()
511 list_for_each_entry(schema, &resctrl_schema_all, list) { in rdtgroup_schemata_show()
512 if (closid < schema->num_closid) in rdtgroup_schemata_show()
[all …]
/linux-6.15/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
Dallwinner,sun4i-a10-mod0-clk.yaml5 $schema: http://devicetree.org/meta-schemas/core.yaml#
25 # PRCM's schema. Make sure we only validate standalone nodes.
/linux-6.15/Documentation/devicetree/bindings/soc/renesas/
Drenesas-soc.yaml5 $schema: http://devicetree.org/meta-schemas/core.yaml#
66 # schema hits all compatibles that have at lest one Renesas compatible
68 # that don't match the schema select pattern. For example,
/linux-6.15/include/linux/
Dresctrl.h63 * @s: Resctrl schema for the resource to which this
235 * enum resctrl_schema_fmt - The format user-space provides for a schema.
236 * @RESCTRL_SCHEMA_BITMAP: The schema is a bitmap in hex.
237 * @RESCTRL_SCHEMA_RANGE: The schema is a decimal number.
257 * @schema_fmt: Which format string and parser is used for this schema.
294 * @conf_type: Whether this schema is specific to code/data.
296 * the hardware that is configured by this schema.
297 * @num_closid: The number of closid that can be used with this schema. When
/linux-6.15/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…
/linux-6.15/Documentation/netlink/
Dgenetlink.yaml5 $schema: https://json-schema.org/draft-07/schema
23 # Schema for specs
36 description: Schema compatibility level. Default is "genetlink".
Dgenetlink-c.yaml5 $schema: https://json-schema.org/draft-07/schema
23 # Schema for specs
36 description: Schema compatibility level. Default is "genetlink".
/linux-6.15/Documentation/devicetree/bindings/net/
Dlantiq,pef2256.yaml5 $schema: http://devicetree.org/meta-schemas/core.yaml#
93 lantiq,channel-phase = 2, the interleave schema with unused time-slots
98 interleave schema is
102 lantiq,channel-phase = 1, the interleave schema is
/linux-6.15/Documentation/devicetree/bindings/pci/
Dpci-ep-bus.yaml5 $schema: http://devicetree.org/meta-schemas/core.yaml#
15 This common schema is intended to be referenced from device tree bindings and
/linux-6.15/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.
/linux-6.15/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
/linux-6.15/Documentation/devicetree/bindings/interrupt-controller/
Dintel,ce4100-ioapic.yaml5 $schema: http://devicetree.org/meta-schemas/core.yaml#
26 This schema defines bindings for I/O APIC interrupt controller.
/linux-6.15/Documentation/devicetree/bindings/iio/adc/
Dingenic,adc.yaml6 $schema: http://devicetree.org/meta-schemas/core.yaml#
18 https://github.com/devicetree-org/dt-schema/blob/master/schemas/iio/iio-consumer.yaml,
/linux-6.15/Documentation/devicetree/bindings/memory-controllers/ddr/
Djedec,lpddr-props.yaml5 $schema: http://devicetree.org/meta-schemas/core.yaml#
12 reused for each type. Nodes using this schema should generally be nested under

12345678910>>...126