Received: by 2002:a05:6a10:9afc:0:0:0:0 with SMTP id t28csp1073491pxm; Wed, 23 Feb 2022 17:25:31 -0800 (PST) X-Google-Smtp-Source: ABdhPJxNd91ruChjWZSsI5XGXjlrKrNv4P7MDKaiFjJqjYjeCtlSd+q9e/RJYTeqxaJbstq0OD2O X-Received: by 2002:a63:6687:0:b0:373:a222:ad4f with SMTP id a129-20020a636687000000b00373a222ad4fmr430543pgc.340.1645665930942; Wed, 23 Feb 2022 17:25:30 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1645665930; cv=none; d=google.com; s=arc-20160816; b=HcQZLCl8Ad3wp43Xg2eN+r/9j/2ModHPZmS4j/8ZYh0ND/oeOoeDZdQu+CZqEiyOo2 CssMhzsblqIroHWFhdNniBDDVNagW+Fa5QElFFDsynRzyfxCHSGQbxANIDz1k2v18QwY pbjg4hwwj/OdAWmPp+yKtnsrANraHtWaSnftYeEpyy4B5TbM0b3wy6R7zCgva59u8iwT YPcYAOoY/AWq8mvR9dXBmdSjRCKEHv2Z4ylBvP0gB3e9fMbEzFeu+HbLxlQ8kd1kEI+i 0l//dQFQEFqXzxJ1E0bysM/7tDSbouGxRB9a+HTYaCyLeRY7TJgf+4BolmS5GPfAHAr/ QIuw== 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=3QJGuEqSimx+UcRyvZAqKstqNm92Q8v+8Md+LVd7vMw=; b=OeA9/JrDLKkobVXXr2oO0JgMb/CYRCBhz6b/qODyker8RU7qqQVnEoFd0jc2SKOQaQ 6rey+En+sqSWaX5eI0AzipMbzAebMineTWfxF/LrGmYotQHN+8X5HTjGCkgtgfJnTk53 unHhnVzx/r/gWG3QqysCXR57ex7WmnowNxKgWYuziBxRNYCw/l+vlfM96DmLYZMHxLMp K/yjw1sfMFn0vsCvRY4miQgKA8Mb5AxrQ4HCWtUQbPvzeAapnF85ajO2WElE0UMO5OgF 5L50GOgL2vbkVLBLh+j3N0GgNsNMEdJChjVAlFJlngT/Dedmefb+/RXX2aj6VWx+P2Td h8sQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=MEQumQnX; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 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 lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [23.128.96.19]) by mx.google.com with ESMTPS id 67si1418349pgi.236.2022.02.23.17.25.30 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 23 Feb 2022 17:25:30 -0800 (PST) Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=MEQumQnX; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id C8CFE10BBF7; Wed, 23 Feb 2022 17:07:07 -0800 (PST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242142AbiBWPh6 (ORCPT + 99 others); Wed, 23 Feb 2022 10:37:58 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47798 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242043AbiBWPh4 (ORCPT ); Wed, 23 Feb 2022 10:37:56 -0500 Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 38572BBE0B; Wed, 23 Feb 2022 07:37:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1645630648; x=1677166648; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=7ONB/aTHqMjYH/OmutKWhupcasaRbDK6GNSZHCYrgIs=; b=MEQumQnXn/kchseS79skJ8C/8UryZIzbBJ2HpjdjH6VRDDuuQa9i8ZWU Xx9hCvjh9wL9nOUCUm02fc6TPhdslylyTvdOAE52DvqqoBqwFp6KH2sQ/ xdXRsWbgYyHiix6YTGJThfIYRXmMrH+hSFQbHNojfsoEr3kw2GIBfxpfh 63xnBb7rRtbEth7E3aJukrgUDnEvimcT2aLk1FapUKRFgYH3Y0v8Hce6p UlNr/aUnRDcWdhqB72sJgWg++wApv0gDzomyagHM1Lk3zUJbBiwJ1L5QK N53SJSJaV+eLDs212HDyNrHHUVoNpJhjdGtXGMU9xiYJAqU4GiXP+CA4q g==; X-IronPort-AV: E=McAfee;i="6200,9189,10266"; a="338427660" X-IronPort-AV: E=Sophos;i="5.88,391,1635231600"; d="scan'208";a="338427660" Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Feb 2022 07:37:27 -0800 X-IronPort-AV: E=Sophos;i="5.88,391,1635231600"; d="scan'208";a="628121128" Received: from smile.fi.intel.com ([10.237.72.59]) by fmsmga003-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Feb 2022 07:37:23 -0800 Received: from andy by smile.fi.intel.com with local (Exim 4.95) (envelope-from ) id 1nMtgt-007TeV-Tl; Wed, 23 Feb 2022 17:36:31 +0200 Date: Wed, 23 Feb 2022 17:36:31 +0200 From: Andy Shevchenko To: Hans de Goede Cc: Andrew Lunn , =?iso-8859-1?Q?Cl=E9ment_L=E9ger?= , "Russell King (Oracle)" , Daniel Scally , Heikki Krogerus , Sakari Ailus , Greg Kroah-Hartman , "Rafael J . Wysocki" , Wolfram Sang , Peter Rosin , 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 10/10] net: sfp: add support for fwnode Message-ID: References: <20220221162652.103834-11-clement.leger@bootlin.com> <20220222142513.026ad98c@fixe.home> <888f9f1a-ca5a-1250-1423-6c012ec773e2@redhat.com> <4d611fe8-b82a-1709-507a-56be94263688@redhat.com> <20220223151436.4798e5ad@fixe.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RDNS_NONE,SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=no 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 Wed, Feb 23, 2022 at 04:27:33PM +0100, Hans de Goede wrote: > On 2/23/22 16:23, Andrew Lunn wrote: > >> As Russell asked, I'm also really interested if someone has a solution > >> to reuse device-tree description (overlays ?) to describe such > >> hardware. However, the fact that CONFIG_OF isn't enabled on x86 config > >> seems a bit complicated on this side. > > > > It does work, intel even used it for one of there tiny x86 SoCs. Maybe > > it was Newton? > > IIRC those SoCs did not use standard EFI/ACPI though, but rather some > other special firmware, I think it was SFI ? This is not so much about > the CPU architecture as it is about the firmware/bootloader <-> > OS interface. I think Andrew refers to Intel SoCs that are using OF. Those so far are CE4xxx and SoFIA SoCs. -- With Best Regards, Andy Shevchenko