With just 12 interface lines, this looks an ideal match to a Pin-Constrained P2 package.It may even work with P1V.
They appear to have some strange constraints on auto-refresh windows, but then they say ["The host system may also effectively increase the tCMS value by explicitly taking responsibility for performing all refresh and doing burst refresh reading of multiple sequential rows in order to catch up on distributed refreshes missed by longer transactions."]
["Table 5.7 Array Refresh Interval per Temperature
Device Temperature (°C) Array Refresh Interval
(ms) Array Rows Recommended tCMS (µs) 85 64 8192 4 105 16 8192 1
A 60Hz video scan, is well inside 85°C spec, and reaches almost to the 105°C corner, and should refresh-as-scanned (but limits RAM usage to the displayed area).
There looks to be a simple linear streaming read mode, similar to QuadSPI parts, which is well suited to Video streaming / Buffering.
[" Linear transactions are generally used for large contiguous data transfers such as graphic
image moves. When configured in linear burst mode, the device will automatically fetch the next sequential row from the memory array to support a continuous linear burst. Simultaneously accessing the next row in the array while the read or write data transfer is in progress, allows for a linear sequential burst operation that can provide a sustained data rate of 333 MB/s (1 byte (8 bit data bus) * 2
(data clock edges) * 166 MHz = 333 MB/s)."]
and this sounds like a possible fish-hook, but there seems a way to force fixed latency ?["In the event a distributed refresh is required at the time a Memory Space read or write transaction or Register Space read transaction begins, the RWDS signal goes high during the Command-Address to indicate that an additional initial latency is being inserted to allow a refresh operation to complete before opening the selected row"]