public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Daniel Ritz <daniel.ritz@gmx.ch>
Cc: Sven Dowideit <svenud@ozemail.com.au>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Tom Marshall <tommy@home.tig-grr.com>
Subject: Re: Problems with PCMCIA (Texas Instruments PCI1450)
Date: Fri, 5 Sep 2003 20:54:29 +0100	[thread overview]
Message-ID: <20030905205429.D14076@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200309052140.27906.daniel.ritz@gmx.ch>; from daniel.ritz@gmx.ch on Fri, Sep 05, 2003 at 09:40:27PM +0200

On Fri, Sep 05, 2003 at 09:40:27PM +0200, Daniel Ritz wrote:
> On Fri September 5 2003 20:38, Russell King wrote:
> > On Fri, Sep 05, 2003 at 08:19:28PM +0200, Daniel Ritz wrote:
> > > ok, now i can reproduce the problem on my ti1410 too. on boot detection
> > > works fine with an UP kernel and fails with an SMP kernel. thanx for the
> > > hint.
> > > 
> > > i go to look at the csets a bit and try to find out more....
> > > (i think i know which change...)
> > 
> > Care to provide a hint?
> 
> yes. just tested. patch below makes on boot detection with a SMP kernel
> working again (for me). which is nice, but i don't see why it is better
> that way...

Ok, now I need to hear from Sven (and others) to see if this patch fixes
their problems.  Also, are these other people running a SMP kernel as
well?

Meanwhile, I'm wondering if we have a timing problem here.  Can you check
whether adding a mdelay(1) just after the BUG_ON in the original code
fixes the problem?

> ===== cs.c 1.56 vs edited =====
> --- 1.56/drivers/pcmcia/cs.c	Sun Aug  3 14:48:43 2003
> +++ edited/cs.c	Fri Sep  5 21:42:09 2003
> @@ -316,7 +316,6 @@
>  
>  	wait_for_completion(&socket->thread_done);
>  	BUG_ON(!socket->thread);
> -	pcmcia_parse_events(socket, SS_DETECT);
>  
>  	return 0;
>  }
> @@ -1524,6 +1523,9 @@
>      if (client == NULL)
>  	return CS_OUT_OF_RESOURCE;
>  
> +    if (++s->real_clients == 1)
> +	pcmcia_parse_events(s, SS_DETECT);
> +    
>      *handle = client;
>      client->state &= ~CLIENT_UNBOUND;
>      client->Socket = s;
> 

-- 
Russell King (rmk@arm.linux.org.uk)	http://www.arm.linux.org.uk/personal/
Linux kernel maintainer of:
  2.6 ARM Linux   - http://www.arm.linux.org.uk/
  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
  2.6 Serial core

  reply	other threads:[~2003-09-05 19:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-26 22:56 Problems with PCMCIA (Texas Instruments PCI1410) Daniel Ritz
2003-08-27 12:59 ` Russell King
2003-09-05 21:53   ` Problems with PCMCIA (Texas Instruments PCI1450) Sven Dowideit
2003-09-05 17:58     ` Russell King
2003-09-05 18:19     ` Daniel Ritz
     [not found]       ` <20030905193811.C14076@flint.arm.linux.org.uk>
2003-09-05 19:40         ` Daniel Ritz
2003-09-05 19:54           ` Russell King [this message]
2003-09-05 20:17             ` Daniel Ritz
2003-09-06 16:41             ` [PATCH] " Russell King
2003-09-07 19:33               ` Sven Dowideit
2003-09-08 22:30               ` Tom Marshall
2003-08-27 23:04 ` Problems with PCMCIA (Texas Instruments PCI1410) Sven Dowideit

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=20030905205429.D14076@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=daniel.ritz@gmx.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=svenud@ozemail.com.au \
    --cc=tommy@home.tig-grr.com \
    /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