[email protected] writes: > From: Thomas Koeller <[email protected]> > > Keeping track of resource assignments greatly simplifies > the task of writing board support code. Many drivers for > DaVinci peripherals were using resources that had never > been allocated, with the notable exception of memory > resources. > > Non-conflicting resource assignment is a responsibility > of the bus the devices are on, in this case, the platform bus. > > The resource management scheme implemented by this patch is not > perfect. The SoC code really has no business managing resources, > it should only provide them to the platform (board support) code. > The board support is the only place where information about the > intended use of the various hardware resources is available.
Actually, the driver is the place where the resources are used and therefore where they should be reserved and released. This patch removes this from the drivers and puts it in SoC code which I don't like. There are really two main things going on here that I see: 1. add parent resources (cfg, irq, dma, etc.) 2. move resource reservation from drivers to SoC code It's primarily 2 that I object to. While I think (1) may be helpful, if we're going to do it, we should do it throughout all of mach-davinci/*. Kevin _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
