From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752056AbdAMP2g (ORCPT ); Fri, 13 Jan 2017 10:28:36 -0500 Received: from mail.kernel.org ([198.145.29.136]:53078 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751528AbdAMP2d (ORCPT ); Fri, 13 Jan 2017 10:28:33 -0500 MIME-Version: 1.0 In-Reply-To: <1484319863.2133.110.camel@linux.intel.com> References: <20170106162635.19677-1-robh@kernel.org> <20170106162635.19677-9-robh@kernel.org> <1483798314.26691.3.camel@linux.intel.com> <1484319863.2133.110.camel@linux.intel.com> From: Rob Herring Date: Fri, 13 Jan 2017 09:28:07 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 8/9] serdev: add a tty port controller driver To: Andy Shevchenko Cc: Greg Kroah-Hartman , Marcel Holtmann , Jiri Slaby , Sebastian Reichel , Arnd Bergmann , "Dr . H . Nikolaus Schaller" , Peter Hurley , Alan Cox , Loic Poulain , Pavel Machek , NeilBrown , Linus Walleij , "open list:BLUETOOTH DRIVERS" , "linux-serial@vger.kernel.org" , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jan 13, 2017 at 9:04 AM, Andy Shevchenko wrote: > On Thu, 2017-01-12 at 10:01 -0600, Rob Herring wrote: >> On Sat, Jan 7, 2017 at 8:11 AM, Andy Shevchenko >> wrote: >> > On Fri, 2017-01-06 at 10:26 -0600, Rob Herring wrote: >> > > Add a serdev controller driver for tty ports. >> > > >> > > The controller is registered with serdev when tty ports are >> > > registered >> > > with the TTY core. As the TTY core is built-in only, this has the >> > > side >> > > effect of making serdev built-in as well. >> > > >> > > >> > > +if SERIAL_DEV_BUS >> > > + >> > > +config SERIAL_DEV_CTRL_TTYPORT >> > > + bool "Serial device TTY port controller" >> > > + depends on TTY >> > > + depends on SERIAL_DEV_BUS=y >> > >> > Do you need one? >> >> Yes, otherwise the bus can be built as a module and this driver can >> still be enabled breaking the build. I could drop supporting building >> the bus as a module because as long as this is the only controller >> driver, it all has to be built-in. > > Would > > if SERIAL_DEV_BUS=y > > work for you? Yes, until we add a driver that doesn't have to be built-in. What about "depends on SERIAL_DEV_BUS != m"? That would be a bit more clear what the reason is. Rob