Received: by 2002:a05:6358:53a8:b0:117:f937:c515 with SMTP id z40csp5146806rwe; Tue, 18 Apr 2023 02:45:46 -0700 (PDT) X-Google-Smtp-Source: AKy350ayXL6FWop99DQyd3ibv1qPKMenaqxWQ9XGy54r+sXFdsSwzgav2SXqxHg+3klaKjEr7dOR X-Received: by 2002:a05:6a00:a95:b0:63b:4313:f8b5 with SMTP id b21-20020a056a000a9500b0063b4313f8b5mr23213892pfl.23.1681811146115; Tue, 18 Apr 2023 02:45:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1681811146; cv=none; d=google.com; s=arc-20160816; b=FyLvpfOICRJZwPN8TZJvcX+qHzJtHoi3H0LPzJjF4b/v+mnx0ibKxdAoT9Sj434mHh I1UWOwEjhhzvGAQ02xBKNyzZaifhJgMG2SFgVxN6967FtHthXkMOVWUopCLI8ihZaxc/ XhToDVA97mqyeMyhAKmGFX0VsQ2DcUovegIgeBL0BEhMbFtqq4YMOoFS6K8yq5av5Qn3 niYWU/8Jlhu7XGTd8mVNmfRVrjwXfyhEWyrmiw5qX2OnjGyOVUxMWCzfpgs/UCcwh1vR nsK4acFAovs/HdFrMuSIzzgCbDC//4n5cQrd/87sjDXB56wTGm7a6uSGPY9uM5Tn1omc 7GSA== 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:date; bh=i0jk0TUcnG+CEn/0Dhy2rmOpKC8hE3b0XGDEcciJtyo=; b=o2kky27x48qfOVi+aogI6Cw1Ist/joSFZ+jHuqfozincb2fU61P78EgUPYp51Bfph2 5fq9H5yhpnSx2LM722dtOMEAXmBvZIx1L63molOrzUQDZW9v40Sc4pHheKcUWuECyZiH XJ0K5PbUY0wyVaulsfHdJiv2XB+KuzgaMYY6TPONwIzFIqgApjwhkWjv2SNA4M7PfIsi RfnrxEAN7GTrBhuodQtH4BMP7jeWfjBfFTugVujIfE+3iZNv+bkC6z56bm8qQkgwm9K3 ruodxmINkTsfG7E5iVXXYDUPE7mTbWL9KDgeT+FzDfGShm0HB5OUozY+8Xwr53odDk+9 5n5w== ARC-Authentication-Results: i=1; mx.google.com; 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 g204-20020a6252d5000000b0063b87656fd6si6926392pfb.203.2023.04.18.02.45.32; Tue, 18 Apr 2023 02:45:46 -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; 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 S231463AbjDRJlu (ORCPT + 99 others); Tue, 18 Apr 2023 05:41:50 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43138 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230519AbjDRJl1 (ORCPT ); Tue, 18 Apr 2023 05:41:27 -0400 Received: from muru.com (muru.com [72.249.23.125]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id D5C47170E; Tue, 18 Apr 2023 02:41:25 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id 9FFF38106; Tue, 18 Apr 2023 09:41:24 +0000 (UTC) Date: Tue, 18 Apr 2023 12:41:23 +0300 From: Tony Lindgren To: Ilpo =?utf-8?B?SsOkcnZpbmVu?= Cc: Andy Shevchenko , Greg Kroah-Hartman , Jiri Slaby , Johan Hovold , Sebastian Andrzej Siewior , Vignesh Raghavendra , linux-omap@vger.kernel.org, linux-serial , LKML Subject: Re: [PATCH] serial: 8250: Clear port->pm on port specific driver unbind Message-ID: <20230418094123.GA14287@atomide.com> References: <20230413070342.36155-1-tony@atomide.com> <20230414054726.GE36234@atomide.com> <63b333cb-13c7-db58-9cf-697aa1c4c48a@linux.intel.com> <20230414094035.GF36234@atomide.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230414094035.GF36234@atomide.com> X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Tony Lindgren [230414 09:40]: > I'm now wondering still if we should clear all the conditional hardware > specific functions too in addition to port->pm that get set in > serial8250_register_8250_port(). Maybe best done in a separate patch > as needed.. Any suggestions? Well we can't do memset on the port for sure at this point.. But what we can do is call serial8250_set_defaults() instead of clearing just port->pm. This will set the port back to serial8250 default functions, and will set port->pm too. I'll send v2 patch after some more testing. Regards, Tony