Enforcing built-in driver init order?

Enforcing built-in driver init order?

[Matt Sealey]

I'm trying to work out how to decouple the BestComm SRAM driver from the
BestComm DMA engine. SRAM is far more useful than just as a DMA buffer,
especially as it can stay active over deep sleep and SDRAM refresh turned
off, as a temporary place to put things. Even with a full set of tasks
there are still some kilobytes free. In future processors the SRAM will
only get larger meaning you can do more things with it, and it may be
used for more than DMA.

My simple problem is, if I split the two drivers apart, the SRAM platform
driver is not guaranteed to load before the DMA platform driver. If it
were a module I could have depmod handle it and load them in order but
this isn't possible since DMA is required on boot, and SRAM is required
for DMA.

Any clues or hints on how it can be EASILY enforced that the SRAM platform
driver is present (and can be checked for??) before the BestComm engine
is turned on and tasks are arbitrarily loaded?

-- 
Matt Sealey <matt@genesi-usa.com>
Genesi, Manager, Developer Relations