Searched refs:carrier_name (Results 1 – 6 of 6) sorted by relevance
/linux-4.4.14/drivers/fmc/ |
D | fmc-dump.c | 53 fmc->carrier_name, fmc->slot_id, dev_name(&fmc->dev)); in fmc_dump_eeprom() 91 fmc->carrier_name, fmc->slot_id, dev_name(&fmc->dev)); in fmc_dump_sdb()
|
D | fmc-core.c | 154 if (fmc_check_version(devs[0]->version, devs[0]->carrier_name)) in fmc_device_register_n() 185 if (!fmc->carrier_name || !fmc->carrier_data || in fmc_device_register_n()
|
D | fmc-fakedev.c | 254 .carrier_name = "fake-fmc-carrier",
|
/linux-4.4.14/include/linux/ |
D | fmc.h | 101 char *carrier_name; /* name or NULL for virtual pins */ member 168 char *carrier_name; /* "SPEC" or similar, for special use */ member
|
/linux-4.4.14/Documentation/fmc/ |
D | carrier.txt | 40 char *carrier_name; /* "SPEC" or similar, for special use */ 76 * carrier_name. 217 by a driver that has verified the `carrier_name' field. 236 char *carrier_name; 243 By specifying a carrier_name for each pin, the driver may access 247 no structure at all refers to the current carrier_name), the operation 267 provided the carrier_name field in the data structure is left
|
D | mezzanine.txt | 25 functionality: the `carrier_name' string allows the driver to check
|