| /linux/fs/proc/ |
| H A D | fd.c | 228 instantiate_t instantiate) in proc_lookupfd_common() argument
241 result = instantiate(dentry, task, &data); in proc_lookupfd_common()
249 instantiate_t instantiate) in proc_readfd_common() argument
276 name, len, instantiate, p, in proc_readfd_common()
|
| /linux/security/keys/ |
| H A D | user_defined.c | 27 .instantiate = generic_key_instantiate,
47 .instantiate = generic_key_instantiate,
|
| /linux/Documentation/driver-api/ |
| H A 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/drivers/i2c/ |
| H A D | i2c-smbus.c | 381 bool instantiate = true; in i2c_register_spd() local
442 instantiate = !write_disabled; in i2c_register_spd()
466 if (!instantiate) in i2c_register_spd()
|
| /linux/Documentation/i2c/ |
| H A 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/Documentation/admin-guide/gpio/ |
| H A D | gpio-aggregator.rst | 31 Userspace may ask the kernel to instantiate an aggregated GPIO
104 instantiate, named exactly as ``line0``, ``line1``, ..., ``lineY``, when
105 you want to instantiate ``Y+1`` (Y >= 0) lines. Configure all lines before
140 in order to instantiate the aggregator device. It can be set back to 0 to
|
| /linux/crypto/asymmetric_keys/ |
| H A D | Kconfig | 33 data and provides the ability to instantiate a crypto key from a
43 private key data and provides the ability to instantiate a crypto key
|
| H A D | pkcs7_key_type.c | 74 .instantiate = generic_key_instantiate,
|
| /linux/Documentation/hwmon/ |
| H A D | tmp103.rst | 32 Please refer how to instantiate this driver:
|
| H A D | adm1177.rst | 22 This driver does not auto-detect devices. You will have to instantiate the
|
| H A D | hih6130.rst | 31 instantiate I2C devices.
|
| H A D | ir36021.rst | 28 This driver does not probe for PMBus devices. You will have to instantiate
|
| H A D | ltc4151.rst | 29 which can be safely used to identify the chip. You will have to instantiate
|
| H A D | ltc4215.rst | 31 instantiate the devices explicitly.
|
| H A D | q54sj108a2.rst | 34 This driver does not auto-detect devices. You will have to instantiate the
|
| H A D | max6620.rst | 44 This driver does not auto-detect devices. You will have to instantiate the
|
| H A D | menf21bmc.rst | 30 You will have to instantiate the MFD driver explicitly.
|
| H A D | ltc3815.rst | 26 This driver does not probe for PMBus devices. You will have to instantiate
|
| H A D | dps920ab.rst | 31 This driver does not auto-detect devices. You will have to instantiate the
|
| H A D | ibm-cffps.rst | 19 This driver does not auto-detect devices. You will have to instantiate the
|
| H A D | shtc1.rst | 49 instantiate the device.
|
| H A D | bpa-rs600.rst | 24 This driver does not probe for PMBus devices. You will have to instantiate
|
| /linux/include/linux/ |
| H A D | key-type.h | 95 int (*instantiate)(struct key *key, struct key_preparsed_payload *prep); member
|
| /linux/Documentation/spi/ |
| H A D | spi-sc18is602.rst | 22 support Chip ID registers. You will have to instantiate the devices explicitly.
|
| /linux/net/rxrpc/ |
| H A D | server_key.c | 42 .instantiate = generic_key_instantiate,
|