* Shilimkar, Santosh <santosh.shilimkar@xxxxxx> [091129 02:02]: > > -----Original Message----- > > From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap- > > owner@xxxxxxxxxxxxxxx] On Behalf Of Tony Lindgren > > Sent: Thursday, November 26, 2009 5:49 AM > > To: linux-arm-kernel@xxxxxxxxxxxxxxxxxxx > > Cc: linux-omap@xxxxxxxxxxxxxxx; Mike Rapoport > > Subject: [PATCH 1/8] omap2: mux: intoduce omap_mux_{read,write} > > > > From: Mike Rapoport <mike@xxxxxxxxxxxxxx> > > > > intoduce omap_mux_{read,write} <snip> > > int __init omap2_mux_init(void) > > { > > + u32 mux_pbase; > > + > > + if (cpu_is_omap2420()) > > + mux_pbase = OMAP2420_CTRL_BASE + OMAP_MUX_BASE_OFFSET; > > + else if (cpu_is_omap2430()) > > + mux_pbase = OMAP243X_CTRL_BASE + OMAP_MUX_BASE_OFFSET; > > + else if (cpu_is_omap34xx()) > > + mux_pbase = OMAP343X_CTRL_BASE + OMAP_MUX_BASE_OFFSET; > > + > > + mux_base = ioremap(mux_pbase, OMAP_MUX_BASE_SZ); > > The control modules on OMAP's divided into 2 domains with different base address > 1. pads in CORE power domain > 2. Pads in wakeup domain. > > If we map these two separately, then we can differentiate the wakeup capable pads. > Not sure whether I am making any sense here but just thought it would be useful. OK, maybe we can consider doing that later on. If we separate the core and wakeup domains for muxing, we should do it in a way where it's transparent to the users. Otherwise the the muxing again gets confusing easily if we have separate sets of functions for the core and wakeup domains. Regards, Tony -- 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
