linux-kernel - Re: [patch 2.6.28-rc2] atmel_serial: keep clock off when it's not needed

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20081028173733.7ba951de@hskinnemo-gx745.norway.atmel.com>
Date:	Tue, 28 Oct 2008 17:37:33 +0100
From:	Haavard Skinnemoen <haavard.skinnemoen@...el.com>
To:	David Brownell <david-b@...bell.net>
Cc:	lkml <linux-kernel@...r.kernel.org>,
	Nicolas Ferre <nicolas.ferre@....atmel.com>,
	Andrew Victor <linux@...im.org.za>
Subject: Re: [patch 2.6.28-rc2] atmel_serial: keep clock off when it's not
 needed

David Brownell <david-b@...bell.net> wrote:
> On Tuesday 28 October 2008, Haavard Skinnemoen wrote:
> > David Brownell <david-b@...bell.net> wrote:
> > > From: David Brownell <dbrownell@...rs.sourceforge.net>
> > > 
> > > The atmel_serial driver is mismanaging its clock by leaving it on
> > > at all times ... the whole point of clock management is to leave
> > > it off unless it's actively needed, which conserves power!!
> > > 
> > > Signed-off-by: David Brownell <dbrownell@...rs.sourceforge.net>
> > 
> > Hmm...the only remaining clk_enable() is in atmel_serial_pm(). Is that
> > really enough?
> > 
> > It looks like the serial core calls ->pm() to power the port up before
> > doing anything that might touch the registers, but I can't see that the
> > console layer does the same thing...
> 
> I verified it on AT91, where the console is normally DBGU and the
> other USARTs do get an open().
> 
> Didn't verify on AVR32, since 2.6.28-rc can't see the root FS because
> of that NOR flash problem.  Though I suppose I can try it on an older
> kernel.
> 
> As a rule the boot loader will be using that USART, and thus will
> have enabled its clock.  :)

Hmm. But in the cases when "normally" and "as a rule" don't apply, the
board will lock up solid with no console output since it will wait
forever for the TXRDY bit to be set...

I'd like to know for sure that it cannot happen, please.

Haavard
--
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/