Home
last modified time | relevance | path

Searched refs:carrier_name (Results 1 – 7 of 7) sorted by relevance

/Linux-v4.19/drivers/fmc/
Dfmc-dump.c51 fmc->carrier_name, fmc->slot_id, dev_name(&fmc->dev)); in fmc_dump_eeprom()
Dfmc-core.c213 if (fmc_check_version(devs[0]->version, devs[0]->carrier_name)) in fmc_device_register_n_gw()
244 if (!fmc->carrier_name || !fmc->carrier_data || in fmc_device_register_n_gw()
Dfmc-debug.c127 fmc->carrier_name, fmc->slot_id, dev_name(&fmc->dev)); in fmc_sdb_dump()
Dfmc-fakedev.c254 .carrier_name = "fake-fmc-carrier",
/Linux-v4.19/include/linux/
Dfmc.h101 char *carrier_name; /* name or NULL for virtual pins */ member
172 char *carrier_name; /* "SPEC" or similar, for special use */ member
/Linux-v4.19/Documentation/fmc/
Dcarrier.txt40 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
Dmezzanine.txt25 functionality: the `carrier_name' string allows the driver to check