Searched refs:instantiate (Results 1 – 25 of 120) sorted by relevance
12345
| /Linux-v6.6/fs/proc/ |
| D | fd.c | 223 instantiate_t instantiate) in proc_lookupfd_common() argument
236 result = instantiate(dentry, task, &data); in proc_lookupfd_common()
244 instantiate_t instantiate) in proc_readfd_common() argument
272 name, len, instantiate, p, in proc_readfd_common()
|
| /Linux-v6.6/security/keys/ |
| D | user_defined.c | 27 .instantiate = generic_key_instantiate,
47 .instantiate = generic_key_instantiate,
|
| /Linux-v6.6/Documentation/driver-api/ |
| D | ipmb.rst | 89 After loading the driver, you can instantiate the device as
92 a different I2C bus, you can instantiate a device for each of
102 For instance, you can instantiate the ipmb-dev-int device from
|
| /Linux-v6.6/Documentation/networking/devlink/ |
| D | devlink-params.rst | 102 - When enabled, the device driver will instantiate Ethernet specific
106 - When enabled, the device driver will instantiate RDMA specific
110 - When enabled, the device driver will instantiate VDPA networking
|
| /Linux-v6.6/Documentation/i2c/ |
| D | instantiating-devices.rst | 2 How to instantiate I2C devices
8 reason, the kernel code must instantiate I2C devices explicitly. There are
115 you can instantiate your I2C devices explicitly. This is done by filling
214 * Probing is only one way to instantiate I2C devices now, while it was the
238 instantiate, respectively delete, an I2C device.
271 You can also instantiate the device before the driver is loaded or even
|
| /Linux-v6.6/crypto/asymmetric_keys/ |
| D | Kconfig | 32 data and provides the ability to instantiate a crypto key from a
42 private key data and provides the ability to instantiate a crypto key
|
| D | pkcs7_key_type.c | 74 .instantiate = generic_key_instantiate,
|
| /Linux-v6.6/Documentation/w1/masters/ |
| D | ds2482.rst | 34 detection is done. You should instantiate the device explicitly.
|
| /Linux-v6.6/Documentation/hwmon/ |
| D | adm1177.rst | 22 This driver does not auto-detect devices. You will have to instantiate the
|
| D | tmp103.rst | 32 Please refer how to instantiate this driver:
|
| D | hih6130.rst | 31 instantiate I2C devices.
|
| D | sht4x.rst | 34 to instantiate the device.
|
| D | ir36021.rst | 28 This driver does not probe for PMBus devices. You will have to instantiate
|
| D | ltc4151.rst | 29 which can be safely used to identify the chip. You will have to instantiate
|
| D | ltc4215.rst | 31 instantiate the devices explicitly.
|
| D | max6620.rst | 44 This driver does not auto-detect devices. You will have to instantiate the
|
| D | q54sj108a2.rst | 34 This driver does not auto-detect devices. You will have to instantiate the
|
| D | menf21bmc.rst | 30 You will have to instantiate the MFD driver explicitly.
|
| D | ltc3815.rst | 26 This driver does not probe for PMBus devices. You will have to instantiate
|
| D | dps920ab.rst | 31 This driver does not auto-detect devices. You will have to instantiate the
|
| D | ibm-cffps.rst | 19 This driver does not auto-detect devices. You will have to instantiate the
|
| D | bpa-rs600.rst | 24 This driver does not probe for PMBus devices. You will have to instantiate
|
| D | sbtsi_temp.rst | 15 To instantiate this driver on an AMD CPU with SB-TSI
|
| /Linux-v6.6/include/linux/ |
| D | key-type.h | 94 int (*instantiate)(struct key *key, struct key_preparsed_payload *prep); member
|
| /Linux-v6.6/Documentation/spi/ |
| D | spi-sc18is602.rst | 22 support Chip ID registers. You will have to instantiate the devices explicitly.
|
12345
