Tony,
> -----Original Message-----
> From: Shilimkar, Santosh
> Sent: Monday, August 16, 2010 7:34 PM
> To: linux-omap@vger.kernel.org
> Cc: p...@pwsan.com; khil...@deeprootsystems.com; Cousson, Benoit;
> Shilimkar, Santosh
> Subject: [PATCH 0/4] omap4: Control module series
>
> On omap4 control mudule is divided in four IP blocks.
> CTRL_MODULE_CORE 0x4a002000
> PAD_CTRL_MODULE_CORE 0x4a100000
> CTRL_MODULE_WKUP 0x4a30c000
> PAD_CTRL_MODULE_WKUP 0x4a31e000
> Addressing all the modules with single base address is not possible
> considering 16 bit offsets. The mux code manages the pad core and pad
> wakeup related base address inside the mux framework. For other usage
> only control core and control pad bases are necessary.
>
> After some offline discussion with Tony, Paul and Benoit, following
> approach
> is decided to address this issue.
> - Most usable registers are form CTRL_MODULE_CORE and
> PAD_CTRL_MODULE_CORE
> - Control core is mapped with existing APIs and to address the pad
> control
> module registers, a new accessor APIs is exported for OMAP4 only.
> - Mux code maps the needed bases internally so they need not be exported.
>
> Thanks to,
> - Tony and Paul for there suggestion to manage this problem.
> - And ofcourse Benoit to work with me on this series
>
> The series is generated against 2.6.36-rc1 + Tony's fixes below series
> - [PATCH 0/6] omap fixes for upcoming 2.6.36-rc1
> http://www.spinics.net/lists/linux-omap/msg34830.html
>
> It's tested on tested on OMAP4 and OMAP3 SDPs.
>
> Santosh Shilimkar (4):
> omap4: control: Add ctrl_pad_base to omap_globals
> omap4: control: Add accessor api's for pad control module
> omap4: control: Add the register definition headers
> omap4: control: Fix the control module register accesses
>
Can you please see if this is good for merge in LO master?
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
