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 AD506C433F5 for ; Mon, 21 Feb 2022 18:06:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229941AbiBUSGq (ORCPT ); Mon, 21 Feb 2022 13:06:46 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:36512 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232547AbiBUSE0 (ORCPT ); Mon, 21 Feb 2022 13:04:26 -0500 Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BF7131D0C7; Mon, 21 Feb 2022 09:56:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1645466182; x=1677002182; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=+/KTjRfi65Ib76kWEGOorsZScmtiCnDSMiUu8H92FgM=; b=ITLgqtddaj9jqorF5CndFdZuYeHqPzmeK9CwEFHoTW8C1rV5J8x8Nr2g L6o9qXrSkWArfVrOfsUUquPA4cmaHrePYOgyc7Me3nqMQLLjk+0lHYNv8 +qyHTnvJe32vv6p2wpcqlPfZkcdTa8/4r4n0BWPL6DGIJVUav09bw49TJ h4cN2Sv54eyyGHC0b6gL7FyMc3QJRAT77ed6egzjP0sMT92oseMNSMmwW RSCItpfmqtW2uMbvmi19HjTbuHUS7PSRfdlKzuzagVkjVPL+bKJkE+MGQ S+tCoQEaJoD5tuf3khN+27vGg9lts/JTRz3qf1NBrlvt86N3x83AXt5xg Q==; X-IronPort-AV: E=McAfee;i="6200,9189,10265"; a="314812286" X-IronPort-AV: E=Sophos;i="5.88,386,1635231600"; d="scan'208";a="314812286" Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Feb 2022 09:56:22 -0800 X-IronPort-AV: E=Sophos;i="5.88,386,1635231600"; d="scan'208";a="706329238" Received: from smile.fi.intel.com ([10.237.72.59]) by orsmga005-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Feb 2022 09:56:17 -0800 Received: from andy by smile.fi.intel.com with local (Exim 4.95) (envelope-from ) id 1nMCuD-006s7L-Qt; Mon, 21 Feb 2022 19:55:25 +0200 Date: Mon, 21 Feb 2022 19:55:25 +0200 From: Andy Shevchenko To: =?iso-8859-1?Q?Cl=E9ment_L=E9ger?= Cc: Daniel Scally , Heikki Krogerus , Sakari Ailus , Greg Kroah-Hartman , "Rafael J . Wysocki" , Wolfram Sang , Peter Rosin , Russell King , Andrew Lunn , Heiner Kallweit , "David S . Miller" , Jakub Kicinski , linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, linux-i2c@vger.kernel.org, netdev@vger.kernel.org, Thomas Petazzoni , Alexandre Belloni Subject: Re: [RFC 09/10] i2c: mux: add support for fwnode Message-ID: References: <20220221162652.103834-1-clement.leger@bootlin.com> <20220221162652.103834-10-clement.leger@bootlin.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20220221162652.103834-10-clement.leger@bootlin.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-acpi@vger.kernel.org On Mon, Feb 21, 2022 at 05:26:51PM +0100, Clément Léger wrote: > Modify i2c_mux_add_adapter() to use with fwnode API to allow creating > mux adapters with fwnode based devices. This allows to have a node > independent support for i2c muxes. I^2C muxes have their own description for DT and ACPI platforms, I'm not sure swnode should be used here at all. Just upload a corresponding SSDT overlay or DT overlay depending on the platform. Can it be achieved? -- With Best Regards, Andy Shevchenko