Home
last modified time | relevance | path

Searched full:trust (Results 1 – 25 of 440) sorted by relevance

12345678910>>...18

/Linux-v6.6/drivers/media/radio/
Dradio-trust.c2 /* 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 …]
DKconfig426 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-v6.6/Documentation/admin-guide/hw-vuln/
Dcore-scheduling.rst8 group of tasks don't trust another), or for performance usecases (some
96 mentioned in `Usage`_, tasks with the same cookie value are assumed to trust
121 The scheduler tries its best to find tasks that trust each other such that all
149 Trust model
151 Core scheduling maintains trust relationships amongst groups of tasks by
153 When a system with core scheduling boots, all tasks are considered to trust
155 trust relationships until userspace uses the above mentioned interfaces, to
161 within such groups are considered to trust each other, but do not trust those
162 outside. Tasks outside the group also don't trust tasks within.
187 siblings run tasks which trust each other, when the kernel is executing
[all …]
/Linux-v6.6/Documentation/security/keys/
Dtrusted-encrypted.rst9 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.
41 mode, trust is rooted to the OTPMK, a never-disclosed 256-bit key
[all …]
/Linux-v6.6/include/uapi/linux/
Dvbox_vmmdev_types.h145 /* 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-v6.6/Documentation/arch/x86/
Dintel_txt.rst13 - 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.
Dtdx.rst4 Intel Trust Domain Extensions (TDX)
7 Intel's Trust Domain Extensions (TDX) protect confidential guest VMs from
175 will expose the register state to the host. TDX guests don't trust the host
261 https://www.intel.com/content/www/us/en/developer/articles/technical/intel-trust-domain-extensions.…
/Linux-v6.6/crypto/asymmetric_keys/
Dpkcs7_trust.c2 /* 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-v6.6/drivers/net/ethernet/microchip/sparx5/
Dsparx5_dcb.c111 /* Requested trust configuration is not supported */ in sparx5_dcb_apptrust_validate()
318 const struct sparx5_dcb_apptrust *trust; in sparx5_dcb_getapptrust() local
320 trust = sparx5_port_apptrust[port->portno]; in sparx5_dcb_getapptrust()
322 memcpy(selectors, trust->selectors, trust->nselectors); in sparx5_dcb_getapptrust()
323 *nselectors = trust->nselectors; in sparx5_dcb_getapptrust()
394 /* Initialize [dscp, pcp] default trust */ in sparx5_dcb_init()
/Linux-v6.6/Documentation/admin-guide/media/
Dgspca-cardlist.rst234 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
Dradio-cardlist.rst31 radio-trust Trust FM radio card
/Linux-v6.6/Documentation/process/
Dmaintainer-pgp-guide.rst47 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
160 - sign other people's keys for web of trust purposes
485 trust: ultimate validity: ultimate
848 delegated trust technologies, namely DNSSEC and TLS, to get you going if
849 the prospect of starting your own Web of Trust from scratch is too
877 Web of Trust (WOT) vs. Trust on First Use (TOFU)
880 PGP incorporates a trust delegation mechanism known as the "Web of
881 Trust." At its core, this is an attempt to replace the need for
886 Unfortunately, very few people understand how the Web of Trust works.
[all …]
Dmanagement-style.rst95 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-v6.6/tools/testing/selftests/rcutorture/bin/
Dtorture.sh394 …RCU_EXPERT=y CONFIG_RCU_SCALE_TEST=y $forceflavor=y $deselectedflavors" --trust-make > $T/$flavor.…
416 …bin/kvm.sh --allcpus --duration "$duration_rcutorture" --configs "$configs_rcutorture" --trust-make
422 …ure lock --allcpus --duration "$duration_locktorture" --configs "$configs_locktorture" --trust-make
430 …$configs_scftorture" --kconfig "CONFIG_NR_CPUS=$HALF_ALLOTED_CPUS" --memory ${scfmem}G --trust-make
437 …s/rcutorture/bin/kvm.sh --allcpus --duration "$duration_rcutorture" --configs "TREE03" --trust-make
441 …s/rcutorture/bin/kvm.sh --allcpus --duration "$duration_rcutorture" --configs "TREE03" --trust-make
475 … torture.verbose_sleep_frequency=8 torture.verbose_sleep_duration=$VERBOSE_BATCH_CPUS" --trust-make
524 …us --duration 5 --kconfig "CONFIG_TASKS_TRACE_RCU=y CONFIG_NR_CPUS=$HALF_ALLOTED_CPUS" --trust-make
562 …cale --allcpus --duration 10 --kconfig "CONFIG_NR_CPUS=$HALF_ALLOTED_CPUS" --memory 2G --trust-make
568 …allcpus --duration 45s --configs TREE03 --kconfig "CONFIG_TEST_CLOCKSOURCE_WATCHDOG=y" --trust-make
[all …]
/Linux-v6.6/drivers/net/ethernet/microchip/lan966x/
Dlan966x_dcb.c277 const struct lan966x_dcb_apptrust *trust; in lan966x_dcb_getapptrust() local
279 trust = lan966x_port_apptrust[port->chip_port]; in lan966x_dcb_getapptrust()
281 memcpy(selectors, trust->selectors, trust->nselectors); in lan966x_dcb_getapptrust()
282 *nselectors = trust->nselectors; in lan966x_dcb_getapptrust()
/Linux-v6.6/Documentation/admin-guide/namespaces/
Dresource-control.rst8 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-v6.6/drivers/net/ethernet/netronome/nfp/nic/
Ddcb.c162 /* We only refresh dscp in dscp trust mode. */ in update_dscp_maxrate()
178 u8 trust; in nfp_nic_set_trust() local
185 trust = dcb->dscp_cnt > 0 ? NFP_DCB_TRUST_DSCP : NFP_DCB_TRUST_PCP; in nfp_nic_set_trust()
186 writeb(trust, dcb->dcbcfg_tbl + dcb->cfg_offset + in nfp_nic_set_trust()
189 dcb->trust_status = trust; in nfp_nic_set_trust()
449 /* Check trust status */ in nfp_nic_dcbnl_ieee_setapp()
506 /* If no dscp mapping is configured, trust pcp */ in nfp_nic_dcbnl_ieee_delapp()
/Linux-v6.6/Documentation/devicetree/bindings/nvmem/
Dfsl,layerscape-sfp.yaml22 - description: Trust architecture 2.1 SFP
25 - description: Trust architecture 3.0 SFP
/Linux-v6.6/drivers/hv/
DKconfig26 VSM achieves and maintains isolation through Virtual Trust Levels
27 (VTLs). Virtual Trust Levels are hierarchical, with higher levels
/Linux-v6.6/security/integrity/platform_certs/
Dmachine_keyring.c47 * Try to load the MokListTrustedRT MOK variable to see if we should trust
82 * on .machine keyring. UEFI systems enable this trust based on a variable,
/Linux-v6.6/Documentation/devicetree/bindings/remoteproc/
Dst,stm32-rproc.yaml49 Reference to the system configuration which holds the RCC trust zone mode
54 - description: The offset of the trust zone setting register
55 - description: The field mask of the trust zone state
/Linux-v6.6/drivers/net/ipa/
Dipa.h159 * GSI initialization can be done either by Trust Zone on the AP or by the
162 * If it's done by Trust Zone, the AP loads the GSI firmware and supplies
163 * it to Trust Zone to verify and install. When this completes, if
/Linux-v6.6/Documentation/maintainer/
Dfeature-and-driver-maintainers.rst116 list or a group email as a maintainer. Trust and understanding are the
117 foundation of kernel maintenance and one cannot build trust with a mailing
126 together by (rarely expressed) mutual respect, trust and convenience.
/Linux-v6.6/drivers/net/ethernet/netronome/nfp/
Dnfp_net_sriov.c210 "trust", true); in nfp_app_set_vf_trust()
214 /* Write trust control bit to VF entry in VF config symbol */ in nfp_app_set_vf_trust()
223 "trust"); in nfp_app_set_vf_trust()
/Linux-v6.6/include/linux/pds/
Dpds_core_if.h358 * @trust: enable VF trust
374 u8 trust; member
414 u8 trust; member

12345678910>>...18