Received: by 2002:a5d:925a:0:0:0:0:0 with SMTP id e26csp809712iol; Sat, 11 Jun 2022 20:23:19 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwStvMHRgxpc6EXol4d/U2Y+6rG8wpyJc9o5kZIytkxf6ha8Ue04/XxO5b3z8As5HwcAw0Z X-Received: by 2002:a17:907:160c:b0:711:3b56:dc7 with SMTP id hb12-20020a170907160c00b007113b560dc7mr35138583ejc.587.1655004199694; Sat, 11 Jun 2022 20:23:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1655004199; cv=none; d=google.com; s=arc-20160816; b=LV+u4oBy5pXVU1NPAQeI+b83f3XXEMddVI+TkqW7mHs9gSpkHtz0HM22wurlDpbKlk Tx4ig0sIFJ4rVJzt2zg5nbro9K7VsI+ZHL8vXgljuSc/ZAGXDE0V/YAJHoGAcfkqxeY6 6VVfkQEiVRPt+jIZqKhtofKtXp6TPDNl8alPSObSH9u8v99wqNaALlynIvIQkiX7ISmj B+i+7eItUBpiYNcd+EbUxg0dYUAzvKVe3gJl0t8IxIYEbe7etTmJ4dC1QEG2Qh3YHWEc BVZhNOzyrT70/kVhFTGkWUlOSi2zHouf/J9kueOjApI3XLrp+UQgAWwCf4ntO0vHDJ8k 6Ehw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=dNvZMKbt+7/Kf7YBjNNI5bE9XcnXeFt+vWqBn00F0RE=; b=xTezK7PDhnoJx1+D8kKXBzggndgaw3xVqOATqeKMArvLEECw/Cp0ZIfmZHKv6Xvaso HLRQnQCH/q1Yci8velAncG9PCMctbjntZ1N5WOZsuE46uWi3yDxu5NoQjX/Jt/v6PxXY kmbT+Q0tJWGZULN6FVm/LW0Vwu38m5+wCpf1kSHFyR72IG/PVNY+2S3DcKMcQ1NwTX/f 9yriylb0Px+0bQIdMUpIEmJnLiheWUYq6H9vY9zj8zJfz78Vo01Ok46HlOwoLGcXW2VK Q3eSgLG0jFbYzs0AyerZMYrccEf/zyHp5PHkZmgrShoyb7cCwZflxzvJyG3s5IEC0vD7 9U0w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=BavePnvB; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id g23-20020a50d0d7000000b0042e1a76680asi3864679edf.394.2022.06.11.20.22.55; Sat, 11 Jun 2022 20:23:19 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=BavePnvB; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232350AbiFKWBf (ORCPT + 99 others); Sat, 11 Jun 2022 18:01:35 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37212 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229473AbiFKWBd (ORCPT ); Sat, 11 Jun 2022 18:01:33 -0400 Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com [IPv6:2a00:1450:4864:20::531]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A4E6C3E5F2 for ; Sat, 11 Jun 2022 15:01:32 -0700 (PDT) Received: by mail-ed1-x531.google.com with SMTP id h19so2982568edj.0 for ; Sat, 11 Jun 2022 15:01:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dNvZMKbt+7/Kf7YBjNNI5bE9XcnXeFt+vWqBn00F0RE=; b=BavePnvBNEsyNXtcZaLBDnP8bcFQNxj3xyZaoBRF7UUU0pp6X7CX8we+nL7XD2td5K CVcJH6mNbpjv817NTr+DzsKFeUVYkswE3RWmwtP2aLdPXaa0kIa62ieX9TwYAj9nxEGc uDarGbZy4+zjPxmy6+EPIywGZBvrrNKBKX6h6ymU3/Rao1qLsw8hb6B/8oPLMkw5JLu6 CIZGJ+vmcjnZahIoA1VlQekqhJr4wSoc8cbkhUp1lNqmh+gXb5kNBR5+sr8ZgySadMFd DJhjUrsoGFSkQjpCAUwUR0uHLTxidMSMP9HGVjewTue32YtMcIwl5SHFrVWaI39o73+O Nm2Q== 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=dNvZMKbt+7/Kf7YBjNNI5bE9XcnXeFt+vWqBn00F0RE=; b=DFX5lzPLsL40hb2XLkdXdwp05q06pZtT3FNDa7EvkiEyq5PGNH0szNWQcVWW4MPIX9 XE2HSB5Eb/2bP9F4sFcAyFWtYOPmcnzs/zLUR8Bh5reja5FQwwVtwA+CR5CX31awTrhh pgsAFibAbNrMlP4YRwhJYw3TyoiQeNIf1c5xpXAIzvQc0EquHpmQM/oMKgUdWUo8qDJu aH8v33rAE6ZUD2cpAR4eXIK4PHnN6uBrgbKH2m9i0D0Vi6qv8FGlwhP1ZFIxlmzjtSPf eBTVwjqjDl43clb0f3tlHfRvzoTnL01YY1kTWUbo1FiXPb0UR+2t0JrogmcaMmfhXvOF KHiQ== X-Gm-Message-State: AOAM532g0prFkQhRh3SqQhOOUDp8/QlDK7Z+ittrA6BSsAs/zqyx/EQf YjlfYviGYEmDd/E6jbQz7EpyFLl4NDTaVqIm1+TLS0Ob1vUuiw== X-Received: by 2002:a05:6402:2405:b0:431:6ef1:e2a with SMTP id t5-20020a056402240500b004316ef10e2amr34447712eda.26.1654984891012; Sat, 11 Jun 2022 15:01:31 -0700 (PDT) MIME-Version: 1.0 References: <20220611061825.4119270-1-swboyd@chromium.org> In-Reply-To: <20220611061825.4119270-1-swboyd@chromium.org> From: Guenter Roeck Date: Sat, 11 Jun 2022 15:01:20 -0700 Message-ID: Subject: Re: [PATCH v2] platform/chrome: cros_ec: Always expose last resume result To: Stephen Boyd Cc: Benson Leung , linux-kernel , patches@lists.linux.dev, Guenter Roeck , "open list:CHROME HARDWARE PLATFORM SUPPORT" , Evan Green , Rajat Jain , Matthias Kaehlcke , Hsin-Yi Wang Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-17.6 required=5.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF, ENV_AND_HDR_SPF_MATCH,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE,USER_IN_DEF_DKIM_WL,USER_IN_DEF_SPF_WL 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 On Fri, Jun 10, 2022 at 11:18 PM Stephen Boyd wrote: > > The last resume result exposing logic in cros_ec_sleep_event() > incorrectly requires S0ix support, which doesn't work on ARM based > systems where S0ix doesn't exist. That's because cros_ec_sleep_event() > only reports the last resume result when the EC indicates the last sleep > event was an S0ix resume. On ARM systems, the last sleep event is always > S3 resume, but the EC can still detect sleep hang events in case some > other part of the AP is blocking sleep. > > Always expose the last resume result if the EC supports it so that this > works on all devices regardless of S0ix support. This fixes sleep hang > detection on ARM based chromebooks like Trogdor. > > Cc: Evan Green > Cc: Rajat Jain > Cc: Matthias Kaehlcke > Cc: Hsin-Yi Wang > Fixes: 7235560ac77a ("platform/chrome: Add support for v1 of host sleep event") > Signed-off-by: Stephen Boyd Reviewed-by: Guenter Roeck > --- > > Changes from v1 (https://lore.kernel.org/r/20220610223703.3387691-1-swboyd@chromium.org): > * Fixed typo > > drivers/platform/chrome/cros_ec.c | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git a/drivers/platform/chrome/cros_ec.c b/drivers/platform/chrome/cros_ec.c > index b3e94cdf7d1a..3abef9747482 100644 > --- a/drivers/platform/chrome/cros_ec.c > +++ b/drivers/platform/chrome/cros_ec.c > @@ -135,10 +135,10 @@ static int cros_ec_sleep_event(struct cros_ec_device *ec_dev, u8 sleep_event) > buf.msg.command = EC_CMD_HOST_SLEEP_EVENT; > > ret = cros_ec_cmd_xfer_status(ec_dev, &buf.msg); > - > - /* For now, report failure to transition to S0ix with a warning. */ > + /* Report failure to transition to system wide suspend with a warning. */ > if (ret >= 0 && ec_dev->host_sleep_v1 && > - (sleep_event == HOST_SLEEP_EVENT_S0IX_RESUME)) { > + (sleep_event == HOST_SLEEP_EVENT_S0IX_RESUME || > + sleep_event == HOST_SLEEP_EVENT_S3_RESUME)) { > ec_dev->last_resume_result = > buf.u.resp1.resume_response.sleep_transitions; > > > base-commit: f2906aa863381afb0015a9eb7fefad885d4e5a56 > -- > https://chromeos.dev >