Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp4637598pxu; Thu, 10 Dec 2020 01:25:17 -0800 (PST) X-Google-Smtp-Source: ABdhPJybwaNqcjXWy44J8ieh79FqRd8UWJB5nVmUAh8AMfFIVbiRvDQb+Jitmmzz/MxtVoR7HckY X-Received: by 2002:a50:ed04:: with SMTP id j4mr6006494eds.84.1607592317558; Thu, 10 Dec 2020 01:25:17 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1607592317; cv=none; d=google.com; s=arc-20160816; b=NaEpP79nRhFevwd2YZSmTMEXxY8Y+sW3Uf8heTpNNCC60uyb2fY0vT+BD6Slp1c7mY TwcEIEVVTun+mQeLhGtt+8NOOOnG8IcJutdEB4tfxIbS5LJrt2SyxMRSK/5eBpr+3TvT Zbq5U5kuj9aXe4xkwemxcqbainN8mu1Tdd6isnOdNElNl1M4jeZxRZdqwJdt7V4fDMWt pi2y5mdM0Q7cE2RhkYFKcThfXypxM7FsEYc0euCJ1AjJ3oxi2n6kB3ipFtgZEFY/BTWQ FeDaR3yUYgNXwOGGTrycZzrMnLKXYeeGn5wGBMFdJEOR3gmH/igqULTF+vabluiOGfkp /oKg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:dkim-signature:date; bh=lJLu91yZ5knoKdquKxIgXMUpQlr6G9Ama2W0NuZtmRU=; b=ikvkdhrvmQ3/gWnw6wu0u92VNs0vRsoC/owzXwIsGppStKKERyVeFpluIPFhQS2hdO Z656dQlQRuYp795WQz3wGQopgine3qTssqHE7DF/rLSyimmSomUVCUXjblJQway0hCMw z2ukIAGlyiwpupNe2pJZ+GWlRmwtA4XFsHW42aFQJPUVRg0B7srQ0Afjq6kEsYoy6uhi i42GhMdtwrZzocRg+HNzUfpEag5Emz2TFSljWrm2g3gyonuER4b/g67fdgxQ97qKmyaZ YQqdUyJqz3sazMYm2q7jV0+q9/6fGEFd0m7eIvniXxGYb46Dm0Mcues9sv9GOxcxxkhg 399g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=gMmjtcKY; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d21si2407588edy.92.2020.12.10.01.24.52; Thu, 10 Dec 2020 01:25:17 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=gMmjtcKY; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729827AbgLJJW6 (ORCPT + 99 others); Thu, 10 Dec 2020 04:22:58 -0500 Received: from mail.kernel.org ([198.145.29.99]:36582 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728235AbgLJJW6 (ORCPT ); Thu, 10 Dec 2020 04:22:58 -0500 Date: Thu, 10 Dec 2020 10:06:11 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1607592137; bh=uusQH84CvrIjsML3nBLyENRNWB4hJAGVg6Oykdnge6A=; h=From:To:Cc:Subject:References:In-Reply-To:From; b=gMmjtcKYa0ITrJ+qrZ5wILYNFF+CT7GJVjfrk5z8Mgx3G7H23sSiJtGYlT/LYU34a lptTGGXXFGernbwdG8NfjSL5B+klBHZ52nazg/nHZMh7Ipx5wrXih6IworH6FB/8A/ 4bFjzlY5UXJ7LevC9lv4NWR+i3MMWDyYCowoN0EI= From: Greg Kroah-Hartman To: Mychaela Falconia Cc: Johan Hovold , Jiri Slaby , "Mychaela N . Falconia" , linux-serial@vger.kernel.org, linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 0/7] tty: add flag to suppress ready signalling on open Message-ID: References: <20201202113942.27024-1-johan@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Dec 09, 2020 at 02:49:45PM -0800, Mychaela Falconia wrote: > Greg K-H wrote: > > > I think we need more review for the rest of the series. This does > > change the way serial ports work in a non-traditional way (i.e. using > > sysfs instead of terminal settings). > > But the problem is that the current status quo is fundamentally broken > for those hardware devices in which DTR and/or RTS have been repurposed > for something other than modem and flow control. Right now whenever a > "cold" (never previously opened) serial port is opened for the first > time, that open action immediately and unstoppably asserts both DTR > and RTS hardware outputs, without giving userspace any opportunity to > say "no, please don't do it". Yes, this behaviour is codified in a > bunch of standards that ultimately trace back to 1970s Original UNIX, > but just because it is a standard does not make it right - this > Unix/POSIX/Linux "standard" serial port behaviour is a bug, not a > feature. Thanks for the long response, but I think you have to realize that creating a new api for something that has been "how things work" since the 1970's should not be taken lightly. No matter if it was a bug or not, changing user-visable behavior is not a trivial thing. What we come up with here has to stand the test of time of being able to be supported properly for the next 40+ years. thanks, greg k-h