01.08.2013 Views

Chapter 10 Memory Subsystem.pdf

Chapter 10 Memory Subsystem.pdf

Chapter 10 Memory Subsystem.pdf

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Public Version<br />

SDRAM Controller (SDRC) <strong>Subsystem</strong> www.ti.com<br />

SDRC_SIDLEACK signal and the input clock frequency can be changed or stopped, depending on the<br />

scenario. After the input clock is stable again, SDRC_IDLEREQ is de-asserted. The DLL then relocks and<br />

the SDRC can be accessed normally. Putting the DLL in idle mode during the clock frequency change is<br />

required because it cannot automatically relock. It might get into a non-functional state and a new manual<br />

DLL configuration phase would then be required, with the risk of corrupting accesses in the mean time.<br />

<strong>10</strong>.2.4 SDRC <strong>Subsystem</strong> Functional Description<br />

The SMS optimizes the SDRAM memory usage to provide:<br />

• The QoS level required by each of the initiators in the system<br />

• A VRFB module (also called the 2D rotation engine) that minimizes the SDRAM page-miss penalty<br />

when accessing rotated (that is, nonsequentially addressed) lines in a graphic frame buffer<br />

<strong>10</strong>.2.4.1 SDRAM <strong>Memory</strong> Scheduler<br />

The SMS module is split into the following subsystems:<br />

• L3 interconnect slave port<br />

• VRFB: Rotation engine (RE)<br />

• Configuration register file<br />

• Request buffers<br />

• Arbitration logic<br />

• SDRC interface: master port<br />

• Debug port<br />

• Response buffer<br />

Figure <strong>10</strong>-48 shows the top-level diagram of the SMS.<br />

2218 <strong>Memory</strong> <strong>Subsystem</strong> SPRUGN4L–May 20<strong>10</strong>–Revised June 2011<br />

Copyright © 20<strong>10</strong>–2011, Texas Instruments Incorporated

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!