linux-kernel - Re: [PATCH C 06/13] OMAP3 clock: DPLLs should enter bypass if new rate is sys

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20090209111922.GA11668@n2100.arm.linux.org.uk>
Date:	Mon, 9 Feb 2009 11:19:22 +0000
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Paul Walmsley <paul@...an.com>
Cc:	linux-arm-kernel@...ts.arm.linux.org.uk,
	linux-kernel@...r.kernel.org, linux-omap@...r.kernel.org,
	Tony Lindgren <tony@...mide.com>
Subject: Re: [PATCH C 06/13] OMAP3 clock: DPLLs should enter bypass if new rate is sys_ck

On Thu, Jan 29, 2009 at 10:47:40PM -0700, Paul Walmsley wrote:
> Hello Russell,
> 
> this E-mail responds to your comments on patches C 04 through C 08.  
> My understanding is that you'd like me to:
> 
> 1. Compress patches C 04 through C 09;

What I would like to see is a clear set of patches (or maybe just a
single patch if appropriate) implementing the bypass DPLL support,
and have it implemented in a common form for both OMAP2 and OMAP3.

In other words, if we're going to have a 'bypass' clock in the DPLL
data, it shouldn't be just an OMAP3 thing.

I suspect it's going to be easier for me to figure out what's going
on, clean up the existing patches and work from them so that they
still fit in the existing series.
--
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/