Received: by 2002:a05:6358:5282:b0:b5:90e7:25cb with SMTP id g2csp3971455rwa; Tue, 23 Aug 2022 13:37:30 -0700 (PDT) X-Google-Smtp-Source: AA6agR4gRBSIVVQWZuH62HUBpIbr3wY9/2X3NaAmWrC+aBiXLKS9y7gKXethh6aAZrTXgrPTeyDd X-Received: by 2002:a17:90a:e7c2:b0:1f5:85ab:938c with SMTP id kb2-20020a17090ae7c200b001f585ab938cmr4933997pjb.133.1661287050204; Tue, 23 Aug 2022 13:37:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1661287050; cv=none; d=google.com; s=arc-20160816; b=GUI8P/aR44zmwBwSW7I1puobcWXlrprFlJIRJCkJFKww9DhRKTMPYsGheH8bt415fo Clsz6Lbwx81kQZKgOUN2HdOL8e98LVU21LqHo+gTt5T31gYYwZNK8Ja3ApUNaGnK8T7N jdV27O1EDX8758t5nStGtxZU8Xmtu4IQbqoVGeSNeA1DjPmp7nk3lW6FvjTUKwOOuuTB oGDgPANVVtQ5FbgwCdBriaXTC6CQ6RlIvhNRo3EZ865i7iyg3uf3+LUND2VhGSYb1LYp 9gOaeKtuwAyHEFFoOBncJVzktyvc33MASJnVj+Ar+6/qquZCOxwJ7yPH6Lvu6Ymm6W+f TvGw== 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=Kdb8TxBwkoe3B83ftbWvI5bDuEon4/Ru3EI6rNbmWGQ=; b=htm7J2nLuXjKgqnTkLJNelT4qDlELgxjfUcgfjnb9e3vXm2+9O/Ml4uF5c4AkE35ky 4Ox4TIDRyvgyyyHK4h+6qeLLXRB5Bn+85rY8m+iAXakCRmOJWe6FFDdZCQ2rtFVXUfY4 kR2QYurCmV0DqVhwYb4MKB4rMUUr1TYt8zQRxXGqIbBsTJx9u+7XNy8bf4+FpUlZ9E8F DZ94vQ+zO6IXlTRAx6CHQm3brvMm3QIGDfaLdatj1yxfFrEwS+V7/62ntRRI+5eQ0IOs bYM9rBxbLkBacCk0A2aIwcnrKUAe4qB4CaT1wRYtsJrxUHrjNDL22JQEqCnNhg8lnkIo 9UBQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=Z43eXf7s; 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=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id h6-20020a636c06000000b0042a020bd06bsi13317447pgc.781.2022.08.23.13.37.18; Tue, 23 Aug 2022 13:37:30 -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=@chromium.org header.s=google header.b=Z43eXf7s; 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=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233543AbiHWT45 (ORCPT + 99 others); Tue, 23 Aug 2022 15:56:57 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35342 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232311AbiHWT4i (ORCPT ); Tue, 23 Aug 2022 15:56:38 -0400 Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 37A7A62C0 for ; Tue, 23 Aug 2022 12:05:34 -0700 (PDT) Received: by mail-pg1-x533.google.com with SMTP id 12so13070701pga.1 for ; Tue, 23 Aug 2022 12:05:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc; bh=Kdb8TxBwkoe3B83ftbWvI5bDuEon4/Ru3EI6rNbmWGQ=; b=Z43eXf7sSp1pEmvfjoOW73lKT1LlllQnMFnv9B3dxhgO56wTdDsGRHhL+uMhTwxJxe 6hNMX3LPN8+gR924uesklbfSY7g4v3CrRBOEhPQPmQprz2riJgnmlZV6S1ItTsUk6p0f Yai/xfjAr7wSQXab8eWRJEHot/0yLlRO3HyYU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc; bh=Kdb8TxBwkoe3B83ftbWvI5bDuEon4/Ru3EI6rNbmWGQ=; b=dh1UJ54rQMstCnc7EBbWcLGIifFvjokZJgnIfsA3Z/vm63h8Q4BP04XEcjFLKxFF56 Mo8k7DVnyVKaDLOLCG8b7MpTNN7a4PuIFFJvSGTT0WDuDY7qQqGR52BOT16ZT5iN3+Ne o6Dh8CIJR2yK3X0DDuqHovw6W4dNPRyxMf8glDNQupYhgSRQWHRTPLQ2UNyigVsyRlty gMmnQFSntRRODP7fPKxJDtocWR9/h+QhIb2Kt6MIRyOGPNHiAmW//noFl5W4c5fR6bst vKO8oeCdrhPrQ2KJKZ9VbOF9YJBsOqBksdkF3xBl7mVWJ/0nvfUHbqchLZhWUMgK6BMj Hvxg== X-Gm-Message-State: ACgBeo2lJ6YSd7bDTIwTsL74dLZ3l92jgqzdB1oNl03NVboRa7g+1AVD xA1ZKFepQUhbaAt/RKL/rTfPoA== X-Received: by 2002:a63:5418:0:b0:42a:d773:cbd6 with SMTP id i24-20020a635418000000b0042ad773cbd6mr5543100pgb.106.1661281533664; Tue, 23 Aug 2022 12:05:33 -0700 (PDT) Received: from localhost ([2620:15c:11a:202:fee6:a961:5d1d:553]) by smtp.gmail.com with UTF8SMTPSA id e3-20020a170902784300b00172de80fec4sm5824250pln.69.2022.08.23.12.05.32 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 23 Aug 2022 12:05:33 -0700 (PDT) Date: Tue, 23 Aug 2022 12:05:31 -0700 From: Matthias Kaehlcke To: Stephen Boyd Cc: Andy Gross , Bjorn Andersson , Konrad Dybcio , Michael Turquette , linux-arm-msm@vger.kernel.org, Johan Hovold , Douglas Anderson , Krishna Kurapati , linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org, Bjorn Andersson Subject: Re: [PATCH 1/2] clk: qcom: gcc-sc7180: Keep USB GDSC power domain on when USB wakeup is enabled Message-ID: References: <20220822115246.1.I45235b7c40997bc2abf813e4722b4dcdd6aecf6b@changeid> <20220822235207.A4D8EC433D6@smtp.kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20220822235207.A4D8EC433D6@smtp.kernel.org> X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,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 Hi Stephen, On Mon, Aug 22, 2022 at 04:52:05PM -0700, Stephen Boyd wrote: > Quoting Matthias Kaehlcke (2022-08-22 11:53:10) > > Set GENPD_FLAG_ACTIVE_WAKEUP for the USB GDSC power domain of SC7180. > > Why? Does it fix something? Please add details to the commit text so we > know how urgent of a patch it is and why it is important. Without it USB is broken after resume when the PHYs remain enabled during suspend. Johan just sent a patch [1] that always disables the PHYs (again) during system suspend, with that this series shouldn't be needed. It is possible that in the future we add a mechanism to keep the PHYs on depending on some config option (quick, kconfig, ...). If that happens we'll have to revisit this series, for now it shouldn't be needed assuming Johan's patch gets landed. [1] https://patchwork.kernel.org/project/linux-usb/patch/20220823124047.14634-1-johan+linaro@kernel.org/