Lines Matching refs:fmc

26 change in layout of some fmc data structures).  Device writers should
53              char *mezzanine_name;           /* Defaults to ``fmc'' */
115    * mezzanine_name: filled by fmc-bus during identification.
123 the fmc-bus environment, and is a good reference to look at.
135              uint32_t (*readl)(struct fmc_device *fmc, int offset);
136              void (*writel)(struct fmc_device *fmc, uint32_t value, int offset);
138              int (*validate)(struct fmc_device *fmc, struct fmc_driver *drv);
139              int (*irq_request)(struct fmc_device *fmc, irq_handler_t h,
141              void (*irq_ack)(struct fmc_device *fmc);
142              int (*irq_free)(struct fmc_device *fmc);
143              int (*gpio_config)(struct fmc_device *fmc, struct fmc_gpio *gpio,
145              int (*read_ee)(struct fmc_device *fmc, int pos, void *d, int l);
146              int (*write_ee)(struct fmc_device *fmc, int pos, const void *d, int l);
175      `fmc-trivial.ko', described in *note fmc-trivial::.
195      informative.  The handler will receive the fmc pointer as dev_id;
197      but fmc-specific flags may be added in the future. You'll most
224 Support for GPIO pins in the fmc-bus environment is not very