| /Linux-v5.15/drivers/media/radio/ |
| D | radio-trust.c | 2 /* radio-trust.c - Trust FM Radio card driver for Linux 2.2
30 MODULE_DESCRIPTION("A driver for the Trust FM Radio card.");
47 MODULE_PARM_DESC(io, "I/O addresses of the Trust FM Radio card (0x350 or 0x358)");
51 struct trust { struct
58 struct trust *tr = kzalloc(sizeof(*tr), GFP_KERNEL); in trust_alloc() argument
73 static void write_i2c(struct trust *tr, int n, ...) in write_i2c()
121 struct trust *tr = container_of(isa, struct trust, isa); in trust_s_mute_volume()
131 struct trust *tr = container_of(isa, struct trust, isa); in trust_s_stereo()
149 struct trust *tr = container_of(isa, struct trust, isa); in trust_s_frequency()
166 struct trust *tr = container_of(isa, struct trust, isa); in trust_s_ctrl()
[all …]
|
| D | Kconfig | 426 tristate "Trust FM radio card"
431 This is a driver for the Trust FM radio cards. Say Y if you have
439 module will be called radio-trust.
442 hex "Trust i/o port (usually 0x350 or 0x358)"
446 Enter the I/O port of your Trust FM radio card. If unsure, try the
|
| /Linux-v5.15/Documentation/admin-guide/hw-vuln/ |
| D | core-scheduling.rst | 8 group of tasks don't trust another), or for performance usecases (some
95 mentioned in `Usage`_, tasks with the same cookie value are assumed to trust
120 The scheduler tries its best to find tasks that trust each other such that all
148 Trust model
150 Core scheduling maintains trust relationships amongst groups of tasks by
152 When a system with core scheduling boots, all tasks are considered to trust
154 trust relationships until userspace uses the above mentioned interfaces, to
160 within such groups are considered to trust each other, but do not trust those
161 outside. Tasks outside the group also don't trust tasks within.
186 siblings run tasks which trust each other, when the kernel is executing
[all …]
|
| /Linux-v5.15/Documentation/security/keys/ |
| D | trusted-encrypted.rst | 9 of a Trust Source for greater security, while Encrypted Keys can be used on any
14 Trust Source
17 A trust source provides the source of security for Trusted Keys. This
18 section lists currently supported trust sources, along with their security
19 considerations. Whether or not a trust source is sufficiently safe depends
22 environment is, and there is no metric of trust, it is dependent on the
23 consumer of the Trusted Keys to determine if the trust source is sufficiently
26 * Root of trust for storage
31 provides crypto operation to establish root of trust for storage.
90 New keys are created from random numbers generated in the trust source. They
[all …]
|
| /Linux-v5.15/include/uapi/linux/ |
| D | vbox_vmmdev_types.h | 145 /* Note: trust level is for windows guests only, linux always uses not-given */
146 /* Requestor trust level: Unspecified */
148 /* Requestor trust level: Untrusted (SID S-1-16-0) */
150 /* Requestor trust level: Untrusted (SID S-1-16-4096) */
152 /* Requestor trust level: Medium (SID S-1-16-8192) */
154 /* Requestor trust level: Medium plus (SID S-1-16-8448) */
156 /* Requestor trust level: High (SID S-1-16-12288) */
158 /* Requestor trust level: System (SID S-1-16-16384) */
160 /* Requestor trust level >= Protected (SID S-1-16-20480, S-1-16-28672) */
162 /* Requestor trust level mask */
|
| /Linux-v5.15/Documentation/x86/ |
| D | intel_txt.rst | 13 - Provides dynamic root of trust for measurement (DRTM)
34 http://www.trust-conference.eu/downloads/Keynote-Speakers/
67 To get trust in the initial kernel without using Intel TXT, a
68 static root of trust must be used. This bases trust in BIOS
81 By using the hardware-based root of trust that Intel TXT provides,
83 pre-launch components can be removed from the trust chain, DMA
91 almost all parts of the trust chain is available (excepting SMM and
101 processor instruction that initiates the dynamic root of trust.
|
| /Linux-v5.15/crypto/asymmetric_keys/ |
| D | pkcs7_trust.c | 2 /* Validate the trust chain of a PKCS#7 message.
20 * Check the trust on one PKCS#7 SignedInfo block.
54 * is apparently the same as one we already trust. in pkcs7_validate_trust_one()
135 * pkcs7_validate_trust - Validate PKCS#7 trust chain
140 * keys we already know and trust.
147 * (*) 0 if at least one signature chain intersects with the keys in the trust
|
| /Linux-v5.15/Documentation/process/ |
| D | maintainer-pgp-guide.rst | 47 that trust must always be placed with developers and never with the code
52 want to make sure that by placing trust into developers we do not simply
179 - sign other people's keys for web of trust purposes
526 trust: ultimate validity: ultimate
844 delegated trust technologies, namely DNSSEC and TLS, to get you going if
845 the prospect of starting your own Web of Trust from scratch is too
873 Web of Trust (WOT) vs. Trust on First Use (TOFU)
876 PGP incorporates a trust delegation mechanism known as the "Web of
877 Trust." At its core, this is an attempt to replace the need for
882 Unfortunately, very few people understand how the Web of Trust works.
[all …]
|
| D | management-style.rst | 95 deleting it, you may have irrevocably lost the trust of that
124 we just do both?" and look pitiful. Trust me, it works. If it's not
176 trust somebody who is so clearly hiding their true character.
236 It's part of what makes people trust you, and allow you the potential
|
| /Linux-v5.15/tools/testing/selftests/rcutorture/bin/ |
| D | torture.sh | 342 …bin/kvm.sh --allcpus --duration "$duration_rcutorture" --configs "$configs_rcutorture" --trust-make
348 …ure lock --allcpus --duration "$duration_locktorture" --configs "$configs_locktorture" --trust-make
354 …torture" --configs "$configs_scftorture" --kconfig "CONFIG_NR_CPUS=$HALF_ALLOTED_CPUS" --trust-make
366 … torture.verbose_sleep_frequency=8 torture.verbose_sleep_duration=$VERBOSE_BATCH_CPUS" --trust-make
378 …-torture rcuscale --allcpus --duration 5 --kconfig "CONFIG_NR_CPUS=$HALF_ALLOTED_CPUS" --trust-make
384 …cale --allcpus --duration 10 --kconfig "CONFIG_NR_CPUS=$HALF_ALLOTED_CPUS" --memory 1G --trust-make
390 …allcpus --duration 45s --configs TREE03 --kconfig "CONFIG_TEST_CLOCKSOURCE_WATCHDOG=y" --trust-make
393 …allcpus --duration 45s --configs TREE03 --kconfig "CONFIG_TEST_CLOCKSOURCE_WATCHDOG=y" --trust-make
399 …ools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration 45s --configs TREE03 --trust-make
|
| D | parse-build.sh | 24 if grep -q CC < $F || test -n "$TORTURE_TRUST_MAKE" || grep -qe --trust-make < `dirname $F`/../log
|
| /Linux-v5.15/Documentation/admin-guide/media/ |
| D | gspca-cardlist.rst | 234 nw80x 06a5:d800 Divio Chicony TwinkleCam, Trust SpaceCam
238 sunplus 06d6:0031 Trust 610 LCD PowerC@m Zoom
265 mr97310a 08ca:0110 Trust Spyc@m 100
296 pac7311 093a:2608 Trust WB-3300p
297 pac7311 093a:260e Gigaware VGA PC Camera, Trust WB-3350p, SIGMA cam 2350
410 ov519 0e96:c001 TRUST 380 USB2 SPACEC@M
419 pac207 145f:013a Trust WB-1300N
420 pac7302 145f:013c Trust
421 sn9c20x 145f:013d Trust WB-3600R
437 sq930x 2770:930c Trust WB-3500T / NSG Robbie 2.0
|
| D | zr364xx.rst | 95 0x06d6 0x0034 Trust Powerc@m 750
97 0x06d6 0x003b Trust Powerc@m 970Z
101 0x06d6 0x003d Trust Powerc@m 910Z
|
| D | radio-cardlist.rst | 31 radio-trust Trust FM radio card
|
| /Linux-v5.15/Documentation/admin-guide/namespaces/ |
| D | resource-control.rst | 8 enabled in a kernel for people who don't trust their users or their
14 memory user's they don't trust to play nice can use.
|
| /Linux-v5.15/drivers/net/ipa/ |
| D | ipa.h | 147 * GSI initialization can be done either by Trust Zone on the AP or by the
150 * If it's done by Trust Zone, the AP loads the GSI firmware and supplies
151 * it to Trust Zone to verify and install. When this completes, if
|
| /Linux-v5.15/Documentation/devicetree/bindings/net/ |
| D | qcom,ipa.yaml | 133 the firmware passed to Trust Zone for authentication. Required
134 when Trust Zone (not the modem) performs early initialization.
142 Trust Zone performs early initialization.
|
| /Linux-v5.15/drivers/net/ethernet/netronome/nfp/ |
| D | nfp_net_sriov.c | 157 "trust"); in nfp_app_set_vf_trust()
161 /* Write trust control bit to VF entry in VF config symbol */ in nfp_app_set_vf_trust()
170 "trust"); in nfp_app_set_vf_trust()
|
| /Linux-v5.15/drivers/net/ethernet/mellanox/mlxsw/ |
| D | spectrum_dcb.c | 389 netdev_err(mlxsw_sp_port->dev, "Couldn't switch to trust L2\n"); in mlxsw_sp_port_dcb_app_update()
396 /* A failure to set trust DSCP means that the QPDPM and QPDSM in mlxsw_sp_port_dcb_app_update()
398 * attempting to set trust DSCP, we couldn't have attempted to in mlxsw_sp_port_dcb_app_update()
399 * switch trust to PCP. Thus no cleanup is necessary. in mlxsw_sp_port_dcb_app_update()
401 netdev_err(mlxsw_sp_port->dev, "Couldn't switch to trust L3\n"); in mlxsw_sp_port_dcb_app_update()
|
| /Linux-v5.15/Documentation/translations/it_IT/process/ |
| D | maintainer-pgp-guide.rst | 532 trust: ultimate validity: ultimate
859 Web of Trust (WOT) o Trust on First Use (TOFU)
863 "Web of Trust". Di base, questo è un tentativo di sostituire la necessità
872 alternativo chiamato "Trust on First Use" (TOFU). Potete pensare a TOFU come
885 ``trust-model`` in ``~/.gnupg/gpg.conf``::
887 trust-model tofu+pgp
895 reale -- è progettato così. Dovreste usare il Web of Trust per assicurarvi
898 Come mantenere il Web of Trust va oltre gli scopi di questo documento,
|
| /Linux-v5.15/Documentation/ABI/testing/ |
| D | sysfs-class-cxl | 242 Trust that when an image is reloaded via PERST, it will not
246 0 don't trust, the image may be different (default)
247 1 trust that the image will not change.
|
| /Linux-v5.15/arch/arm/include/asm/ |
| D | compiler.h | 7 * asked it for some inline assembly sequences. Apparently we can't trust
|
| /Linux-v5.15/include/linux/qed/ |
| D | qed_iov_if.h | 31 int (*set_trust) (struct qed_dev *cdev, int vfid, bool trust);
|
| /Linux-v5.15/arch/mips/jazz/ |
| D | reset.c | 5 * We don't trust the firmware so we do it the classic way by poking and
|
| /Linux-v5.15/security/integrity/platform_certs/ |
| D | platform_keyring.c | 23 * Add a key to the platform keyring without checking its trust chain. This
|
