From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751414AbdFYWnT (ORCPT ); Sun, 25 Jun 2017 18:43:19 -0400 Received: from zimbra.gr13.net ([46.4.151.110]:52174 "EHLO zimbra.gr13.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751373AbdFYWnS (ORCPT ); Sun, 25 Jun 2017 18:43:18 -0400 To: linux-kernel@vger.kernel.org From: "Enrico Weigelt, metux IT consult" Subject: Directly accessing serial ports from drivers w/o TTYs ? Message-ID: Date: Mon, 26 Jun 2017 00:43:12 +0200 User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi folks, is there already a way for accessing serial ports from drivers, w/o having to go through the TTY subsystem ? Serdev seems provide a connection between arbitrary TTYs to device drivers. But this implies always having a TTY for each UART (even if it's never used outside the kernel). Is there any way for accessing uarts more directly ? --mtx -- Enrico, Sohn von Wilfried, a.d.F. Weigelt, metux IT consulting +49-151-27565287