On Tue, 29 Nov 2011, Cousson, Benoit wrote: > On 11/27/2011 3:07 AM, Paul Walmsley wrote: > > > So just out of curiosity, do those SYSCONFIG registers in the STM address > > space apply to the entire DEBUGSS, or just the STM IP block? > > The STM IP is the only one to have the TI generic wrapper to be compliant with > TI standards. > But in term of PRCM, there is only one IP, the DEBUGSS. > There are probably a bunch of internal clock management inside it that are not > exposed to PRCM. > > The confusing part is that in theory all these entries can be accessed by the > same OCP port, and should potentially have this flags. > The point is that for the moment, we are mainly using that flag to get the > SYSCONFIG. > We already discussed that, but I think we should modify this flag to highlight > the SYSCONFIG / SYSSTATUS availability. > Maybe with something like ADDR_SYSCONFIG? > > Any thought? Well, the ADDR_TYPE_RT flag in this hwmod would indicate the address space of the DEBUGSS's OCP header registers, not the MIPI STM's OCP header registers. So if the MIPI STM's OCP header registers also control the entire DEBUGSS power management, then the current layout makes sense. Otherwise, the MIPI STM should be created as a separate hwmod. It appears to me that the DEBUGSS has no OCP header registers of its own. Upon reflection, rather than creating a macro hwmod for the DEBUGSS, it seems to make more sense to add hwmods for its two internal interconnects, then to create another hwmod for the MIPI STM device. - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
