/linux/drivers/gpu/drm/vmwgfx/ |
H A D | vmwgfx_binding.h | 86 * @bi: struct vmw_ctx_bindinfo we derive from. 97 * @bi: struct vmw_ctx_bindinfo we derive from. 108 * @bi: struct vmw_ctx_bindinfo we derive from. 125 * @bi: struct vmw_ctx_bindinfo we derive from. 138 * @bi: struct vmw_ctx_bindinfo we derive from. 153 * @bi: struct vmw_ctx_bindinfo we derive from. 168 * @bi: struct vmw_ctx_bindinfo we derive from. 209 * @bi: struct vmw_ctx_bindinfo we derive from.
|
/linux/Documentation/devicetree/bindings/pwm/ |
H A D | pwm-rockchip.yaml | 73 - description: Used to derive the functional clock for the device. 90 Used both to derive the functional clock
|
/linux/Documentation/devicetree/bindings/i2c/ |
H A D | i2c-rk3x.yaml | 57 there is one clock that is used both to derive the functional clock 59 For newer hardware (rk3399) this clock is used to derive
|
/linux/drivers/md/dm-vdo/ |
H A D | funnel-queue.h | 27 * in the queue must all be the same so the client can derive their structure pointer from the 78 * structure. The caller must be able to derive the address of the start of their data structure
|
/linux/Documentation/devicetree/bindings/clock/ |
H A D | xgene.txt | 21 - clock-output-names : shall be the name of the PLL referenced by derive 30 - clock-output-names : shall be the name of the clock referenced by derive
|
H A D | cirrus,cs2000-cp.yaml | 60 If not given, the static mode shall be used to derive the
|
H A D | imx7ulp-scg-clock.yaml | 30 include: clock reference selection, generation of clock used to derive
|
/linux/drivers/s390/crypto/ |
H A D | zcrypt_ccamisc.h | 172 * Derive proteced key from an CCA AES DATA secure key. 185 * Derive proteced key from CCA AES cipher secure key. 197 * Derive proteced key from CCA ECC secure private key.
|
/linux/Documentation/devicetree/bindings/iio/adc/ |
H A D | aspeed,ast2400-adc.yaml | 28 Input clock used to derive the sample clock. Expected to be the
|
H A D | aspeed,ast2600-adc.yaml | 42 Input clock used to derive the sample clock. Expected to be the
|
/linux/drivers/platform/x86/ |
H A D | dual_accel_detect.h | 14 * (instead userspace can derive the status itself by directly reading the 2 accels).
|
/linux/net/sunrpc/auth_gss/ |
H A D | gss_krb5_test.c | 662 .desc = "Derive Kc subkey for camellia128-cts-cmac", 669 .desc = "Derive Ke subkey for camellia128-cts-cmac", 676 .desc = "Derive Ki subkey for camellia128-cts-cmac", 683 .desc = "Derive Kc subkey for camellia256-cts-cmac", 690 .desc = "Derive Ke subkey for camellia256-cts-cmac", 697 .desc = "Derive Ki subkey for camellia256-cts-cmac", 1287 .desc = "Derive Kc subkey for aes128-cts-hmac-sha256-128", 1294 .desc = "Derive Ke subkey for aes128-cts-hmac-sha256-128", 1301 .desc = "Derive Ki subkey for aes128-cts-hmac-sha256-128", 1308 .desc = "Derive Kc subkey for aes256-cts-hmac-sha384-192", [all …]
|
H A D | gss_krb5_keys.c | 255 * krb5_derive_key_v2 - Derive a subkey for an RFC 3962 enctype 344 * krb5_kdf_feedback_cmac - Derive a subkey for a Camellia/CMAC-based enctype 479 * krb5_kdf_hmac_sha2 - Derive a subkey for an AES/SHA2-based enctype
|
/linux/fs/crypto/ |
H A D | keysetup_v1.c | 41 * derived key can "decrypt" it to get back to the master key, then derive any 267 /* v1 policy, !DIRECT_KEY: derive the file's encryption key */
|
/linux/rust/kernel/net/phy/ |
H A D | reg.rs | 55 #[derive(Copy, Clone, Debug)] 138 #[derive(Copy, Clone, Debug)]
|
/linux/tools/testing/selftests/bpf/progs/ |
H A D | test_rdonly_maps.c | 51 /* validate verifier can derive loop termination */ in part_loop()
|
/linux/Documentation/virt/coco/ |
H A D | sev-guest.rst | 110 The SNP_GET_DERIVED_KEY ioctl can be used to get a key derive from a root key. 115 SEV-SNP firmware to derive the key. See SEV-SNP specification for further details
|
/linux/Documentation/devicetree/bindings/serial/ |
H A D | mvebu-uart.txt | 13 - clocks: UART reference clock used to derive the baudrate. If no clock
|
/linux/rust/macros/ |
H A D | zeroable.rs | 6 pub(crate) fn derive(input: TokenStream) -> TokenStream { in derive() function
|
/linux/sound/soc/fsl/ |
H A D | fsl_esai.c | 39 * @extalclk: esai clock source to derive HCK, SCK and FS 40 * @fsysclk: system clock source to derive HCK, SCK and FS 322 dev_err(dai->dev, "failed to derive required HCK%c rate\n", in fsl_esai_set_dai_sysclk() 334 dev_err(dai->dev, "failed to derive required HCK%c rate\n", in fsl_esai_set_dai_sysclk() 382 dev_err(dai->dev, "failed to derive required SCK%c rate\n", in fsl_esai_set_bclk()
|
/linux/Documentation/devicetree/bindings/devfreq/ |
H A D | nvidia,tegra30-actmon.yaml | 16 components in the system. This information can be used to derive the rate at
|
/linux/Documentation/security/tpm/ |
H A D | tpm-security.rst | 82 and storage seeds, which can be used to derive asymmetric keys. 88 The mechanism chosen for the Linux Kernel is to derive the primary
|
/linux/Documentation/driver-api/driver-model/ |
H A D | binding.rst | 30 Instead of trying to derive a complex state machine and matching
|
/linux/drivers/net/ethernet/mellanox/mlxbf_gige/ |
H A D | mlxbf_gige_regs.h | 81 * so use that plus size of single register to derive total size
|
/linux/Documentation/virt/kvm/x86/ |
H A D | msr.rst | 94 from current tsc to derive a notion of elapsed time since the 115 derive per-CPU time by doing::
|