/kernel/linux/linux-5.10/drivers/media/radio/ |
D | radio-trust.c | 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() 185 struct trust *tr = container_of(isa, struct trust, isa); in trust_initialize()
|
D | Makefile | 20 obj-$(CONFIG_RADIO_TRUST) += radio-trust.o
|
/kernel/linux/linux-5.10/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.
|
/kernel/linux/linux-5.10/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.
|
D | topology.rst | 72 The logical ID of the package. As we do not trust BIOSes to enumerate the
|
/kernel/linux/linux-5.10/include/linux/qed/ |
D | qed_iov_if.h | 31 int (*set_trust) (struct qed_dev *cdev, int vfid, bool trust);
|
/kernel/linux/linux-5.10/drivers/net/ethernet/broadcom/bnxt/ |
D | bnxt_sriov.h | 37 int bnxt_set_vf_trust(struct net_device *dev, int vf_id, bool trust);
|
/kernel/linux/linux-5.10/drivers/net/ethernet/huawei/hinic/ |
D | hinic_sriov.h | 46 bool trust; member
|
D | hinic_sriov.c | 351 if (vf_info->pf_set_mac && !(vf_info->trust) && in hinic_set_vf_mac_msg_handler() 565 ivi->trusted = vfinfo->trust; in hinic_get_vf_config() 791 bool trust) in hinic_set_vf_trust() argument 801 vf_infos[vf_id].trust = trust; in hinic_set_vf_trust() 820 cur_trust = nic_io->vf_infos[vf].trust; in hinic_ndo_set_vf_trust() 1129 if (vf_infos->trust) in hinic_clear_vf_infos()
|
/kernel/linux/linux-5.10/tools/testing/selftests/rcutorture/bin/ |
D | kvm-check-branches.sh | 77 kvm.sh --cpus $cpus --duration 3 --trust-make > $resdir/$ds/$idir/kvm.sh.out 2>&1
|
D | kvm.sh | 212 --trust-make)
|
/kernel/linux/linux-5.10/Documentation/admin-guide/media/ |
D | radio-cardlist.rst | 31 radio-trust Trust FM radio card
|
/kernel/linux/linux-5.10/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 876 PGP incorporates a trust delegation mechanism known as the "Web of 886 "the SSH-like approach to trust." With SSH, the first time you connect 890 trust the changed key or not. Similarly, the first time you import 896 We recommend that you use the combined TOFU+PGP trust model (which is 898 ``trust-model`` setting in ``~/.gnupg/gpg.conf``:: [all …]
|
D | management-style.rst | 95 deleting it, you may have irrevocably lost the trust of that 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
|
/kernel/linux/linux-5.10/Documentation/hwmon/ |
D | lm63.rst | 75 is left to the BIOS, and the driver will blindly trust it. Only the original
|
D | dell-smm-hwmon.rst | 104 other users and you don't trust them you may want
|
/kernel/linux/linux-5.10/Documentation/usb/ |
D | authorization.rst | 94 can fake descriptors and device info. Don't trust that. You are
|
/kernel/linux/linux-5.10/Documentation/ABI/testing/ |
D | sysfs-class-cxl | 246 0 don't trust, the image may be different (default) 247 1 trust that the image will not change.
|
D | sysfs-bus-nfit | 212 the system over the activation event, or trust that the OS will
|
/kernel/linux/linux-5.10/Documentation/security/tpm/ |
D | xen-tpmfront.rst | 21 the chain of trust rooted in the hardware TPM to virtual machines in Xen. Each
|
/kernel/linux/linux-5.10/Documentation/dev-tools/kunit/ |
D | index.rst | 83 someone sends you some code. Why trust that someone ran all their tests
|
/kernel/linux/linux-5.10/Documentation/i2c/ |
D | functionality.rst | 9 I2C specifications, a client can not trust that everything it needs
|
/kernel/linux/linux-5.10/Documentation/input/devices/ |
D | iforce-protocol.rst | 17 from Immerse. That's why you should not trust what is written in this
|
/kernel/linux/linux-5.10/arch/arm64/boot/dts/qcom/ |
D | ipq6018.dtsi | 204 qcom,config-pipe-trust-reg = <0>;
|
/kernel/linux/linux-5.10/drivers/char/tpm/ |
D | Kconfig | 146 can be found at http://www.trust.rub.de/projects/linux-device-driver-infineon-tpm/
|