From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 579E7E92FF9 for ; Fri, 6 Oct 2023 08:30:32 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231173AbjJFIaa (ORCPT ); Fri, 6 Oct 2023 04:30:30 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42112 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230076AbjJFIa2 (ORCPT ); Fri, 6 Oct 2023 04:30:28 -0400 Received: from mgamail.intel.com (mgamail.intel.com [192.55.52.115]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9B11283; Fri, 6 Oct 2023 01:30:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1696581027; x=1728117027; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=AwhlxzzmAzPePwi2wcwAldf1evn70J98RRqGuI/mr24=; b=gIcfG4XWNQ6Wx96XWumYphNinGU5GZ4l2K1/e3MWRFvrmo/pPxu1/aUR SPsBm5ymlBetf0PtGzo2nEj66Pj5z3ftswFEBDne3JDZUz5Nl/Zd6WYWS QhEWpL5wsvxkI1jKT8V6ri8VwPLc7Rj+93Jj5Qm/tfj4NCCGHxC2vAY87 uLE/zPSw5s5wlYOwhOl9UYWfKLArOYNbN7fbagQkN7GkJKvXeZSWy/noc 4VeSs4yS1/NjKULNMSQEVjgjeGsnXeZjDUwRa1d3YDjipPL90l67INh/j BNVq+HQznOpJjSBIu9fAUaJIWv4svQLuukfnezM9jGWBdgKQBofK6HOIS A==; X-IronPort-AV: E=McAfee;i="6600,9927,10854"; a="383594763" X-IronPort-AV: E=Sophos;i="6.03,203,1694761200"; d="scan'208";a="383594763" Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Oct 2023 01:30:27 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10854"; a="999258780" X-IronPort-AV: E=Sophos;i="6.03,203,1694761200"; d="scan'208";a="999258780" Received: from smile.fi.intel.com ([10.237.72.54]) by fmsmga006.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Oct 2023 01:30:23 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.97-RC1) (envelope-from ) id 1qogE0-00000003EoO-271a; Fri, 06 Oct 2023 11:30:20 +0300 Date: Fri, 6 Oct 2023 11:30:20 +0300 From: Andy Shevchenko To: Tony Lindgren Cc: Greg Kroah-Hartman , Jiri Slaby , Dhruva Gole , Ilpo =?iso-8859-1?Q?J=E4rvinen?= , John Ogness , Johan Hovold , Sebastian Andrzej Siewior , Vignesh Raghavendra , linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org, Maximilian Luz Subject: Re: [PATCH] serial: core: Fix checks for tx runtime PM state Message-ID: References: <20231005075644.25936-1-tony@atomide.com> <20231006072738.GI34982@atomide.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20231006072738.GI34982@atomide.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Oct 06, 2023 at 10:27:38AM +0300, Tony Lindgren wrote: > * Andy Shevchenko [231005 12:01]: > > On Thu, Oct 05, 2023 at 10:56:42AM +0300, Tony Lindgren wrote: > > > The serdev device and the serial core controller devices are siblings of > > > the serial port hardware device. The runtime PM usage count from serdev > > > > I'm a bit lost in terminology here. > > AFAIU there are: > > 1) children of the serial physical device; > > 2) siblings (to each other). > > > > But may be I mistakenly deciphered the diagram from the previous discussion. > > You're right, so how about: > > The serdev device and the serial core controller devices are children of > the serial port hardware device. The runtime PM usage count from serdev > device does not propagate to the serial core device siblings, it only > propagates to the parent. Clearer, thank you! -- With Best Regards, Andy Shevchenko