[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080819233857.41b756cc@lxorguk.ukuu.org.uk>
Date: Tue, 19 Aug 2008 23:38:57 +0100
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Rodolfo Giometti <giometti@...eenne.com>
Cc: linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
David Woodhouse <dwmw2@...radead.org>,
Dave Jones <davej@...hat.com>, Sam Ravnborg <sam@...nborg.org>,
Greg KH <greg@...ah.com>,
Randy Dunlap <randy.dunlap@...cle.com>,
Kay Sievers <kay.sievers@...y.org>
Subject: Re: [PATCH 05/10] ldisc: new dcd_change() method for line
disciplines.
On Wed, 20 Aug 2008 00:49:31 +0200
Rodolfo Giometti <giometti@...eenne.com> wrote:
> On Tue, Aug 19, 2008 at 10:53:22PM +0100, Alan Cox wrote:
> > > + * void (*dcd_change)(struct uart_port *port, unsigned int status,
> > > + * struct timespec *ts)
> > > + *
> > > + * Tells the discipline that the DCD pin has changed its status and
> > > + * the relative timestamp. Pointer ts can be NULL.
> > > */
> >
> > uart_port is a specific property of a few random types of interface, pass
> > a tty struct up. Otherwise looks fine. Might one day expand it to a more
> > generic change type and pass info on what changed but thats a future
> > mystery.
>
> How can I get the struct uart_port pointer starting from struct
> tty_struct one?
A tty may not even have a uart structure. Why do you need to know the
interrupt (if such a concept even exists for the given tty) ?
Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists