On Tue, 2012-03-06 at 09:50 -0600, Gross, Andy wrote: > > > On Tue, Mar 6, 2012 at 8:35 AM, Tomi Valkeinen <tomi.valkeinen@xxxxxx> > wrote: > > > I have to say I don't know much about DMM, but my > understanding is that > DMM is a bigger entity, of which TILER is only a small part, > and DMM > manages all memory accesses. > > Can there be other users for the DMM than DRM? I know there > could be > other users for the TILER, and I know you want to combine that > with the > DRM driver, but I'm wondering about the other parts of DMM > than the > TILER. > > Somehow having a DMM driver inside omapdrm sounds strange. > > > The DMM does indeed contain a number of entities. However, the TILER > portion is the only part that requires a driver. All other register > modifications (LISA map settings, EMIF, etc) are done statically in > the loader or u-boot and never changed again. As such, DMM has become > synonymous with TILER. Ok. Well, as I said, I don't know much about that, just sounds rather strange to me =). Does this "DMM has become synonymous" mean that people just started calling TILER DMM, and thus the name has stuck, or are there technical reasons to handle it as DMM in the kernel? If the former, and if TILER is the technically exact name for it, perhaps it would make sense to call it TILER, as that's what (at least I) would be looking for if I read the TRM and try to find the code for the TILER. Tomi
Attachment:
signature.asc
Description: This is a digitally signed message part
