CONFIG_OMAP4_ERRATA_I688: OMAP4 errata: Async Bridge Corruption

General informations

The Linux kernel configuration item CONFIG_OMAP4_ERRATA_I688:

• prompt: OMAP4 errata: Async Bridge Corruption
• type: bool
• depends on: ( CONFIG_ARCH_OMAP4 || CONFIG_SOC_OMAP5 ) && ! CONFIG_ARCH_MULTIPLATFORM
• defined in arch/arm/mach-omap2/Kconfig
• found in Linux kernels: 3.3–3.19, 4.0

Help text

If a data is stalled inside asynchronous bridge because of back pressure, it may be accepted multiple times, creating pointer misalignment that will corrupt next transfers on that data path until next reset of the system (No recovery procedure once the issue is hit, the path remains consistently broken). Async bridge can be found on path between MPU to EMIF and MPU to L3 interconnect. This situation can happen only when the idle is initiated by a Master Request Disconnection (which is trigged by software when executing WFI on CPU). The work-around for this errata needs all the initiators connected through async bridge must ensure that data path is properly drained before issuing WFI. This condition will be met if one Strongly ordered access is performed to the target right before executing the WFI. In MPU case, L3 T2ASYNC FIFO and DDR T2ASYNC FIFO needs to be drained. IO barrier ensure that there is no synchronisation loss on initiators operating on both interconnect port simultaneously.

Hardware

LKDDb

Raw data from LKDDb:

• (none)

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: