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 5609FC433FE for ; Wed, 24 Nov 2021 06:34:34 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235830AbhKXGhl (ORCPT ); Wed, 24 Nov 2021 01:37:41 -0500 Received: from smtp-relay-internal-0.canonical.com ([185.125.188.122]:45718 "EHLO smtp-relay-internal-0.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229479AbhKXGhk (ORCPT ); Wed, 24 Nov 2021 01:37:40 -0500 Received: from mail-ot1-f71.google.com (mail-ot1-f71.google.com [209.85.210.71]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp-relay-internal-0.canonical.com (Postfix) with ESMTPS id 2C26E3F225 for ; Wed, 24 Nov 2021 06:34:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1637735670; bh=guuwLJoUHG0Pp+fLEKyXR1ouSwDQ+4obA9pivZjno18=; h=MIME-Version:References:In-Reply-To:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=nyT5EXqeVUoqE4osVrTI6DpNnNZtBpnOjtVDUKcnbeqh1CD2YPfVYTXPG7+eRB+oH MztS42+QQ6e8Dblu0aS/c1mbwtsopd67NSLucmj/Dzat7vcLdMWvy3SkF3BE1ELohH D9LBkaE09gZXBYNkqz+VC+yMYMtxdT8H0q8xzfhp+oL00FlkejLW8SVs/lUDPV4hnP UZ8iyKp0lT9dIY35iCu9EPz8zJMwWpmeoza+c8D7yToIl0xZEIMjGan7c26YeuWflV O8NnouMU7lB8cinsYHhGEuJS0qz0Vx1UXvsrq2RjLqgoEkV6ac1UIAQC/uFV/UjEWf SaZs58YCKxA8g== Received: by mail-ot1-f71.google.com with SMTP id n13-20020a9d6f0d000000b00579e30aaa02so381889otq.0 for ; Tue, 23 Nov 2021 22:34:30 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=guuwLJoUHG0Pp+fLEKyXR1ouSwDQ+4obA9pivZjno18=; b=yP+Qm+Og9J8manoOWVlrpzWmpUTKkasCH7sZVWzgGuPSVouCsLG9L+4k32/kmmI5bW 0d//Ya+s4MiibplNcvUZ3Zm2SL9GgV75cQa4jC3HAxZVpx5WAWowVBAvopd/WjywB65L 1qsykCa/KhGVeuiorR7hpvB6bZLb6I545p/W84t3j+VBD95yiGem+NYqKFJlGPIluaOh qs4m3p+giHPz/tVPedKImWemAEPtI3zv41B2Jlo/fG46Hio2SEZFrSVC8JXhkVNbJfJC 8aLym8CjbUBoDb2xRfC28Ir3gwObk/BL8Ic0uLNqmA0mTTF6twY2dA45q5XY+3ggfw5Q sqMg== X-Gm-Message-State: AOAM533CWp4lNkdEFa9JmPH8zlBax0sDBDVK1gzo/6SsX+BmqfBuF3OW FMCEvE5oHj5esBgDSyPh46AjyegNLZQoxvG/dp0JLe30BKWrJqKQ51LE4SdIbbJB5WNoDPdvmyb Wf3lirLWbSr1vtMwmBpMJHZtldGl4WmVAoSFbDIh74YA55IMXCLU9ca/Jsg== X-Received: by 2002:a9d:58f:: with SMTP id 15mr7638199otd.11.1637735669024; Tue, 23 Nov 2021 22:34:29 -0800 (PST) X-Google-Smtp-Source: ABdhPJzk0s+woLJZ3U0nArE/e84jqSdDYeQUZMcxSngcU2abNCsW/mVXbjBkfmDt/xiIeXtDQ8KI08M50nmkjwh5xZk= X-Received: by 2002:a9d:58f:: with SMTP id 15mr7638161otd.11.1637735668679; Tue, 23 Nov 2021 22:34:28 -0800 (PST) MIME-Version: 1.0 References: <20211122161927.874291-1-kai.heng.feng@canonical.com> <14e6c86d-0764-ceaf-4244-fcbf2c2dc23e@intel.com> In-Reply-To: <14e6c86d-0764-ceaf-4244-fcbf2c2dc23e@intel.com> From: Kai-Heng Feng Date: Wed, 24 Nov 2021 14:34:16 +0800 Message-ID: Subject: Re: [Intel-wired-lan] [PATCH 1/3] Revert "e1000e: Additional PHY power saving in S0ix" To: "Lifshits, Vitaly" Cc: jesse.brandeburg@intel.com, anthony.l.nguyen@intel.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, acelan.kao@canonical.com, Jakub Kicinski , intel-wired-lan@lists.osuosl.org, "David S. Miller" Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Vitaly, On Tue, Nov 23, 2021 at 11:22 PM Lifshits, Vitaly wrote: > > Hello Kai, > > > We believe that simply reverting these patches is not a good idea. It will cause the driver to behave on a corporate system as if the CSME firmware is not there. This can lead to an unpredictable behavior in the long run. I really don't want to revert the series either. > > > The issue exposed by these patches is currently under active debug. We would like to find the root cause and fix it in a way that will still enable S0ix power savings on both corporate and consumer systems. I am aware. But we've been waiting for the fix for a while, so I guess it's better to revert the series now, and re-apply them when the fix is ready. Kai-Heng > > > On 11/22/2021 18:19, Kai-Heng Feng wrote: > > This reverts commit 3ad3e28cb203309fb29022dea41cd65df0583632. > > The s0ix series makes e1000e on TGL and ADL fails to work after s2idle > resume. > > There doesn't seem to be any solution soon, so revert the whole series. > > Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=214821 > Signed-off-by: Kai-Heng Feng > --- > drivers/net/ethernet/intel/e1000e/netdev.c | 6 ------ > 1 file changed, 6 deletions(-) > > diff --git a/drivers/net/ethernet/intel/e1000e/netdev.c b/drivers/net/ethernet/intel/e1000e/netdev.c > index 44e2dc8328a22..e16b7c0d98089 100644 > --- a/drivers/net/ethernet/intel/e1000e/netdev.c > +++ b/drivers/net/ethernet/intel/e1000e/netdev.c > @@ -6380,16 +6380,10 @@ static void e1000e_s0ix_entry_flow(struct e1000_adapter *adapter) > ew32(CTRL_EXT, mac_data); > > /* DFT control: PHY bit: page769_20[0] = 1 > - * page769_20[7] - PHY PLL stop > - * page769_20[8] - PHY go to the electrical idle > - * page769_20[9] - PHY serdes disable > * Gate PPW via EXTCNF_CTRL - set 0x0F00[7] = 1 > */ > e1e_rphy(hw, I82579_DFT_CTRL, &phy_data); > phy_data |= BIT(0); > - phy_data |= BIT(7); > - phy_data |= BIT(8); > - phy_data |= BIT(9); > e1e_wphy(hw, I82579_DFT_CTRL, phy_data); > > mac_data = er32(EXTCNF_CTRL);