Hi Stephen, On Thu, Jan 12, 2012 at 3:43 PM, Stephen Warren <swar...@nvidia.com> wrote: > Simon Glass wrote at Thursday, January 12, 2012 4:17 PM: >> On Tue, Jan 10, 2012 at 9:56 AM, Stephen Warren <swar...@nvidia.com> wrote: >> > On 12/26/2011 12:33 PM, Simon Glass wrote: >> >> From: Jimmy Zhang <jimmzh...@nvidia.com> >> >> >> >> Power supplies must be adjusted in line with clock frequency. This code >> >> provides a simple routine to set the voltage to allow operation at maximum >> >> frequency. >> >> >> >> Signed-off-by: Simon Glass <s...@chromium.org> >> >> --- >> >> arch/arm/cpu/armv7/tegra2/Makefile | 1 + >> >> arch/arm/cpu/armv7/tegra2/pmu.c | 355 >> >> ++++++++++++++++++++++++++++++++ >> >> arch/arm/include/asm/arch-tegra2/pmu.h | 63 ++++++ >> >> 3 files changed, 419 insertions(+), 0 deletions(-) >> >> create mode 100644 arch/arm/cpu/armv7/tegra2/pmu.c >> >> create mode 100644 arch/arm/include/asm/arch-tegra2/pmu.h >> > >> > This driver appears to be for an I2C-based device, so I assume it'd for >> > a particular PMIC not Tegra's PMC HW module. I imagine this is a driver >> > for the TI TPS6586X, right? >> > >> > As such, naming this "pmu" and putting it into the Tegra directory >> > doesn't make sense. There should be a generic TPS6586X driver, and >> > possibly a separate file and patch to implement the use of that chip in >> > conjunction with Tegra. >> >> Oh dear, but yes you are right. It is a TPS658621C according to my >> schematic. I will leap into this also. > > I believe some number of the devices are compatible, hence the kernel > has a tps6586x driver rather than more individual drivers for each > value of "x".
OK I will follow along with that. Regards, Simon > > -- > nvpublic > _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot