linux-kernel - Re: [PATCH] AT91: manage clock by functionality instead of CPUs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 31 Mar 2009 14:51:49 +0200
From:	Nicolas Ferre <nicolas.ferre@...el.com>
To:	ARM Linux Mailing List <linux-arm-kernel@...ts.arm.linux.org.uk>
CC:	Andrew Victor <avictor.za@...il.com>,
	Linux Kernel list <linux-kernel@...r.kernel.org>,
	David Brownell <david-b@...bell.net>,
	Ville Syrjälä <syrjala@....fi>
Subject: Re: [PATCH] AT91: manage clock by functionality instead of CPUs

Nicolas Ferre :
> In clock.c file the clock management is grouped by cpu with cpu_is_xxx()
> function. This lead to some kind of difficulties to read this file and
> maintainability issues as the number of AT91 cpus & PLLs/clocks is growing.
> 
> In this patch, I try to group clock functionality together and match cpus with
> this functionality set.
> An update to at91_pmc.h is needed to cover some new PMC possibilities (and
> some update in comments).
> 
> Signed-off-by: Nicolas Ferre <nicolas.ferre@...el.com>
> ---
>  arch/arm/mach-at91/clock.c                 |  151 ++++++++++++++++++++-------
>  arch/arm/mach-at91/include/mach/at91_pmc.h |   26 ++++-
>  2 files changed, 132 insertions(+), 45 deletions(-)

I forget to add in my previous email:

Acked-by: Andrew Victor <avictor.za@...il.com>

Ok, as we have no more comment, I submit it to the patch system.

Regards,
-- 
Nicolas Ferre

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/