Received: by 2002:a05:7412:419a:b0:f3:1519:9f41 with SMTP id i26csp4472803rdh; Wed, 29 Nov 2023 02:26:59 -0800 (PST) X-Google-Smtp-Source: AGHT+IHUoSquNrvHXDKuW7KcZUyjKKqXc13rOhoQDsTrM9OWdtxd5CBqVrJPZbj2NbhZI7ygFzNk X-Received: by 2002:a05:6808:124e:b0:3b5:6462:3191 with SMTP id o14-20020a056808124e00b003b564623191mr22266717oiv.48.1701253618783; Wed, 29 Nov 2023 02:26:58 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1701253618; cv=none; d=google.com; s=arc-20160816; b=i3fZR8yrccDCOAySi0JsWx8aaHou7tIhiEuuEccokHDOc/Rd1dQaD2wHjSPMunz81c CHUT3Ul9PD7Eb9YoAJ4GR7TlT9V/dOWRfTUOCOFhlbv2lsCRTeb8AonwmOXvIEDgYCTa uc2jL/XwdQjb5KEUDA8BHzGQbT0vt5Y9vUQ9KhYlFzkOSPCLhDGnx44uDUS4dhrgr6AI vSnK+AdseiC5L00LiDP6fji9mPIrWR2BmKqSuAXlhl0c8hhOLFaF/kmQ0VUFhsV6Lyff dgGJsjluHny3GcvWxBwjU0jKXJiVqOTxlvOY8BBKE012y5cnVGvCTv6PNr2NEnAQ4Nik csWQ== 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:dkim-signature; bh=jwe/LwQq+QQ6dvbhFcyBUCWxtvcs2WAhCKRzn1X6h/g=; fh=/fl7EgnJCgRIYqf0Y0EFmmuJmVaHgtZH4zms9tWjsOY=; b=YzlgtWgahFQiAPYUEjXshhiKr4gEC+n403cOniO3rAGypIfG9ZYn/rkZ9HaqBJm+ZT w7YD5i/EMvi0mYDnTILBBnLijIm2iy6U3ocNfW5I2TagciByDjQmH9rAlFzSxZlC8/6Q GqgIe9yO9cW1ufjoPzwPG094Uh3eMo3ysVM3OYAiXekac9LUr+L9fv6m5BvquVcCqkqm yJPIDDApibUdVhzfMyeSEGdNp8tMaYwxoE02j+zO1EPOsaf6pDMPM3PkdMWHe9YL3oH/ Q0DBUrtH74uxOrsyyNUH30iXU7nFJEmX0Cc3BoUVwMPGzi7qwV+dDMA3n5+022Ar+fWK 5/Mg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=Xk75wjw+; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.37 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 snail.vger.email (snail.vger.email. [23.128.96.37]) by mx.google.com with ESMTPS id x3-20020a63f703000000b005c5fe3ad1fdsi1771858pgh.357.2023.11.29.02.26.58 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 29 Nov 2023 02:26:58 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.37 as permitted sender) client-ip=23.128.96.37; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=Xk75wjw+; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.37 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 out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by snail.vger.email (Postfix) with ESMTP id ADF15803E7AA; Wed, 29 Nov 2023 02:26:57 -0800 (PST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.11 at snail.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232885AbjK2K0q (ORCPT + 99 others); Wed, 29 Nov 2023 05:26:46 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55620 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229873AbjK2K0o (ORCPT ); Wed, 29 Nov 2023 05:26:44 -0500 Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.10]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 53408BA for ; Wed, 29 Nov 2023 02:26:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1701253611; x=1732789611; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=BJxYP16lOxo2zmWtEP5drYB30Z4f3hd1h6W3Mdtes9Y=; b=Xk75wjw+k7G0cywweCScaHn0fTsiRpuyXWXbiHfKCGz0t4EuiJ1yqUg/ vtJRf1Vp6xIPDvSme83eVbNN8XouJf9n3wpmTlI20TRHeMNJLCRANgrHh fjFFhXbG8hUDpVOkMAY5uIgHH2H826ZjGEEER6KbJ1Zbx4mjcxqOLEpTf SVu8EaW3MqiN/M7scf5HKqf6jzfzfXZhA0grfkpZAiqOmQtyODRpSz1yw PrcmcnVewQRZgNGeAalDeMs3JkSkRPvxB9iEigHTiduqylCLATwZRs18z zftmITCwhdb+fG4VlcBJpIZgYLhATCOCYnfWEk/OWrcq+FMy0LWvllbqs A==; X-IronPort-AV: E=McAfee;i="6600,9927,10908"; a="6406768" X-IronPort-AV: E=Sophos;i="6.04,235,1695711600"; d="scan'208";a="6406768" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orvoesa102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Nov 2023 02:26:50 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10908"; a="797874676" X-IronPort-AV: E=Sophos;i="6.04,235,1695711600"; d="scan'208";a="797874676" Received: from turnipsi.fi.intel.com (HELO kekkonen.fi.intel.com) ([10.237.72.44]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Nov 2023 02:26:48 -0800 Received: from kekkonen.localdomain (localhost [127.0.0.1]) by kekkonen.fi.intel.com (Postfix) with SMTP id 0221411FBF0; Wed, 29 Nov 2023 12:26:45 +0200 (EET) Date: Wed, 29 Nov 2023 10:26:44 +0000 From: Sakari Ailus To: Andy Shevchenko Cc: Wentong Wu , gregkh@linuxfoundation.org, tomas.winkler@intel.com, hdegoede@redhat.com, alexander.usyskin@intel.com, zhifeng.wang@intel.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/2] mei: Add MEI hardware support for IVSC device Message-ID: References: <1701174846-16316-1-git-send-email-wentong.wu@intel.com> <1701174846-16316-3-git-send-email-wentong.wu@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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,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 X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (snail.vger.email [0.0.0.0]); Wed, 29 Nov 2023 02:26:57 -0800 (PST) On Wed, Nov 29, 2023 at 12:21:32PM +0200, Andy Shevchenko wrote: > On Wed, Nov 29, 2023 at 09:26:47AM +0000, Sakari Ailus wrote: > > On Tue, Nov 28, 2023 at 08:34:06PM +0800, Wentong Wu wrote: > > ... > > > I wouldn't mind having a single Kconfig option for the two drivers either. > > They're always used together, aren't they? > > As far as I understand the topology, here we have one "core" driver and > one "leaf" driver. So, in my understanding they may not go together as > it will bring unneeded code in the future in some configurations. Yes, that is possible in the future if other clients appear. But will there be any? Both drivers appear to be related to IVSC. -- Sakari Ailus