From: Stefan Seyfried <seife@suse.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
magnus.damm@gmail.com, DHollenbeck <dick@softplc.com>
Subject: Re: yenta_socket rapid fires interrupts
Date: Thu, 13 Jan 2005 15:13:41 +0100 [thread overview]
Message-ID: <41E68215.8060004@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0501111322060.2373@ppc970.osdl.org>
Linus Torvalds wrote:
> What I don't see is why the port changes state, then. Since the yenta
> driver doesn't care for the interrupt anyway, it shouldn't be touching the
> hardware, and if it doesn't touch the hardware, then the pcmcia thing
> should eventually just calm down, even if it were to de-bounce a few
> times.
>
> The above is what you'd likely see if somebody was forcing a reset on the
> card or a card voltage re-interrogation all the time, which I don't see
> why it would happen.
i have a "feeling" that a weak power supply or a little bit too high
current draw from the card may cause something like this. But this is
just what i wrote: a feeling from my stomach ;-)
Stefan
next prev parent reply other threads:[~2005-01-13 14:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 17:33 yenta_socket rapid fires interrupts DHollenbeck
2005-01-10 19:24 ` Alan Cox
2005-01-11 3:17 ` Linus Torvalds
2005-01-11 19:18 ` DHollenbeck
2005-01-11 19:46 ` Grzegorz Kulewski
2005-01-11 19:54 ` Linus Torvalds
2005-01-11 21:16 ` DHollenbeck
2005-01-11 21:40 ` Linus Torvalds
2005-01-13 14:13 ` Stefan Seyfried [this message]
2005-01-13 15:42 ` DHollenbeck
2005-01-13 15:59 ` DHollenbeck
2005-01-11 21:38 ` DHollenbeck
2005-01-11 21:43 ` Linus Torvalds
2005-01-11 22:32 ` DHollenbeck
2005-01-12 0:03 ` Linus Torvalds
2005-01-12 23:14 ` DHollenbeck
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=41E68215.8060004@suse.de \
--to=seife@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dick@softplc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.