FreeCalypso > hg > fc-selenite

comparison src/cs/layer1/tpu_drivers/source0/tpudrv12.h @ 163:a911ac771094

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
board preprocessor conditionals: prep for more FC hw in the future Please see the corresponding change in fc-magnetite for the explanation.
author Mychaela Falconia <falcon@freecalypso.org>
date Mon, 01 Apr 2019 01:20:03 +0000
parents df9c471ce9e9
children 7409b22cac61
comparison
equal deleted inserted replaced
162:8c5d012b9c4d 163:a911ac771094
272 #define RU_1900 ( PA_OFF | FEM_PINS ^ 0 ) 272 #define RU_1900 ( PA_OFF | FEM_PINS ^ 0 )
273 #define RD_1900 ( PA_OFF | FEM_PINS ^ 0 ) 273 #define RD_1900 ( PA_OFF | FEM_PINS ^ 0 )
274 #define TU_1900 ( PA_HI_BAND | FEM_PINS ^ FEM_8 ) 274 #define TU_1900 ( PA_HI_BAND | FEM_PINS ^ FEM_8 )
275 #define TD_1900 ( PA_OFF | FEM_PINS ^ 0 ) 275 #define TD_1900 ( PA_OFF | FEM_PINS ^ 0 )
276 276
277 #elif defined(CONFIG_TARGET_GTAMODEM) || defined(CONFIG_TARGET_FCDEV3B) 277 #elif defined(CONFIG_TARGET_GTAMODEM)
278 278
279 // Openmoko's triband configuration is a bastardized version 279 // Openmoko's triband configuration is a bastardized version
280 // of TI's quadband one from Leonardo/E-Sample 280 // of TI's quadband one from Leonardo/E-Sample
281 281
282 #define FEM_7 BIT_2 // act2 282 #define FEM_7 BIT_2 // act2
320 320
321 /* 321 /*
322 * In our FreeCalypso hw family, we would like to be able to use 322 * In our FreeCalypso hw family, we would like to be able to use
323 * both triband and quadband RFFEs. Our current FCDEV3B is triband, 323 * both triband and quadband RFFEs. Our current FCDEV3B is triband,
324 * copied from Openmoko, and the same is expected to be the case for 324 * copied from Openmoko, and the same is expected to be the case for
325 * future low-cost designs, but if someone pays for a new RF layout, 325 * future low-budget designs, but if someone pays for a new RF layout,
326 * we can use a quadband RFFE instead. If we ever have two different 326 * we can use a quadband RFFE instead. If we ever have two different
327 * hw platforms or variants that differ in the RFFE but are otherwise 327 * hw platforms or variants that differ in the RFFE but are otherwise
328 * firmware-compatible, we would like to have the same fw build 328 * firmware-compatible, we would like to have the same fw build
329 * work with both triband and quadband RFFEs. How is it possible? 329 * work with both triband and quadband RFFEs. How is it possible?
330 * The trick is that we define our set of TSPACT RFFE control signals 330 * The trick is that we define our set of TSPACT RFFE control signals