Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

This project is archived. Its data is read-only.

Commit 8c810e7e authored Feb 25, 2011 by Paul Walmsley

OMAP2xxx: clock data: clean up some comments



Minor cleanup of some clock data comments.  No functional changes.

Signed-off-by: Paul Walmsley <paul@pwsan.com>

parent a4fc9274

arch/arm/mach-omap2/clock2420_data.c

+10 −13

Original line number	Diff line number	Diff line
		/*
		* linux/arch/arm/mach-omap2/clock2420_data.c
		* OMAP2420 clock data
		*
		* Copyright (C) 2005-2009 Texas Instruments, Inc.
		* Copyright (C) 2004-2011 Nokia Corporation
		@@ -34,18 +34,15 @@
		/*
		* 2420 clock tree.
		*
		* NOTE:In many cases here we are assigning a 'default' parent. In many
		* cases the parent is selectable. The get/set parent calls will also
		* switch sources.
		*
		* Many some clocks say always_enabled, but they can be auto idled for
		* power savings. They will always be available upon clock request.
		* NOTE:In many cases here we are assigning a 'default' parent. In
		* many cases the parent is selectable. The set parent calls will
		* also switch sources.
		*
		* Several sources are given initial rates which may be wrong, this will
		* be fixed up in the init func.
		*
		* Things are broadly separated below by clock domains. It is
		* noteworthy that most periferals have dependencies on multiple clock
		* noteworthy that most peripherals have dependencies on multiple clock
		* domains. Many get their interface clocks from the L4 domain, but get
		* functional clocks from fixed sources or other core domain derived
		* clocks.

arch/arm/mach-omap2/clock2430_data.c

+10 −13

Original line number	Diff line number	Diff line
		/*
		* linux/arch/arm/mach-omap2/clock2430_data.c
		* OMAP2430 clock data
		*
		* Copyright (C) 2005-2009 Texas Instruments, Inc.
		* Copyright (C) 2004-2011 Nokia Corporation
		@@ -34,18 +34,15 @@
		/*
		* 2430 clock tree.
		*
		* NOTE:In many cases here we are assigning a 'default' parent. In many
		* cases the parent is selectable. The get/set parent calls will also
		* switch sources.
		*
		* Many some clocks say always_enabled, but they can be auto idled for
		* power savings. They will always be available upon clock request.
		* NOTE:In many cases here we are assigning a 'default' parent. In
		* many cases the parent is selectable. The set parent calls will
		* also switch sources.
		*
		* Several sources are given initial rates which may be wrong, this will
		* be fixed up in the init func.
		*
		* Things are broadly separated below by clock domains. It is
		* noteworthy that most periferals have dependencies on multiple clock
		* noteworthy that most peripherals have dependencies on multiple clock
		* domains. Many get their interface clocks from the L4 domain, but get
		* functional clocks from fixed sources or other core domain derived
		* clocks.