From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752445AbdC0UAk (ORCPT ); Mon, 27 Mar 2017 16:00:40 -0400 Received: from mail.kernel.org ([198.145.29.136]:33492 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751183AbdC0UA3 (ORCPT ); Mon, 27 Mar 2017 16:00:29 -0400 MIME-Version: 1.0 In-Reply-To: <1490621848-24828-11-git-send-email-stefan.wahren@i2se.com> References: <1490621848-24828-1-git-send-email-stefan.wahren@i2se.com> <1490621848-24828-11-git-send-email-stefan.wahren@i2se.com> From: Rob Herring Date: Mon, 27 Mar 2017 15:00:00 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH RFC v4 10/10] tty: serdev: add functions to retrieve common UART settings To: Stefan Wahren Cc: Mark Rutland , "David S. Miller" , Greg Kroah-Hartman , Jiri Slaby , Marcel Holtmann , Sebastian Reichel , netdev , "devicetree@vger.kernel.org" , "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 Mon, Mar 27, 2017 at 8:37 AM, Stefan Wahren wrote: > Currently serdev core doesn't provide functions to retrieve common > UART settings like data bits, stop bits or parity. This patch adds > the interface to the core and the necessary implementation for > serdev-ttyport. It doesn't provide them because why do you need to know? The attached device should request the settings it needs and be done with it. Maybe some devices can support a number of settings and you could want negotiate the settings with the UART, though surely 8N1 is in that list. It's rare to see something that's not 8N1 from what I've seen. Rob