From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758104Ab0J2QWc (ORCPT ); Fri, 29 Oct 2010 12:22:32 -0400 Received: from lxorguk.ukuu.org.uk ([81.2.110.251]:55637 "EHLO lxorguk.ukuu.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757865Ab0J2QWa (ORCPT ); Fri, 29 Oct 2010 12:22:30 -0400 Date: Fri, 29 Oct 2010 17:22:14 +0100 From: Alan Cox To: Par-Gunnar Hjalmdahl Cc: Arnd Bergmann , linus.walleij@stericsson.com, linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org, Lukasz.Rymanowski@tieto.com Subject: Re: [PATCH 5/9] mfd: Add UART support for the ST-Ericsson CG2900. Message-ID: <20101029172214.25b14c2a@pyx> In-Reply-To: References: <20101022135130.617f0ce8@lxorguk.ukuu.org.uk> <201010281422.46687.arnd@arndb.de> X-Mailer: Claws Mail 3.7.6 (GTK+ 2.18.9; i686-redhat-linux-gnu) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWysKsSBQMIAwIZCwj///8wIhxoRDXH9QHCAAABeUlEQVQ4jaXTvW7DIBAAYCQTzz2hdq+rdg494ZmBeE5KYHZjm/d/hJ6NfzBJpp5kRb5PHJwvMPMk2L9As5Y9AmYRBL+HAyJKeOU5aHRhsAAvORQ+UEgAvgddj/lwAXndw2laEDqA4x6KEBhjYRCg9tBFCOuJFxg2OKegbWjbsRTk8PPhKPD7HcRxB7cqhgBRp9Dcqs+B8v4CQvFdqeot3Kov6hBUn0AJitrzY+sgUuiA8i0r7+B3AfqKcN6t8M6HtqQ+AOoELCikgQSbgabKaJW3kn5lBs47JSGDhhLKDUh1UMipwwinMYPTBuIBjEclSaGZUk9hDlTb5sUTYN2SFFQuPe4Gox1X0FZOufjgBiV1Vls7b+GvK3SU4wfmcGo9rPPQzgIabfj4TYQo15k3bTHX9RIw/kniir5YbtJF4jkFG+dsDK1IgE413zAthU/vR2HVMmFUPIHTvF6jWCpFaGw/A3qWgnbxpSm9MSmY5b3pM1gvNc/gQfwBsGwF0VCtxZgAAAAASUVORK5CYII= Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > Shouldn't you instead be using the drivers/bluetooth/hci_{ldisc,h4} code? > > We also need the ldisc code to handle events from FM and GPS and since > that is chip specific we cannot add that to the generic hci_ldisc > code. Agreed - it's a different protocol. > I agree that we might run into problems if two drivers try to register > the same line discipline. It might then be better to introduce a new If your ldisc is written properly it shouldn't matter. Each tty has a private ldisc pointer to keep the per ldisc instance data. > line discipline then even though that could cause other problems. I do > not know if it is possible to add a condition in Kconfig otherwise so > the CG2900 ldisc cannot be active while the "normal" ldisc driver is > selected. Not sure I follow the concern here ?