[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090728150727.GA10870@rakim.wolfsonmicro.main>
Date: Tue, 28 Jul 2009 16:07:27 +0100
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Janusz Krzysztofik <jkrzyszt@....icnet.pl>
Cc: alsa-devel@...a-project.org, Jonathan McDowell <noodles@...th.li>,
Tony Lindgren <tony@...mide.com>,
Peter Ujfalusi <peter.ujfalusi@...ia.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
e3-hacking@...th.li, Arun KS <arunks@...tralsolutions.com>,
"linux-serial@...r.kernel.org" <linux-serial@...r.kernel.org>,
"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [alsa-devel] [RFC] [PATCH 1/3] ASoC: Add support for Conexant
CX20442-11 voice modem codec
On Tue, Jul 28, 2009 at 04:59:33PM +0200, Janusz Krzysztofik wrote:
> Following that model, the line discipline code didn't seam to belong to a
> codec driver for me. If it could be recognized as a new bus dirver, it should
> be pushed down probably into a separate module. However, if it was rather
> some kind of a bus adapter driver, it seamed to belong to the machine code.
The way it looks with the current code the line discipline itself is
going to apply equally well to any serial port that's used - I'm not
clear what's system-specific about it. The bit that connects the line
discipline to the line is a different matter but the bit that interacts
with the TTY layer after registration is working through a pluggable
abstraction layer and shouldn't, I'd expect, be specific to the
particular serial port.
--
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