Searched refs:linking (Results 1 – 25 of 84) sorted by relevance
1234
16 Pins on the device (for linking into audio routes) for RT274:
17 Pins on the device (for linking into audio routes) for RT5616:
12 Pins on the device (for linking into audio routes):
11 Pins on the device (for linking into audio routes):
13 Pins on the device (for linking into audio routes):
15 Pins on the device (for linking into audio routes):
16 Pins on the device (for linking into audio routes):
23 Pins on the device (for linking into audio routes) for I2C:
3 This node is responsible for linking together all ux500 Audio Driver components.
29 Pins on the device (for linking into audio routes):
29 Pins on the device (for linking into audio routes) for RT5660:
30 Pins on the device (for linking into audio routes) for RT5668B:
30 Pins on the device (for linking into audio routes) for RT5682:
36 Pins on the device (for linking into audio routes) for RT5651:
37 Pins on the device (for linking into audio routes) for RT5659/RT5658:
44 Pins on the device (for linking into audio routes) for RT5659/RT5658:
39 Pins on the device (for linking into audio routes):
39 Pins on the device (for linking into audio routes) for RT5663:
46 Pins on the device (for linking into audio routes):
41 Pins on the device (for linking into audio routes) for RT5645/RT5650:
2 * Common module linker script, always used when linking a module.
10 processors(PDSP), linking RAM, descriptor pools and infrastructure18 The QMSS driver manages the PDSP setups, linking RAM regions,
43 Those objects are then used in final linking:
51 Additional options used for $(LD) when linking modules.63 Additional flags to be passed when linking host programs.194 symbols in the final module linking stage. It changes such errors
