Searched refs:FMC (Results 1 – 16 of 16) sorted by relevance
/linux-4.4.14/drivers/fmc/ |
D | Kconfig | 2 # FMC (ANSI-VITA 57.1) bus support 5 menuconfig FMC config 6 tristate "FMC support" 9 FMC (FPGA Mezzanine Carrier) is a mechanical and electrical 19 if FMC 22 tristate "FMC fake device (software testing)" 29 tristate "FMC trivial mezzanine driver (software testing)" 31 This is a fake mezzanine driver, to show how FMC works and test it. 36 tristate "FMC mezzanine driver to write I2C EEPROM" 44 tristate "FMC mezzanine driver that registers a char device" [all …]
|
/linux-4.4.14/Documentation/fmc/ |
D | FMC-and-SDB.txt | 2 FMC (FPGA Mezzanine Card) is the standard we use for our I/O devices, 7 To achieve this, we abstract the FMC interface. 13 Code and documentation for the FMC bus was born as part of the spec-sw 29 What is FMC 32 FMC, as said, stands for "FPGA Mezzanine Card". It is a standard 37 The FMC card is an almost square PCB, around 70x75 millimeters, that is 49 FMC, as such, is not a bus in the usual meaning of the term, because 60 a filesystem inside the FMC EEPROM. 62 SDB is not mandatory for use of this FMC kernel bus, but if you have SDB 68 SDB support for FMC is described in *note FMC Identification:: and
|
D | parameters.txt | 27 [ 6626.150370] FMC: mezzanine 0: 0000:02:00.0 on SPEC 28 [ 6626.155179] FMC: dumping eeprom 0x2000 (8192) bytes 47 FMC: mezzanine 0: 0000:02:00.0 on SPEC 48 FMC: poor dump of sdb first level:
|
D | fmc-trivial.txt | 5 interrupt handler. I used it to verify the basic mechanism of the FMC 8 The module implements the generic FMC parameters, so it can program a
|
D | mezzanine.txt | 1 FMC Driver 4 An FMC driver is concerned with the specific mezzanine and associated 10 EEPROM (as mandated by the FMC standard) or by the actual cores 40 Like most other Linux drivers, and FMC driver must list all the devices 42 table, but in FMC we can match hardware based either on the contents of 47 vendor) and the device (see *note FMC Identification::); for 78 Most of the FMC drivers need the same set of kernel parameters. This 95 accept to drive cards that appear in the list (even if the FMC ID
|
D | fmc-fakedev.txt | 6 Unlike the SPEC driver, which creates an FMC device for each PCI cards 12 described in *note FMC Identification::),, which by default is 35 offset 0, the module will unregister and register again the FMC device.
|
D | fmc-chardev.txt | 8 created by udev) is the same name as the underlying FMC device. Thus, 12 fdelay-0400 if the FMC core can rely on both a mezzanine name and a bus 44 The simple program tools/fmc-mem in this package can access an FMC char 46 is not specific to FMC at all, it just uses lseek, read and write.
|
D | 00-INDEX | 10 FMC-and-SDB.txt 11 - What are FMC and SDB, basic concepts for this framework
|
D | API.txt | 4 The FMC core exports the usual 4 functions that are needed for a bus to 23 The data structure that describe a device is detailed in *note FMC 24 Device::, the one that describes a driver is detailed in *note FMC
|
D | carrier.txt | 1 FMC Device 4 Within the Linux bus framework, the FMC device is created and 7 registers an associated FMC device for each card. The SVEC driver can 9 twice, because the SVEC carries two FMC mezzanines). Similarly, an 10 Etherbone driver will be able to register its own FMC devices, offering 13 The contents of the EEPROM within the FMC are used for identification 178 The carrier enumerates FMC devices by loading a standard (or 306 Given the typical use case of FMC devices, GPIO operations are not
|
D | identifiers.txt | 1 FMC Identification 4 The FMC standard requires every compliant mezzanine to carry 21 write the EEPROM. If you are just a software developer writing an FMC 127 This package (generic FMC bus support) only accesses two files in the 132 short name used by the FMC core. For example, a name of "fdelay" may
|
/linux-4.4.14/Documentation/arm/stm32/ |
D | stm32f429-overview.txt | 10 - External memory support through FMC controller (PSRAM, SDRAM, NOR, NAND)
|
/linux-4.4.14/sound/pci/trident/ |
D | trident_main.c | 455 FmcRvolCvol = ((voice->FMC & 3) << 14) | in snd_trident_write_voice_regs() 639 outw(((voice->FMC & 0x0003) << 14) | ((voice->RVol & 0x007f) << 7) | in snd_trident_write_rvol_reg() 663 outw(((voice->FMC & 0x0003) << 14) | ((voice->RVol & 0x007f) << 7) | in snd_trident_write_cvol_reg() 970 voice->FMC = 3; in snd_trident_playback_prepare() 996 evoice->FMC = 3; in snd_trident_playback_prepare() 1113 voice->FMC = 3; in snd_trident_capture_prepare() 1207 voice->FMC = 0; in snd_trident_si7018_capture_prepare() 1231 evoice->FMC = 3; in snd_trident_si7018_capture_prepare() 1285 voice->FMC = 3; in snd_trident_foldback_prepare() 1308 evoice->FMC = 3; in snd_trident_foldback_prepare() [all …]
|
D | trident.h | 301 unsigned char FMC; /* 2 bits */ member
|
/linux-4.4.14/Documentation/ |
D | 00-INDEX | 195 - information about the FMC bus abstraction
|
/linux-4.4.14/ |
D | MAINTAINERS | 4404 FMC SUBSYSTEM
|