linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: Alan Jenkins <alan-jenkins@tuffmail.co.uk>, linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] cpuidle: avoid singing capacitors
Date: Wed, 05 Mar 2008 09:32:15 -0800	[thread overview]
Message-ID: <47CED91F.4020106@goop.org> (raw)
In-Reply-To: <20080301132924.0dc22b36@mjolnir.drzeus.cx>

Pierre Ossman wrote:
> On Fri, 29 Feb 2008 13:09:05 -0800 (PST)
> Alan Jenkins <alan-jenkins@tuffmail.co.uk> wrote:
>
>   
>> Pierre Ossman wrote:
>>     
>>> Many devices today are of a less than stellar quality, and singing
>>> transistors are a common problem. A high-pitch noise is created, caused
>>> by power fluctuations as the processor enters and leaves deep sleep at
>>> a high frequency.
>>>       
>> Capacitors or transistors?  The subject and the description disagree.
>>
>>     
>
> That should teach me to write commit messages when I'm tired... Capacitors is of course the right answer. :)

More likely inductors, I think.  The coils can vibrate against the coil 
if they haven't been properly potted in something.  Capacitors don't 
really have anything which can "sing".

    J

  reply	other threads:[~2008-03-05 17:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a2itf-5jB-27@gated-at.bofh.it>
2008-02-29 21:09 ` [RFC][PATCH] cpuidle: avoid singing capacitors Alan Jenkins
2008-03-01 12:29   ` Pierre Ossman
2008-03-05 17:32     ` Jeremy Fitzhardinge [this message]
2008-03-05 18:01       ` Pierre Ossman
2008-02-29 18:38 Pierre Ossman
2008-02-29 21:44 ` Lennart Sorensen
2008-03-01 12:31   ` Pierre Ossman
2008-03-01 13:40 ` Pierre Ossman
2008-03-02  2:27 ` Lee Revell
2008-03-02 14:17   ` Pierre Ossman
2008-03-03 12:36 ` Andi Kleen

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=47CED91F.4020106@goop.org \
    --to=jeremy@goop.org \
    --cc=alan-jenkins@tuffmail.co.uk \
    --cc=drzeus-list@drzeus.cx \
    --cc=linux-kernel@vger.kernel.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).