Received: by 2002:a05:6358:701b:b0:131:369:b2a3 with SMTP id 27csp3311251rwo; Mon, 24 Jul 2023 09:10:13 -0700 (PDT) X-Google-Smtp-Source: APBJJlF0N/TrSdQVFh9ZSriNeiQ2Auv+NC4aukpMZov2LU4//9FEryVKTZGIF0CajpscQDdTJu0w X-Received: by 2002:a05:6a21:9986:b0:138:dbff:f0c1 with SMTP id ve6-20020a056a21998600b00138dbfff0c1mr11511462pzb.1.1690215013293; Mon, 24 Jul 2023 09:10:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1690215013; cv=none; d=google.com; s=arc-20160816; b=hfxEkP/shbHCchpKT0puXcKwHzbXCUpr2ELNZnK0fYI3EdBZgKVlP6660FOiLGgaEU ysFaUosSR7cJN/atdDhdkVJ6LX8NzdtHimLzq7Koqa3wWFTmJR2XUyr8UqSFASa8nAlO 3zEnpMNWvwXFSymTTPTg/YyDLblZI4Gn0wyVidFiS5pOeTVH/Y3rFnwSiR/Zp0Y5Rjg0 YzXEjbsrHw3Y5RdkOiqorTFo2KjlkuAIWcn7on7flLlu47NXib/KJRQDfLR3svi1PAvy HEXMYSuxq099DtUsOB9vZtH2S+A3vgh0rpBHAGt6S4XH/ROFWG9sXtunEFFY+9IdDS0o qyHg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:subject:content-transfer-encoding:mime-version :references:in-reply-to:message-id:cc:to:from:date:dkim-signature; bh=/T4b5niEyR4mZCuDGPl+hY4So/AXh1+NSpM5MAWjNig=; fh=1Af6EXnzGVSn9w3TDCGaKig9KUZQZ7mTLRIpCOlp/Xo=; b=QWh+Nhczyt7W4yqwLM0W9dJOMLHjzTkkT04UdSmzipqHP5yfMxjFOxPfNgL0t26/Np xQy/K+YxlMXK6J98w+6jonRtpoew7NbgqR5Ne4KRDASJk6YfVaeS525s/e6HCszzUpze vLOZOMJoj617bv5AFJqFm0Iua750cDpKAkpSSeMUMT9oclxr7UnppL3XXof1dFsHz//a akmMDfgNtsUUcnOOUsJ/g640OZ/pTN3yQDAqYTmX5M2txow0j83ls0JHQmSSS56kOQUR 4DO37hfKAno8dtr0Y9BLxBf254tOse0iyBs+1GW2z2PWen5XhRKV+tm//sqd+4wbXDuf fuGA== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@hugovil.com header.s=x header.b=gCon4PPr; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id ds11-20020a056a004acb00b0067af445c0e6si9296222pfb.181.2023.07.24.09.10.00; Mon, 24 Jul 2023 09:10:13 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=fail header.i=@hugovil.com header.s=x header.b=gCon4PPr; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229991AbjGXPyt (ORCPT + 99 others); Mon, 24 Jul 2023 11:54:49 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34058 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229506AbjGXPyr (ORCPT ); Mon, 24 Jul 2023 11:54:47 -0400 Received: from mail.hugovil.com (mail.hugovil.com [162.243.120.170]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DD5608E; Mon, 24 Jul 2023 08:54:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=hugovil.com ; s=x; h=Subject:Content-Transfer-Encoding:Content-Type:Mime-Version: References:In-Reply-To:Message-Id:Cc:To:From:Date:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=/T4b5niEyR4mZCuDGPl+hY4So/AXh1+NSpM5MAWjNig=; b=gCon4PPrmEX9pjBv2vCF5E6wIx G4VxmIoK7qcAD7irGRI09CzsImpbHHCYK3aB8orBat7+pD28XdP5MM6vlBva8Xvhgp2pLYkmerMGU 66Yt6tpqo/ZK0GPzslXbKxoXHLtlBUxvJzYXAdzZdgMty9wWXDPu6Jmei3CxF3X+t/Mk=; Received: from modemcable061.19-161-184.mc.videotron.ca ([184.161.19.61]:57608 helo=pettiford) by mail.hugovil.com with esmtpa (Exim 4.92) (envelope-from ) id 1qNxtG-0007Li-Ix; Mon, 24 Jul 2023 11:54:31 -0400 Date: Mon, 24 Jul 2023 11:54:28 -0400 From: Hugo Villeneuve To: Greg KH Cc: Rob Herring , krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org, jirislaby@kernel.org, jringle@gridpoint.com, isaac.true@canonical.com, jesse.sung@canonical.com, tomasz.mon@camlingroup.com, l.perczak@camlintechnologies.com, linux-serial@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org, Hugo Villeneuve , stable@vger.kernel.org, Andy Shevchenko , Lech Perczak Message-Id: <20230724115428.d191186852c0bd0ee0d78398@hugovil.com> In-Reply-To: <2023072240-supremacy-shallot-a77f@gregkh> References: <20230721161840.1393996-1-hugo@hugovil.com> <20230721161840.1393996-7-hugo@hugovil.com> <20230722104724.ef0c5896c239e721794b9fe9@hugovil.com> <2023072240-supremacy-shallot-a77f@gregkh> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-SA-Exim-Connect-IP: 184.161.19.61 X-SA-Exim-Mail-From: hugo@hugovil.com X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net X-Spam-Level: X-Spam-Status: No, score=-2.2 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,SPF_HELO_PASS, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 Subject: Re: [RESEND PATCH v8 06/10] serial: sc16is7xx: fix regression with GPIO configuration X-SA-Exim-Version: 4.2.1 (built Wed, 08 May 2019 21:11:16 +0000) X-SA-Exim-Scanned: Yes (on mail.hugovil.com) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 22 Jul 2023 17:15:26 +0200 Greg KH wrote: > On Sat, Jul 22, 2023 at 10:47:24AM -0400, Hugo Villeneuve wrote: > > On Fri, 21 Jul 2023 13:24:19 -0600 > > Rob Herring wrote: > > > > > On Fri, Jul 21, 2023 at 10:19 AM Hugo Villeneuve wrote: > > > > > > > > From: Hugo Villeneuve > > > > > > > > Commit 679875d1d880 ("sc16is7xx: Separate GPIOs from modem control lines") > > > > and commit 21144bab4f11 ("sc16is7xx: Handle modem status lines") > > > > changed the function of the GPIOs pins to act as modem control > > > > lines without any possibility of selecting GPIO function. > > > > > > Requiring a new DT property is not fixing a kernel regression. You > > > should be returning the kernel to original behavior and then have a > > > new DT property for new behavior. > > > > Hi Rob, > > please read the entire patch history starting from V1 > > and you will understand why this course of action was > > not selected. > > That's not going to happen, sorry, you need to explain it here, in this > patch series, why a specific action is being taken over another one, as > no one has time to go dig through past history, sorry. Hi Rob, I initially submitted a patch to revert the kernel to original behavior, but it created more problems because the patch was unfortunately split in two separate patches, and mixed with other non closely-related changes. It was also noted to me that reverting to the old behavior would break things for some users. It was suggested to me by a more experienced kernel developer to "suggest a fix, instead of hurrying a revert": https://lkml.org/lkml/2023/5/17/758 That is what we decided to do in the end, and it worked quite well. Hugo.