Received: by 2002:a05:6359:6284:b0:131:369:b2a3 with SMTP id se4csp3083414rwb; Mon, 7 Aug 2023 08:02:54 -0700 (PDT) X-Google-Smtp-Source: AGHT+IG4AjIys5SRWPAoE2DXEAwkx3/Y+1qmR5vUqe4Eud6EjGbfCQInKJITqVGg/H0MPU1Rz4kI X-Received: by 2002:a17:906:25b:b0:99c:d069:d1f with SMTP id 27-20020a170906025b00b0099cd0690d1fmr3979397ejl.66.1691420573789; Mon, 07 Aug 2023 08:02:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1691420573; cv=none; d=google.com; s=arc-20160816; b=ku0tpmZnv2ak5ydgfh1z7HL9+CYB3Hbc2VPzOQ0Lr4ygQLRKlnKSsqzNmTTolqoPsu Cfg3vpEqWg0cdFbQTTmFmYlB3qyoKDWr+ucJiwHAw2MULkeG63FUEHQm8kLnJSm8fb6x sPSPTbRL8zcy5xqBz3JJSVbiI1gsSXGScIACxNkT3Q81oYyLeAgZtMNHzZF00COOjxT0 L/z7vHs+j8E8NlCDBGjnFY+6Sxfi31ZpwPTHvWpBys+56KTzjoT7WnkCcUhBe3jJa31r OvLvzEQlJBLr43nDLzG0avwhTlWLurhk1fJuL79hiO3WjEUuNVLde4s/jh7JygojrKKl bJ0A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:organization:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=hB4hU7xmILqGV21Fby5RmDUee4weAzxV8YU3oD2mkKM=; fh=kZOqh24kbZSzHf4+AQumBC02UA8B4uEMuvbrjkBOkaI=; b=ZMqgUsbgce5BLpe51ESnaMXsWvsTxkBTr7BZuOArdbfwLgxOR2uSAK4KufMYt9OBqd sb53jUahboPDta5Xcyq2NfltvtoIWdaIb1agJtsZmxYLmsqHDldL5LYUYDvo9s0jXv1P rha9wvDepagpyJ7iAMNlGjTWO5is0YViMYxkRX6+NhuS9rceHc8Y3/EUX+03p4r8u0dk c5uTf0z8B2J49CbjoIkLeJ61e09qPoTIwhxvzEBWzjbQTdaFpOsP7Y5WcfYt1P7yT2Mu v4emGCQqQkdo7ayuU+pgptL1SLgafM4iYm0AP2NVfdLjgn+jOCoQIl/vqQd90XuOrnrT mQ/g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=dHo4qmBC; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id m22-20020a170906849600b0098f99532db4si5678416ejx.664.2023.08.07.08.02.26; Mon, 07 Aug 2023 08:02:53 -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=pass header.i=@intel.com header.s=Intel header.b=dHo4qmBC; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233985AbjHGOdb (ORCPT + 99 others); Mon, 7 Aug 2023 10:33:31 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45572 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232465AbjHGOda (ORCPT ); Mon, 7 Aug 2023 10:33:30 -0400 Received: from mgamail.intel.com (mgamail.intel.com [192.55.52.151]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4A03210DC; Mon, 7 Aug 2023 07:33:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1691418809; x=1722954809; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=TRDCLFDgzgMsAH800OlISo9NPJHoNGEwoCEGo3ugJME=; b=dHo4qmBC8osqA8qh+/9mRCMBokFuBX8/d7pRc6TO0na+2DLI12F7/Bzy u3MhLMZwpt89hko6rJC0sDk2iKqkH/k9uLn9lOrtvIXFQwckGHp/JbblR jWpe0mpRMexjLzby7sIlhETHvIochznBJ7qeM/H5BzF1CsBe8YB/PXKyO P6P4JleXWGIwZB5RO5hv0gBCysVWRs0U5I6wHZ61GHsSxpkzd9ZmKbOW+ u+A63hyg5tC3xa4QHTmRxR6sxr3y7cVLF7b4Rzgegca1wrJOV7XfI+Cq7 S+MesuifdmNQFsHN/4koD5SHUsA/Kbem4uNn1Caq8oE2LyQcanEGmA+D7 A==; X-IronPort-AV: E=McAfee;i="6600,9927,10795"; a="350867078" X-IronPort-AV: E=Sophos;i="6.01,262,1684825200"; d="scan'208";a="350867078" Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 07 Aug 2023 07:32:54 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10795"; a="977465850" X-IronPort-AV: E=Sophos;i="6.01,262,1684825200"; d="scan'208";a="977465850" Received: from smile.fi.intel.com ([10.237.72.54]) by fmsmga006.fm.intel.com with ESMTP; 07 Aug 2023 07:32:52 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1qT1Hu-00FTgr-1x; Mon, 07 Aug 2023 17:32:50 +0300 Date: Mon, 7 Aug 2023 17:32:50 +0300 From: Andy Shevchenko To: Andi Shyti Cc: Jarkko Nikula , Mario Limonciello , Wolfram Sang , linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org, Mika Westerberg , Jan Dabros Subject: Re: [PATCH v1 4/9] i2c: designware: Propagate firmware node Message-ID: References: <20230725143023.86325-1-andriy.shevchenko@linux.intel.com> <20230725143023.86325-5-andriy.shevchenko@linux.intel.com> <20230804205956.uuna4c76ww64z3zm@intel.intel> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230804205956.uuna4c76ww64z3zm@intel.intel> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,RCVD_IN_DNSWL_BLOCKED, SPF_HELO_NONE,SPF_NONE 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 On Fri, Aug 04, 2023 at 10:59:56PM +0200, Andi Shyti wrote: > On Mon, Jul 31, 2023 at 11:09:24PM +0300, Andy Shevchenko wrote: > > On Fri, Jul 28, 2023 at 03:25:58PM +0300, Jarkko Nikula wrote: > > > On 7/25/23 17:30, Andy Shevchenko wrote: > > > > Propagate firmware node by using a specific API call, i.e. device_set_node(). ... > > > > + device_set_node(&dev->adapter.dev, dev_fwnode(dev->dev)); > > > > > > Would this be better to put in the same place where ACPI_COMPANION_SET() is > > > removed like below? I'd keep this static inline function in the header file > > > as simple as possible. All extra code might invite adding even more. > > > > We come again to the duplication and prone to deviation code, I wouldn't like > > to go this way. The idea of this call is to unify and avoid mistakes, like > > updating only in ACPI or DT (or any new one if happens in the future) case > > and leaving the second one unconsidered. > > it's anyway an inline function becoming a bit too fat. Can't we > make it not inline? > > > That said, I would rather drop this patch until i2c core will take this > > once for all (may be never in the reasonable future :-). > > Which patch are you referring to that should be taken into i2c > core? Something I tried to do in the past but failed. https://lore.kernel.org/linux-i2c/20211207162457.18450-1-andriy.shevchenko@linux.intel.com/ -- With Best Regards, Andy Shevchenko