From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752327AbdATXz6 (ORCPT ); Fri, 20 Jan 2017 18:55:58 -0500 Received: from mail-wm0-f66.google.com ([74.125.82.66]:32818 "EHLO mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750982AbdATXz4 (ORCPT ); Fri, 20 Jan 2017 18:55:56 -0500 Message-ID: <5882A389.1070701@gmail.com> Date: Fri, 20 Jan 2017 23:55:53 +0000 From: Sudip Mukherjee User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Andy Shevchenko CC: Linus Walleij , Alexandre Courbot , Greg Kroah-Hartman , Jiri Slaby , One Thousand Gnomes , "linux-kernel@vger.kernel.org" , "linux-serial@vger.kernel.org" , "linux-gpio@vger.kernel.org" Subject: Re: [PATCH v10 2/3] serial: exar: split out the exar code from 8250_pci References: <1484864602-5266-1-git-send-email-sudipm.mukherjee@gmail.com> <1484864602-5266-2-git-send-email-sudipm.mukherjee@gmail.com> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Friday 20 January 2017 10:25 PM, Andy Shevchenko wrote: > On Fri, Jan 20, 2017 at 12:23 AM, Sudip Mukherjee > wrote: >> From: Sudip Mukherjee >> >> Add the serial driver for the Exar chips. And also register the >> platform device for the GPIO provided by the Exar chips. > > Thanks, this is indeed much cleaner that v6 I saw couple of weeks before! > >> Andy, >> Having 3 setup hooks and assigning everything there was becoming too >> complicated for me to follow, so i left it as it is. Though some more >> parts from the board setup has been removed. uart_offset has been >> completely removed. > > Yes, what about baudrate? > I will check later, but for me it seems other way, i.e. simpler to > have just 3 setup functions in a row than one is lurking somewhere > with allocation et al. > >> + CONNECT_DEVICE(XR17C154, UART_4_485), >> + CONNECT_DEVICE(XR17C158, UART_8_485), > > Perhaps it takes few LOC more, but having same defined struct here > with dedicated ->setup() looks cleaner to me. > I think now I understand the 3 different setup functions. Let me try v11 (hopefully the last one). Regards Sudip