SPRZ530D April   2022  – June 2026 AM68 , AM68A , TDA4AL-Q1 , TDA4VE-Q1 , TDA4VL-Q1

 

  1.   1
  2. 1Modules Affected
  3. 2Nomenclature, Package Symbolization, and Revision Identification
    1. 2.1 Device and Development-Support Tool Nomenclature
    2. 2.2 Devices Supported
    3. 2.3 Package Symbolization and Revision Identification
  4. 3Silicon Revision 1.0 Usage Notes and Advisories
    1. 3.1 Silicon Revision 1.0 Usage Notes
      1.      i2134
    2. 3.2 Silicon Revision 1.0 Advisories
      1.      i2049
      2.      i2062
      3.      i2063
      4.      i2064
      5.      i2065
      6.      i2079
      7.      i2087
      8.      i2091
      9.      i2097
      10.      i2103
      11.      i2120
      12.      i2134
      13.      i2137
      14.      i2146
      15.      i2157
      16.      i2159
      17.      i2160
      18.      i2161
      19.      i2163
      20.      i2166
      21.      i2177
      22.      i2189
      23.      i2190
      24.      i2196
      25.      i2197
      26.      i2205
      27.      i2215
      28.      i2216
      29.      i2219
      30.      i2232
      31.      i2234
      32.      i2235
      33.      i2237
      34.      i2242
      35.      i2243
      36.      i2244
      37.      i2249
      38.      i2253
      39.      i2271
      40.      i2272
      41.      i2278
      42.      i2279
      43.      i2283
      44.      i2307
      45.      i2308
      46.      i2310
      47.      i2311
      48.      i2312
      49.      i2313
      50.      i2316
      51.      i2320
      52.      i2326
      53.      i2329
      54.      i2330
      55.      i2351
      56.      i2362
      57.      i2366
      58.      i2371
      59.      i2372
      60.      i2378
      61.      i2381
      62.      i2383
      63.      i2399
      64.      i2401
      65.      i2409
      66.      i2413
      67.      i2414
      68.      i2415
      69.      i2418
      70.      i2419
      71.      i2422
      72.      i2424
      73.      i2431
      74.      i2435
      75.      i2436
      76.      i2437
      77.      i2454
      78.      i2449
      79.      i2482
  5.   Trademarks
  6.   Revision History

i2196

IA: Potential deadlock scenarios in IA

Details:

The interrupt Aggregator (IA) has one main function, which is to convert events arriving on the Event Transport Lane (ETL) bus, can convert them to interrupt status bits which are used to generate level interrupts. The block that performed this function in IA version 1.0 was called the status event block.

In addition to the status event block, there are two other main processing blocks; the multicast event block, and the counted event block. The multicast block really functions as an event splitter. For every event it takes in, it can generate two output events. The counted event block is used to convert high frequency events into a readable count. It counts input events and generates output events on count transitions to/from 0 to/from non-zero count values. Unlike the status event block, the multicast and counted event blocks generate output ETL events that are then mapped to other processing blocks.

An issue was found after design that could cause the IA to deadlock. The issue occurs when event “loops” occur between these three processing blocks. It is possible to create a situation where a processing block can not output an event because the path is blocked, and since it can not output an event, it can not take any new input events. This inability to take input events prevents the output path from being able to unwind, and thus both paths remain blocked.

Workaround(s):

Figure 3-3 shows the conceptual block diagram of IA 1.0. Potential loops are avoided by adopting the policy of not allowing the counted event block to send events to the multicast block. This method was chosen because it is more common to split an event first, and then count one while sending the other elsewhere. With this path blocked by convention, it is not possible for a single event to visit any block more than once and thus not possible for paths to become blocked so long as the outputs remain unblocked.

 Interrupt Aggregator Version 1.0 Figure 3-3 Interrupt Aggregator Version 1.0

By following the conventions outlined here, the system is safe from looping hazards that can create a deadlock scenario.