| /linux-4.4.14/fs/proc/ |
| D | fd.c | 211 instantiate_t instantiate) in proc_lookupfd_common() argument
222 result = instantiate(dir, dentry, task, (void *)(unsigned long)fd); in proc_lookupfd_common()
230 instantiate_t instantiate) in proc_readfd_common() argument
258 name, len, instantiate, p, in proc_readfd_common()
|
| D | base.c | 1802 instantiate_t instantiate, struct task_struct *task, const void *ptr) in proc_fill_cache() argument
1815 if (instantiate(d_inode(dir), child, task, ptr) < 0) { in proc_fill_cache()
|
| /linux-4.4.14/security/keys/ |
| D | user_defined.c | 31 .instantiate = generic_key_instantiate,
51 .instantiate = generic_key_instantiate,
|
| D | big_key.c | 48 .instantiate = generic_key_instantiate,
|
| D | request_key_auth.c | 40 .instantiate = request_key_auth_instantiate,
|
| D | key.c | 421 ret = key->type->instantiate(key, prep); in __key_instantiate_and_link()
800 if (!index_key.type->instantiate || in key_create_or_update()
|
| D | keyring.c | 91 .instantiate = keyring_instantiate,
|
| D | trusted.c | 1130 .instantiate = trusted_instantiate,
|
| /linux-4.4.14/Documentation/i2c/ |
| D | instantiating-devices | 1 How to instantiate I2C devices
7 reason, the kernel code must instantiate I2C devices explicitly. There are
99 you can instantiate your I2C devices explicitly. This is done by filling
192 * Probing is only one way to instantiate I2C devices now, while it was the
215 must write the right parameters to them in order to properly instantiate,
247 You can also instantiate the device before the driver is loaded or even
|
| D | old-module-parameters | 40 Of course, it is important to instantiate the "dummy" device before loading
|
| D | writing-clients | 22 Usually, you will implement a single driver structure, and instantiate
166 you can instantiate that device by simply filling an i2c_board_info
|
| D | slave-interface | 33 I2C slave backends behave like standard I2C clients. So, you can instantiate
|
| /linux-4.4.14/Documentation/w1/masters/ |
| D | ds2482 | 27 detection is done. You should instantiate the device explicitly.
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | tmp103 | 27 Please refer how to instantiate this driver:
|
| D | hih6130 | 26 instantiate I2C devices.
|
| D | ltc4215 | 26 instantiate the devices explicitly.
|
| D | ltc4151 | 24 which can be safely used to identify the chip. You will have to instantiate
|
| D | menf21bmc | 27 You will have to instantiate the MFD driver explicitly.
|
| D | shtc1 | 28 instantiate the device.
|
| D | htu21 | 25 This driver does not auto-detect devices. You will have to instantiate the
|
| D | max20751 | 27 This driver does not auto-detect devices. You will have to instantiate the
|
| D | ltc4260 | 25 which can be safely used to identify the chip. You will have to instantiate
|
| D | tps40422 | 26 This driver does not auto-detect devices. You will have to instantiate the
|
| D | max16064 | 26 This driver does not auto-detect devices. You will have to instantiate the
|
| D | max6650 | 46 This driver does not auto-detect devices. You will have to instantiate the
|
| D | adc128d818 | 45 addresses 0x35 to 0x37. Those addresses are not scanned. You have to instantiate
|
| D | max8688 | 26 This driver does not auto-detect devices. You will have to instantiate the
|
| D | lineage-pem | 30 which can be safely used to identify the chip. You will have to instantiate
|
| D | ltc4261 | 25 which can be safely used to identify the chip. You will have to instantiate
|
| D | ltc2945 | 25 which can be safely used to identify the chip. You will have to instantiate
|
| D | lm25066 | 50 This driver does not auto-detect devices. You will have to instantiate the
|
| D | adm1275 | 43 This driver does not auto-detect devices. You will have to instantiate the
|
| D | pcf8591 | 62 try. You have to explicitly instantiate the device at the relevant
|
| D | ltc4245 | 27 instantiate the devices explicitly.
|
| D | max16065 | 61 can be safely used to identify the chip. You will have to instantiate
|
| D | ucd9200 | 37 This driver does not auto-detect devices. You will have to instantiate the
|
| D | ucd9000 | 53 This driver does not auto-detect devices. You will have to instantiate the
|
| D | max34440 | 50 This driver does not auto-detect devices. You will have to instantiate the
|
| D | adm1021 | 104 will have to explicitly instantiate the sensor chips from user-space. See
|
| D | zl6100 | 74 This driver does not auto-detect devices. You will have to instantiate the
|
| D | smm665 | 62 can be safely used to identify the chip. You will have to instantiate
|
| D | pmbus | 62 PMBus devices. You will have to instantiate the devices explicitly.
|
| D | ltc2978 | 84 This driver does not probe for PMBus devices. You will have to instantiate
|
| /linux-4.4.14/crypto/asymmetric_keys/ |
| D | pkcs7_key_type.c | 93 .instantiate = generic_key_instantiate,
|
| D | Kconfig | 37 data and provides the ability to instantiate a crypto key from a
|
| D | asymmetric_type.c | 366 .instantiate = generic_key_instantiate,
|
| /linux-4.4.14/include/linux/ |
| D | key-type.h | 102 int (*instantiate)(struct key *key, struct key_preparsed_payload *prep); member
|
| /linux-4.4.14/Documentation/spi/ |
| D | spi-sc18is602 | 19 support Chip ID registers. You will have to instantiate the devices explicitly.
|
| /linux-4.4.14/fs/cifs/ |
| D | cifs_spnego.c | 64 .instantiate = cifs_spnego_key_instantiate,
|
| D | cifsacl.c | 83 .instantiate = cifs_idmap_key_instantiate,
|
| /linux-4.4.14/Documentation/i2c/busses/ |
| D | i2c-taos-evm | 9 module to instantiate the right I2C chip on the bus. Obviously, a driver
|
| /linux-4.4.14/fs/jffs2/ |
| D | LICENCE | 20 As a special exception, if other files instantiate templates or use
|
| /linux-4.4.14/Documentation/block/ |
| D | null_blk.txt | 26 Selects which block-layer the module should instantiate with.
|
| /linux-4.4.14/net/dns_resolver/ |
| D | dns_key.c | 256 .instantiate = generic_key_instantiate,
|
| /linux-4.4.14/Documentation/misc-devices/ |
| D | max6875 | 45 The driver does not probe any address, so you explicitly instantiate the
|
| /linux-4.4.14/Documentation/DocBook/ |
| D | filesystems.xml.db | 15 API-d-instantiate
16 API-d-instantiate-no-diralias
|
| /linux-4.4.14/Documentation/security/ |
| D | keys-request-key.txt | 110 instantiate key U, using key W as a reference (perhaps it contacts a
135 authorisation key to negatively instantiate a key that's under construction.
|
| D | keys.txt | 409 description, and to instantiate it with the supplied payload and attach it
667 The process must have write access on the key to be able to instantiate
680 (*) Negatively instantiate a partially constructed key.
691 The process must have write access on the key to be able to instantiate
747 (*) Assume the authority granted to instantiate a key
751 This assumes or divests the authority required to instantiate the
1149 instantiate key). The structure pointed to by prep looks like:
1170 along to the instantiate() or update() operations. If set, the expiry
1183 successfully, even if instantiate() or update() succeed.
1186 (*) int (*instantiate)(struct key *key, struct key_preparsed_payload *prep);
[all …]
|
| /linux-4.4.14/fs/nfs/ |
| D | nfs4idmap.c | 180 .instantiate = generic_key_instantiate,
403 .instantiate = generic_key_instantiate,
|
| /linux-4.4.14/Documentation/devicetree/bindings/mfd/ |
| D | max8998.txt | 102 /* Regulators to instantiate */
|
| D | s2mps11.txt | 33 instantiate a sub-node named "clocks". It uses the common clock binding
|
| /linux-4.4.14/Documentation/networking/ |
| D | dns_resolver.txt | 131 /sbin/request-key what program to run to instantiate the key.
|
| D | vrf.txt | 105 To instantiate a VRF device and associate it with a table:
|
| /linux-4.4.14/net/ceph/ |
| D | crypto.c | 569 .instantiate = generic_key_instantiate,
|
| /linux-4.4.14/net/rxrpc/ |
| D | ar-key.c | 46 .instantiate = generic_key_instantiate,
62 .instantiate = generic_key_instantiate,
|
| /linux-4.4.14/Documentation/scsi/ |
| D | scsi_fc_transport.txt | 58 Linux device tree, and instruct the fc_host's driver to instantiate the
173 A "simple" create interface to instantiate a vport on an fc_host.
|
| /linux-4.4.14/arch/powerpc/platforms/ |
| D | Kconfig | 332 Uses information from the OF or flattened device tree to instantiate
|
| /linux-4.4.14/security/keys/encrypted-keys/ |
| D | encrypted.c | 973 .instantiate = encrypted_instantiate,
|
| /linux-4.4.14/Documentation/nvdimm/ |
| D | nvdimm.txt | 18 libndctl: instantiate a new library context example
271 LIBNDCTL: instantiate a new library context example
|
| /linux-4.4.14/Documentation/filesystems/caching/ |
| D | fscache.txt | 325 OBJ INST Length of time to instantiate an object
|
| D | backend-api.txt | 252 allocated and attached to the cookie. This should instantiate that object
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | mmu.txt | 386 To instantiate a large spte, four constraints must be satisfied:
|
| /linux-4.4.14/Documentation/filesystems/cifs/ |
| D | CHANGES | 247 problem (instantiate inodes/dentries in right order for readdir).
|
| /linux-4.4.14/Documentation/ |
| D | pinctrl.txt | 464 abstract and provide pinmux settings to the devices you choose to instantiate
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | coda.txt | 767 instantiate a vnode, inode or file handle at kernel level for the new
|