Messages in this thread | | | Subject | Re: Driver for tightly coupled memory | From | Ben Nizette <> | Date | Wed, 17 Sep 2008 09:04:50 +1000 |
| |
On Tue, 2008-09-16 at 15:49 -0700, Alessio Sangalli wrote: > Ben Nizette wrote: > > > If a driver needs a quick FIFO it can attempt to get the RAM for said > > FIFO from the genalloc and fall back to main memory otherwise. Simple, > > flexible, easy :-) > > Well, interesting, that is why I asked here before writing code. > > In this case however, do you imply that a device driver will just do all > the genalloc stuff? In this case it has to know about the TCM details, > and problems may arise if more than one driver wants to use this > feature. Or, are you suggesting to write a small TCM driver that will do > the gen_pool_create() and gen_pool_add() and then export the struct > gen_pool for use by other drivers that may require it?
Generally the genalloc pool will be set up exactly once, at boot, by the platform code. Then yes indeed the pool can be exported for driver use.
--Ben.
| |