FreeCalypso > hg > fc-selenite

comparison src/cs/layer1/tpu_drivers/source0/tpudrv12.h @ 205:89aa29293ded

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
tpudrv12.h: sync with Magnetite
author Mychaela Falconia <falcon@freecalypso.org>
date Tue, 13 Oct 2020 01:07:46 +0000
parents d05fb947b50d
children 7751f14fa759
comparison
equal deleted inserted replaced
204:027b22814ac4 205:89aa29293ded
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