Date: Wed, 4 Nov 2009 00:54:32 +0000
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: Alan Cox <alan@linux.intel.com>, linux-mmc@vger.kernel.org,
       lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 00/11] Sort out sdio_uart - stage two
Message-ID: <20091104005432.3cdc924f@lxorguk.ukuu.org.uk>
In-Reply-To: <alpine.LFD.2.00.0911031401170.13333@xanadu.home>
References: <20091103141525.31032.45206.stgit@localhost.localdomain>
	<alpine.LFD.2.00.0911031401170.13333@xanadu.home>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 954
Lines: 21

> >From what I can see, sdio_uart_open() and sdio_uart_activate() are 
> called on the first cat invocation, and then sdio_uart_close() and 
> sdio_uart_shutdown() when cat is stopped with ^C.  However neither 

I would have expected the cat to terminate when the port is unplugged
(and the uart remove method called - doing a hangup)

> sdio_uart_open() nor sdio_uart_activate() is ever called anymore with 
> any subsequent cat invocations until a reboot.  Some upper layer must 
> have taken upon itself to return -EIO to user space.

The first call into the driver is to sdio_uart_install which looks up the
port from tty->index and would blow up if for some reason the get method
failed.

Still digging.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/