Home
last modified time | relevance | path

Searched full:derive (Results 1 – 25 of 174) sorted by relevance

1234567

/linux-5.10/drivers/gpu/drm/vmwgfx/
Dvmwgfx_binding.h86 * @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-5.10/Documentation/devicetree/bindings/pwm/
Dpwm-rockchip.txt12 - There is one clock that's used both to derive the functional clock
15 - "pwm": This is used to derive the functional clock.
Dpwm-sprd.txt10 "pwmn": used to derive the functional clock for PWM channel n (n range: 0 ~ 3).
/linux-5.10/Documentation/devicetree/bindings/iio/adc/
Dpalmas-gpadc.txt27 Values are rounded to derive 0uA, 5uA, 15uA, 20uA.
29 Values are rounded to derive 0uA, 10uA, 400uA, 800uA.
Daspeed,ast2400-adc.yaml27 Input clock used to derive the sample clock. Expected to be the
/linux-5.10/Documentation/devicetree/bindings/sound/
Dfsl,esai.txt31 derive HCK, SCK and FS.
33 derive HCK, SCK and FS.
/linux-5.10/Documentation/devicetree/bindings/i2c/
Di2c-rk3x.yaml52 there is one clock that is used both to derive the functional clock
54 For newer hardware (rk3399) this clock is used to derive
/linux-5.10/Documentation/devicetree/bindings/clock/
Dxgene.txt21 - 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
Dimx7ulp-scg-clock.yaml30 include: clock reference selection, generation of clock used to derive
/linux-5.10/drivers/s390/crypto/
Dzcrypt_ccamisc.h171 * Derive proteced key from an CCA AES DATA secure key.
184 * Derive proteced key from CCA AES cipher secure key.
196 * Derive proteced key from CCA ECC secure private key.
/linux-5.10/Documentation/devicetree/bindings/arm/tegra/
Dnvidia,tegra30-actmon.txt4 components in the system. This information can be used to derive the rate at
/linux-5.10/tools/testing/selftests/bpf/progs/
Dtest_rdonly_maps.c50 /* validate verifier can derive loop termination */ in part_loop()
Dtest_tc_tunnel.c84 * network protocol, and derive the outer header fields from in encap_ipv4()
101 /* Derive the IPv4 header fields from the IPv6 header */ in encap_ipv4()
/linux-5.10/Documentation/devicetree/bindings/serial/
Dmvebu-uart.txt13 - clocks: UART reference clock used to derive the baudrate. If no clock
/linux-5.10/net/bluetooth/
Damp.c199 /* Derive Generic AMP Link Key (gamp) */ in phylink_gen_key()
202 bt_dev_err(hdev, "could not derive Generic AMP Key: err %d", err); in phylink_gen_key()
212 /* Derive Dedicated AMP Link Key: "802b" is 802.11 PAL keyID */ in phylink_gen_key()
/linux-5.10/fs/crypto/
Dkeysetup_v1.c41 * derived key can "decrypt" it to get back to the master key, then derive any
264 /* v1 policy, !DIRECT_KEY: derive the file's encryption key */
/linux-5.10/drivers/clk/
DKconfig180 Y2 and Y3 derive from PLL1
181 Y4 and Y5 derive from PLL2
/linux-5.10/Documentation/driver-api/driver-model/
Dbinding.rst30 Instead of trying to derive a complex state machine and matching
/linux-5.10/sound/soc/fsl/
Dfsl_esai.c41 * @extalclk: esai clock source to derive HCK, SCK and FS
42 * @fsysclk: system clock source to derive HCK, SCK and FS
327 dev_err(dai->dev, "failed to derive required HCK%c rate\n", in fsl_esai_set_dai_sysclk()
339 dev_err(dai->dev, "failed to derive required HCK%c rate\n", in fsl_esai_set_dai_sysclk()
387 dev_err(dai->dev, "failed to derive required SCK%c rate\n", in fsl_esai_set_bclk()
/linux-5.10/crypto/
Dadiantum.c59 * needing to derive per-file keys. So instead we use two blocks, or 32 bytes.
108 * Given the XChaCha stream key K_S, derive the block cipher key K_E and the
139 /* Derive the subkeys */ in adiantum_setkey()
/linux-5.10/Documentation/virt/kvm/
Dmsr.rst94 from current tsc to derive a notion of elapsed time since the
115 derive per-CPU time by doing::
/linux-5.10/drivers/net/phy/
Dsfp-bus.c215 * Parse the EEPROM identification information and derive the supported
326 /* For fibre channel SFP, derive possible BaseX modes */ in sfp_parse_support()
364 * Derive the phy_interface_t mode for the SFP module from the link
/linux-5.10/drivers/mtd/nand/raw/gpmi-nand/
Dgpmi-nand.h92 * @clk_rate: The clock rate that must be used to derive the
/linux-5.10/Documentation/admin-guide/hw-vuln/
Dspectre.rst148 be used later by the kernel as an index to an array or to derive
228 code to derive invalid data pointers accessing privileged memory in
267 (e.g. in registers) via hyper-calls to derive invalid pointers to
293 or message passing. Such parameters could be used to derive data
/linux-5.10/include/dt-bindings/pinctrl/
Drzn1-pinctrl.h17 * You can derive the hardware value pretty easily too, as

1234567