comparison src/cs/layer1/tpu_drivers/source0/tpudrv12.h @ 685:3fb7384e820d

tpudrv12.h: FCDEV3B goes back to being itself A while back we had the idea of a FreeCalypso modem family whereby our current fcdev3b target would some day morph into fcmodem, with multiple FC modem family products, potentially either triband or quadband, being firmware-compatible with each other and with our original FCDEV3B. But in light of the discovery of Tango modules that earlier idea is now being withdrawn: instead the already existing Tango hw is being adopted into our FreeCalypso family. Tango cannot be firmware-compatible with triband OM/FCDEV3B targets because the original quadband RFFE on Tango modules is wired in TI's original Leonardo arrangement. Because this Leonardo/Tango way is now becoming the official FreeCalypso way of driving quadband RFFEs thanks to the adoption of Tango into our FC family, our earlier idea of extending FIC's triband RFFE control signals with TSPACT5 no longer makes much sense - we will probably never produce any new hardware with that once-proposed arrangement. Therefore, that triband-or-quadband FCFAM provision is being removed from the code base, and FCDEV3B goes back to being treated the same way as CONFIG_TARGET_GTAMODEM for RFFE control purposes.
author Mychaela Falconia <falcon@freecalypso.org>
date Thu, 24 Sep 2020 21:03:08 +0000
parents 026c98f757a6
children e0feeea32ca5
comparison
equal deleted inserted replaced
684:269554439ace 685:3fb7384e820d
273 #define RU_1900 ( PA_OFF | FEM_PINS ^ 0 ) 273 #define RU_1900 ( PA_OFF | FEM_PINS ^ 0 )
274 #define RD_1900 ( PA_OFF | FEM_PINS ^ 0 ) 274 #define RD_1900 ( PA_OFF | FEM_PINS ^ 0 )
275 #define TU_1900 ( PA_HI_BAND | FEM_PINS ^ FEM_8 ) 275 #define TU_1900 ( PA_HI_BAND | FEM_PINS ^ FEM_8 )
276 #define TD_1900 ( PA_OFF | FEM_PINS ^ 0 ) 276 #define TD_1900 ( PA_OFF | FEM_PINS ^ 0 )
277 277
278 #elif defined(CONFIG_TARGET_GTAMODEM) 278 #elif defined(CONFIG_TARGET_GTAMODEM) || defined(CONFIG_TARGET_FCDEV3B)
279 279
280 // Openmoko's triband configuration is a bastardized version 280 // Openmoko's triband configuration is a bastardized version
281 // of TI's quadband one from Leonardo/E-Sample 281 // of TI's quadband one from Leonardo/E-Sample
282 282
283 #define FEM_7 BIT_2 // act2 283 #define FEM_7 BIT_2 // act2
314 314
315 #define RU_1900 ( PA_OFF | FEM_PINS ^ FEM_8 ) 315 #define RU_1900 ( PA_OFF | FEM_PINS ^ FEM_8 )
316 #define RD_1900 ( PA_OFF | FEM_PINS ^ 0 ) 316 #define RD_1900 ( PA_OFF | FEM_PINS ^ 0 )
317 #define TU_1900 ( PA_HI_BAND | FEM_PINS ^ FEM_7 ) 317 #define TU_1900 ( PA_HI_BAND | FEM_PINS ^ FEM_7 )
318 #define TD_1900 ( PA_OFF | FEM_PINS ^ 0 ) 318 #define TD_1900 ( PA_OFF | FEM_PINS ^ 0 )
319
320 #elif defined(CONFIG_TARGET_FCFAM)
321
322 /*
323 * In our FreeCalypso hw family, we would like to be able to use
324 * both triband and quadband RFFEs. Our current FCDEV3B is triband,
325 * copied from Openmoko, and the same is expected to be the case for
326 * future low-budget designs, but if someone pays for a new RF layout,
327 * we can use a quadband RFFE instead. If we ever have two different
328 * hw platforms or variants that differ in the RFFE but are otherwise
329 * firmware-compatible, we would like to have the same fw build
330 * work with both triband and quadband RFFEs. How is it possible?
331 * The trick is that we define our set of TSPACT RFFE control signals
332 * starting with our current OM-based triband version, and add one
333 * more signal to support potential future quadband designs.
334 */
335
336 #define FEM_RX_1900 BIT_1 // act1
337 #define FEM_TX_HIGH BIT_2 // act2
338 #define FEM_TX_LOW BIT_4 // act4
339 #define FEM_RX_850 BIT_5 // act5
340
341 #define PA_HI_BAND BIT_3 // act3
342 #define PA_LO_BAND 0
343 #define PA_OFF 0
344
345 #define FEM_PINS (FEM_TX_LOW | FEM_TX_HIGH | FEM_RX_850 | FEM_RX_1900)
346
347 #define FEM_OFF ( FEM_PINS ^ 0 )
348
349 #define FEM_SLEEP ( 0 )
350
351 // This configuration is always inverted.
352
353 // RX_UP/DOWN and TX_UP/DOWN
354 #define RU_900 ( PA_OFF | FEM_PINS ^ 0 )
355 #define RD_900 ( PA_OFF | FEM_PINS ^ 0 )
356 #define TU_900 ( PA_LO_BAND | FEM_PINS ^ FEM_TX_LOW )
357 #define TD_900 ( PA_OFF | FEM_PINS ^ 0 )
358
359 #define RU_850 ( PA_OFF | FEM_PINS ^ FEM_RX_850 )
360 #define RD_850 ( PA_OFF | FEM_PINS ^ 0 )
361 #define TU_850 ( PA_LO_BAND | FEM_PINS ^ FEM_TX_LOW )
362 #define TD_850 ( PA_OFF | FEM_PINS ^ 0 )
363
364 #define RU_1800 ( PA_OFF | FEM_PINS ^ 0 )
365 #define RD_1800 ( PA_OFF | FEM_PINS ^ 0 )
366 #define TU_1800 ( PA_HI_BAND | FEM_PINS ^ FEM_TX_HIGH )
367 #define TD_1800 ( PA_OFF | FEM_PINS ^ 0 )
368
369 #define RU_1900 ( PA_OFF | FEM_PINS ^ FEM_RX_1900 )
370 #define RD_1900 ( PA_OFF | FEM_PINS ^ 0 )
371 #define TU_1900 ( PA_HI_BAND | FEM_PINS ^ FEM_TX_HIGH )
372 #define TD_1900 ( PA_OFF | FEM_PINS ^ 0 )
373 319
374 #elif defined(CONFIG_TARGET_MGC2GSMT) 320 #elif defined(CONFIG_TARGET_MGC2GSMT)
375 321
376 /* 322 /*
377 * The common MGC2GSMT version of Huawei GTM900-B is very closely based 323 * The common MGC2GSMT version of Huawei GTM900-B is very closely based