LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Cc: "Andrew Victor" <avictor.za@gmail.com>,
	lkml <linux-kernel@vger.kernel.org>,
	"Haavard Skinnemoen" <hskinnemoen@atmel.com>,
	"Nicolas Ferre" <nicolas.ferre@rfo.atmel.com>
Subject: Re: [patch 2.6.28-rc2] atmel_serial: keep clock off when it's not needed
Date: Wed, 29 Oct 2008 08:54:15 -0700	[thread overview]
Message-ID: <200810290854.15506.david-b@pacbell.net> (raw)
In-Reply-To: <20081029110845.309a7548@hskinnemo-gx745.norway.atmel.com>

On Wednesday 29 October 2008, Haavard Skinnemoen wrote:
> David Brownell <david-b@pacbell.net> wrote:
> > On Tuesday 28 October 2008, Andrew Victor wrote:
> > > 
> > > > I verified it on AT91, where the console is normally DBGU and the
> > > > other USARTs do get an open().
> > > 
> > > The DBGU is part of the system peripherals, which are clocked from MCK
> > > and which is always enabled.
> > 
> > Exactly.
> 
> Exactly what?

Exactly the point I was making by describing the testing:
it covered "normal" behavior where the console was clocked
when Linux started.  But not the case you described.


> That your patch has exactly zero effect on your test case? 

Hardly; if that were the case, I wouldn't have posted it!

The other UARTs' clocks again behaved correctly during normal
operation ... acting like they did a few years ago when last I
happened to look at how clocks interacted with this driver.
(Or maybe "with its predecessor".)


> > > Therefore I don't think this is a valid test-case.
> > 
> > Not for the oddball case Haavard mentioned, no:  the console port
> > being something the boot loader wasn't using, which couldn't show
> > the early boot messages (before console setup) in any case.  Those
> > kinds of systems aren't especially debuggable (it's JTAG or nothing).
> 
> Since when is it acceptable to lock up solid in "oddball" cases?

I'm not sure why you're asking *me* that, instead of some
person who said it was OK.  I pointed out that a system
configured like that would have a lot more rude failure
modes than just the one you were pointing out.  Enough to
ensure such configurations wouldn't find much use at all.


> Not to work
> mention that I don't think this is an "oddball" case at all -- the
> bootloader has absolutely _no_ way of influencing the initial enable
> count of the clock, so the kernel will turn it off as soon as it gets
> the chance.

That's a nuance that the platform's clock code needs to handle.

Rule of thumb:  don't turn off "unused" clocks until late in the
system boot sequence ... when drivers for various devices, like
the console, have been fully initialized.  Else you'll turn off
something that was used implicitly during booting:  clocks for
intermediate busses, boot media, console, etc.


> > I don't have any issue with getting that fixed too ... but unless
> > someone has a platform that relies on that case (or can be made to
> > do so, for testing), then it's hard for me to worry about it!
> 
> David, I can't believe you're taking such an easy attitude towards
> basic correctness!

Call it pragmatism.  In a choice between fixing a bug that's been
observed to happen, or not doing so because of an issue that's never
been observed (and won't appear on production systems) ... I'd fix
the bug, and worry about that issue later (if at all).


> I agree that the clock management is already wrong, but keeping a
> couple of clocks enabled when they could have been disabled is far less
> of a problem than locking up the console.

And I asked what systems would actually see such a lockup.  What
system will let me talk to the boot loader on a console, telling
it how to boot, but then lock up when it gets into Linux?


> I also understand if you don't want to fix the console issue I pointed
> out, but I'm surprised that you aren't even willing to acknowledge the
> problem, brushing it off with words like "normally" and "as a rule".

Reread the words of mine that you quoted above; I acknowledged the
issue but can't see it being critical.

- Dave

      reply	other threads:[~2008-10-29 15:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-27 21:06 David Brownell
2008-10-28 11:45 ` Haavard Skinnemoen
2008-10-28 16:20   ` David Brownell
2008-10-28 16:37     ` Haavard Skinnemoen
2008-10-28 17:08       ` David Brownell
2008-10-28 17:48         ` Haavard Skinnemoen
2008-10-28 18:41     ` Andrew Victor
2008-10-28 19:51       ` David Brownell
2008-10-29 10:08         ` Haavard Skinnemoen
2008-10-29 15:54           ` David Brownell [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200810290854.15506.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=avictor.za@gmail.com \
    --cc=haavard.skinnemoen@atmel.com \
    --cc=hskinnemoen@atmel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.ferre@rfo.atmel.com \
    --subject='Re: [patch 2.6.28-rc2] atmel_serial: keep clock off when it'\''s not needed' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).