Searched refs:instantiate (Results 1 – 25 of 98) sorted by relevance
1234
| /Linux-v5.4/fs/proc/ |
| D | fd.c | 208 instantiate_t instantiate) in proc_lookupfd_common() argument
221 result = instantiate(dentry, task, &data); in proc_lookupfd_common()
229 instantiate_t instantiate) in proc_readfd_common() argument
262 name, len, instantiate, p, in proc_readfd_common()
|
| /Linux-v5.4/crypto/asymmetric_keys/ |
| D | Kconfig | 44 data and provides the ability to instantiate a crypto key from a
54 private key data and provides the ability to instantiate a crypto key
63 private key data and provides the ability to instantiate a crypto key
|
| D | pkcs7_key_type.c | 74 .instantiate = generic_key_instantiate,
|
| /Linux-v5.4/security/keys/ |
| D | user_defined.c | 27 .instantiate = generic_key_instantiate,
47 .instantiate = generic_key_instantiate,
|
| /Linux-v5.4/Documentation/driver-api/ |
| D | ipmb.rst | 85 After loading the driver, you can instantiate the device as
88 a different I2C bus, you can instantiate a device for each of
98 For instance, you can instantiate the ipmb-dev-int device from
|
| /Linux-v5.4/Documentation/i2c/ |
| D | instantiating-devices.rst | 2 How to instantiate I2C devices
8 reason, the kernel code must instantiate I2C devices explicitly. There are
100 you can instantiate your I2C devices explicitly. This is done by filling
195 * Probing is only one way to instantiate I2C devices now, while it was the
218 must write the right parameters to them in order to properly instantiate,
252 You can also instantiate the device before the driver is loaded or even
|
| /Linux-v5.4/Documentation/w1/masters/ |
| D | ds2482.rst | 34 detection is done. You should instantiate the device explicitly.
|
| /Linux-v5.4/Documentation/hwmon/ |
| D | tmp103.rst | 32 Please refer how to instantiate this driver:
|
| D | hih6130.rst | 31 instantiate I2C devices.
|
| 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 | ltc3815.rst | 26 This driver does not probe for PMBus devices. You will have to instantiate
|
| D | menf21bmc.rst | 30 You will have to instantiate the MFD driver explicitly.
|
| D | ibm-cffps.rst | 19 This driver does not auto-detect devices. You will have to instantiate the
|
| D | ir38064.rst | 26 This driver does not probe for PMBus devices. You will have to instantiate
|
| D | shtc1.rst | 49 instantiate the device.
|
| D | ltc2990.rst | 36 This driver does not probe for PMBus devices. You will have to instantiate
|
| D | max20751.rst | 32 This driver does not auto-detect devices. You will have to instantiate the
|
| D | ltc4260.rst | 30 which can be safely used to identify the chip. You will have to instantiate
|
| D | tps40422.rst | 30 This driver does not auto-detect devices. You will have to instantiate the
|
| /Linux-v5.4/certs/ |
| D | blacklist.c | 75 .instantiate = generic_key_instantiate,
|
| /Linux-v5.4/include/linux/ |
| D | key-type.h | 93 int (*instantiate)(struct key *key, struct key_preparsed_payload *prep); member
|
| /Linux-v5.4/Documentation/spi/ |
| D | spi-sc18is602.rst | 22 support Chip ID registers. You will have to instantiate the devices explicitly.
|
| /Linux-v5.4/Documentation/devicetree/bindings/clock/ |
| D | samsung,s2mps11.txt | 11 To register these as clocks with common clock framework instantiate under
|
| /Linux-v5.4/Documentation/i2c/busses/ |
| D | i2c-taos-evm.rst | 11 module to instantiate the right I2C chip on the bus. Obviously, a driver
|
1234
