Platform Porting Guide

Porting Dependency and requirements

Porting Manual

AudioReach is designed with cross-platform requirement in mind. In order to port AudioReach onto desired hardware and software platform, developer are expected to develop platform & OS abstraction layers and hardware & software endpoint modules. In addition, platform should provide execution environment for AudioReach components to run on.

Platform & OS Abstraction Layer

• ARGS OSAL

  Platform specific OSAL implementation is required for porting AudioReach Graph Services and Signal Processing Engine. See Operating System Abstraction Layer for functionalities to be implemented.

  Refer to OSAL API’s and Linux Implementation for more details.

• ARE POSAL

  Custom POSAL implementation must provide implementation for following functionalities.

  • Signal, Mutex, condition var, channel, thread

  • Timer

  • Cache, memory

  • Memory map

  • Data logging (PCM and Binary data),

  • Thread priority mapping

  • Power Voting (MIPS and Memory bandwidth voting)

  Refer to POSAL API’s and Generic and Linux Implementation for more details.

• GPR platform layer

  To implement GPR platform layer refer to Custom Platform Wrapper and Custom Domain ID. See gpr_init_lx_wrapper.c for linux based platform layer.

• GPR datalink layer

  To implement custom datalink layer refer to steps and code example at Custom IPC Data Link or Transport Layer. See gpr_lx.c for linux based datalink layer.

Hardware & Software Endpoint Modules

Reference ALSA Endpoint module to be released soon.

Provide Execution Environment

Platform should provide execution environment for AudioReach components like:

• GSL ( gsl_init() )

• ARE Framework ( spf_framework_pre_init() and spf_framework_post_init() )

For example, as part of AGM initialization ( agm_init() ), GSL and ARE framework can be initialized. Where GSL in turn initializes OS Abstraction layer (OSAL), Audio Calibration Database (ACDB) and other utilities (say for logging data), framework pre init includes initializing Audio Module Data Base (AMDB), Data Logging Service (DLS), Integrated Resource Monitor (IRM) and framework post init initializes Audio Processing Manager (APM) service.

Sample ARE Framework init execution environment

// Sample framework init implementation.
ar_result_t audio_framework_init(void)
{
   ar_result_t result = AR_EOK;

   /* Init global state structure */
   posal_init();

   /* Init gpr infrastructure */
   result = gpr_init();
   if (result != AR_EOK)
   {
     //Handle failure. Update return code.
   }

   // Init spf framwork. Call pre_init() and post_init() functions.
   spf_framework_pre_init();

   spf_framework_post_init();

   printf("spf_framework_init done, framework ready to receive commands.");

   return result;
}