Home
last modified time | relevance | path

Searched refs:json (Results 1 – 21 of 21) sorted by relevance

/Linux-v5.4/Documentation/devicetree/
Dwriting-schema.rst3 Writing DeviceTree Bindings in json-schema
6 Devicetree bindings are written using json-schema vocabulary. Schema files are
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
45 Optional. A json-schema used to match nodes for applying the
81 binding. Each property contains a set of constraints using json-schema
98 The default for arrays in json-schema is they are variable sized and allow more
127 schema for the schema) to ensure they are both valid json-schema and valid
148 json-schema Resources
[all …]
/Linux-v5.4/tools/perf/pmu-events/
DREADME11 - Regular files with '.json' extension in the name are assumed to be
28 the topic. Eg: "Floating-point.json".
34 cache.json memory.json virtual-memory.json
35 frontend.json pipeline.json
46 is derived from JSON file name, 'power8.json').
128 File/path/name.json.
DBuild3 jevents-y += json.o jsmn.o jevents.o
8 find $(JDIR) -name '*.json' -o -name 'mapfile.csv')
Djevents.c229 const char *json; member
250 for (i = 0; table[i].json; i++) { in field_to_perf()
251 if (json_streq(map, val, table[i].json)) in field_to_perf()
/Linux-v5.4/tools/cgroup/
Diocost_monitor.py15 import json
209 table_fmt = not args.json
213 if args.json:
256 output += json.dumps(iocstat.dict(now))
273 output += '\n' + json.dumps(iocg_stat.dict(now, path))
Diocost_coef_gen.py23 import json
103 d = json.loads(f.read())
/Linux-v5.4/tools/testing/selftests/tc-testing/creating-testcases/
DAddingTestCases.txt10 template.json for the required JSON format for test cases.
16 directories named with the -D option) for .json files. Any test case
23 when defining the match pattern. Refer to the supplied json test files
24 for examples when in doubt. The match pattern is written in json, and
26 expression, but should be written using json syntax.
/Linux-v5.4/scripts/
Dgen_compile_commands.py11 import json
142 json.dump(compile_commands, f, indent=2, sort_keys=True)
/Linux-v5.4/tools/bpf/bpftool/Documentation/
Dbpftool.rst22 | { **-j** | **--json** } [{ **-p** | **--pretty** }] }
55 -j, --json
Dbpftool-perf.rst15 *OPTIONS* := { [{ **-j** | **--json** }] [{ **-p** | **--pretty** }] }
49 -j, --json
Dbpftool-feature.rst15 *OPTIONS* := { { **-j** | **--json** } [{ **-p** | **--pretty** }] }
69 -j, --json
Dbpftool-net.rst15 *OPTIONS* := { [{ **-j** | **--json** }] [{ **-p** | **--pretty** }] }
84 -j, --json
Dbpftool-cgroup.rst15 *OPTIONS* := { { **-j** | **--json** } [{ **-p** | **--pretty** }] | { **-f** | **--bpffs** } }
121 -j, --json
Dbpftool-btf.rst15 *OPTIONS* := { { **-j** | **--json** } [{ **-p** | **--pretty** }] }
75 -j, --json
Dbpftool-prog.rst15 *OPTIONS* := { { **-j** | **--json** } [{ **-p** | **--pretty** }] | { **-f** | **--bpffs** } }
194 -j, --json
227 **# bpftool --json --pretty prog show**
Dbpftool-map.rst15 *OPTIONS* := { { **-j** | **--json** } [{ **-p** | **--pretty** }] | { **-f** | **--bpffs** } }
150 -j, --json
/Linux-v5.4/tools/testing/selftests/tc-testing/
Dtdc.py15 import json
436 testlist = json.load(test_data, object_pairs_hook=OrderedDict)
437 except json.JSONDecodeError as jde:
586 json.dump(testlist, outfile, indent=4)
/Linux-v5.4/
D.gitignore148 /compile_commands.json
/Linux-v5.4/tools/testing/selftests/bpf/
Dtest_offload.py20 import json
159 out = json.loads(stdout)
/Linux-v5.4/Documentation/scheduler/
Dsched-deadline.rst740 More interestingly, configurations can be described with a json file that
743 # rt-app my_config.json
747 details (`<rt-app-sources>/doc/*.json`).
/Linux-v5.4/tools/bpf/bpftool/bash-completion/
Dbpftool190 local c='--version --json --pretty --bpffs --mapcompat --debug'