Received: by 2002:a6b:500f:0:0:0:0:0 with SMTP id e15csp181855iob; Mon, 2 May 2022 16:29:36 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxceL157gfeWqnEMFn/OYVLtB0P61pH5Z5piTAdLzibzdhF8hF90GmlhU3eFZnyTPFakNFY X-Received: by 2002:a17:90b:4c46:b0:1d9:f9e1:254 with SMTP id np6-20020a17090b4c4600b001d9f9e10254mr1703527pjb.24.1651534176471; Mon, 02 May 2022 16:29:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1651534176; cv=none; d=google.com; s=arc-20160816; b=ZdS3+GI4TRjQs3n0jAoOt2OLoO9J/6Oj5HQzfTmOMlMUBo++cxXuIFn8tj4+0LmGim bJH6Zdk9yeJK362sTpdMpEhxn5PEoRsynIDQWUboTEWhbBwxTGmW8/+XlXtUUaGZ4o5+ zWpOW/sfu+AxVpFiRmtgs7zsDZhLelm40PUYHUVlvGY/HhOaxQeHLyNDI1AhOpPiimI6 HJfKMQcOEFT5V71hBArfOFcKGwJuLImZ13FkTyC7DhOvZ50y4aWlmRIcoCBPPDsIshTo n4uMHurjaS4kdKkba/fRieBcTI3FG6q+jhVfwSmKtOUv/PF38x4BK8y9REtIMcSP7Jfa 3O3w== 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=eZhGw7YyT/ZrlFIRy3eVj5mDKu5kan3AZzbtehcyrwo=; b=T1a2XzCSnWCHqqV1nauW6baCEj3vMpy6wrtpSGMsrgcmKRBRbTaFRMd06korPd0fIY wjeN9wt+aTTf9JhBQomLrzX3Nk0ptPZWBfvwV3apBGsNPdOdwmEBj1mwq54o+IHCiPbb fZd6R7gdva64OoWyJv62ho4jahxZeYflDxIAu7zVOSLIHO6wszt05ohLWnUUEeJG5+rc ODdbprXaD7FkBVPNAFkjCALe7I+ptGLRr0lSLF1prU/ZlBB9Bgi99gR8UfVqnn2KzdAO CwPenxX9FSxbaezuLLqiyGM0JCFbrkFZMiZSyGnvcQimKmulprTe0PmS3JaXLeB4VPEM wK+A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=NlQQgGyv; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 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. [2620:137:e000::1:18]) by mx.google.com with ESMTPS id d17-20020a056a00245100b004fa3a8e003fsi7809859pfj.246.2022.05.02.16.29.36 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 02 May 2022 16:29:36 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=NlQQgGyv; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 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 973822C125; Mon, 2 May 2022 16:29:26 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1383851AbiEBQIi (ORCPT + 99 others); Mon, 2 May 2022 12:08:38 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48406 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229621AbiEBQIh (ORCPT ); Mon, 2 May 2022 12:08:37 -0400 Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4DA7EBC3D; Mon, 2 May 2022 09:05:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1651507508; x=1683043508; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=mTN/sFuEKOvHaXrCmuIKcyX8bTKXzMSHR2ip8sSamBk=; b=NlQQgGyv35yNl4gAZEIF4PGmPBhe89/v588AeYSSXWjID/0ubTdgwxrl djuVRjvV56tyZCuTBxptbj6WPBKbSCsE3Mjtt76CtbCcLyjWM13ZbposO K11rOIafOmFJhrlF7ptXCp+rMU4H20FfpyvwGm0RmRICx7B1AlTAgUk9n UKHwdlQZqVQZKe1SGm1uN/JjvzInufpMSxX+wFyz2wIck2I46gT2csjyI 0KF6FkQBMVVpOFUTZK9lL/+mUQ8CnrYl7PmpsWjmgifPQFJUKb+0OGB+a 7fktiCcuylRcic1X2aQBacwqOHQ3rtO44ix9/6xZguZtERGoxwpbnA/SR w==; X-IronPort-AV: E=McAfee;i="6400,9594,10335"; a="330239489" X-IronPort-AV: E=Sophos;i="5.91,192,1647327600"; d="scan'208";a="330239489" Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 May 2022 09:05:07 -0700 X-IronPort-AV: E=Sophos;i="5.91,192,1647327600"; d="scan'208";a="516162976" Received: from smile.fi.intel.com ([10.237.72.54]) by orsmga003-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 May 2022 09:05:05 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.95) (envelope-from ) id 1nlYXm-00B6Tb-Tt; Mon, 02 May 2022 19:05:02 +0300 Date: Mon, 2 May 2022 19:05:02 +0300 From: Andy Shevchenko To: Hans de Goede Cc: Paul Gortmaker , linux-kernel@vger.kernel.org, Aubrey Li , Len Brown , linux-acpi@vger.kernel.org, Mark Gross , platform-driver-x86@vger.kernel.org, "Rafael J. Wysocki" Subject: Re: [PATCH 0/4] platform: allow ATOM PMC code to be optional Message-ID: References: <20220428062430.31010-1-paul.gortmaker@windriver.com> <20220428181131.GG12977@windriver.com> <827dc313-33ff-1c91-afaf-7645b655a1be@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <827dc313-33ff-1c91-afaf-7645b655a1be@redhat.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo X-Spam-Status: No, score=-2.5 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=unavailable 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 Mon, May 02, 2022 at 04:30:57PM +0200, Hans de Goede wrote: > On 4/28/22 20:11, Paul Gortmaker wrote: ... > As for users breaking support for BYT/CHT setups because they forget > to enable this, without X86_INTEL_LPSS being enabled BYT/CHT are pretty > much broken anyways and since patch 2/4 adds a "select PMC_ATOM" to the > X86_INTEL_LPSS Kconfig option I'm not really worried about that. > > I'm afraid this patch-set might break some randomconfig builds though, > but I cannot see anything obviously causing such breakage here, so > I think it would be fine to just merge this series as is and then > see if we get any breakage reports. > > Andy, are you ok with me moving ahead and merging this series as is? It seems as is can't be fulfilled due to your own comment, but in general I'm not objecting the idea. So, go ahead if you feel it's ready. -- With Best Regards, Andy Shevchenko