From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <1484050829.2133.9.camel@linux.intel.com> Subject: Re: [PATCH 0/9] Serial slave device bus From: Andy Shevchenko To: "H. Nikolaus Schaller" , Marcel Holtmann Cc: Rob Herring , Greg Kroah-Hartman , Jiri Slaby , Sebastian Reichel , Arnd Bergmann , 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 Date: Tue, 10 Jan 2017 14:20:29 +0200 In-Reply-To: <6C3E6EA6-5B22-47E8-B2B2-C37D4D080505@goldelico.com> References: <20170106162635.19677-1-robh@kernel.org> <8E1651EC-E9E5-4BB5-84CB-8CFEE08009BA@goldelico.com> <6C3E6EA6-5B22-47E8-B2B2-C37D4D080505@goldelico.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 List-ID: On Tue, 2017-01-10 at 13:10 +0100, H. Nikolaus Schaller wrote: > > So the question is really if a driver only needs to do power > > management on open() and close() or if it also has to translate or > > transform the packets. There are devices who speak NMEA and all is > > good. > > The device I want to upstream the driver speaks NMEA but should be > powered down unless accessed... By the way, have you seen the series [1] I'm working on towards bringing runtime PM for all (current) serial drivers? [1] https://www.spinics.net/lists/linux-serial/msg24025.html -- Andy Shevchenko Intel Finland Oy