* Mike Turquette <mturquette@xxxxxx> [121011 15:27]: > Quoting Nishanth Menon (2012-10-11 06:33:04) > > On 18:26-20121003, Mike Turquette wrote: > > > From: Mike Turquette <mturquette@xxxxxxxxxx> > > [...] > > > > > > arch/arm/mach-omap2/Makefile | 8 +- > > > arch/arm/mach-omap2/abb.c | 322 +++++++++++++++++++++++++ > > > arch/arm/mach-omap2/abb.h | 94 ++++++++ > > [...] > > > arch/arm/plat-omap/include/plat/voltage.h | 1 + > > > 18 files changed, 699 insertions(+), 37 deletions(-) > > > create mode 100644 arch/arm/mach-omap2/abb.c > > > create mode 100644 arch/arm/mach-omap2/abb.h > > > create mode 100644 arch/arm/mach-omap2/abb36xx_data.c > > > create mode 100644 arch/arm/mach-omap2/abb44xx_data.c > > > > dumb question: with the request to move everything out of mach-omap2 > > directory, do we still want to add more files into mach-omap2? > > > > Not a dumb question at all. I approached this problem by modeling it > after existing voltage layer code (in particular the vp and vc drivers). > > My hope is to get it merged as-is and then bundle the abb code up with > the vp/vc migration to drivers/* when that happens some day. People > using omap36xx and above need this code now, so it seems prudent to take > this approach today. This is needed, but makes moving the vc code to drivers a bit more complex. So we also need a plan to move this all to drivers in the follow up patches. And we need a maintainer for the code. Who is going to be doing all that? 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
