[PATCH v6 0/3] omap3 nand: cleanup exiting platform related code
Ghorai, Sukumar
s-ghorai at ti.com
Fri Jul 9 06:59:32 EDT 2010
Tony,
> -----Original Message-----
> From: Tony Lindgren [mailto:tony at atomide.com]
> Sent: Friday, July 09, 2010 2:03 PM
> To: Ghorai, Sukumar
> Cc: linux-omap at vger.kernel.org; linux-mtd at lists.infradead.org
> Subject: Re: [PATCH v6 0/3] omap3 nand: cleanup exiting platform related
> code
>
> * Sukumar Ghorai <s-ghorai at ti.com> [100709 10:19]:
> > The following set of patches applies on top of for-next branch.
> > http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git
> > Patches verified on: omap3430-SDP, omap3630-sdp, zoom3 and beagle
> board
> >
> > And these are the patches required to address the following input -
> > 1. The NAND driver needs to stop tinkering with the GPMC registers
> > The omap General Purpose Memory Controller (GPMC) registers are omap
> > specific, and not driver specific. Tinkering with these
> registers can
> > cause issues with the other devices on the GPMC.
> >
> > 2. Passing hardcoded GPMC_CS0_BASE needs to go from the board files
> > Passing hardcoded GPMC virtual addressess is sure way to mess up
> things.
> > This should all become unnecessary once the NAND drivers stops
> messing
> > with the GPMC registers directly.
>
> Looks good to me, thanks for doing this.
>
> One more request: Please repost this series one more time with linux-arm-
> kernel
> mailing list Cc'd. Then if no comments, I'll merge this series during the
> next
> merge window.
[Ghorai] Thanks.
And would you please check if you have any input on following patch series? Otherwise I will rework on this and send again. We need those patches in this time.
1. http://www.mail-archive.com/linux-omap@vger.kernel.org/msg30735.html
2. http://www.mail-archive.com/linux-omap@vger.kernel.org/msg31471.html
Regards,
Ghorai
More information about the linux-mtd
mailing list