Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp1156517rwb; Thu, 1 Dec 2022 13:13:20 -0800 (PST) X-Google-Smtp-Source: AA0mqf5YSXVIXS3IjF0RJnEhDL6iIDEJOAeSSc8FxmunCWH1S+oRoZxDNFJAyFhb0ZOAPmDuZKh3 X-Received: by 2002:a17:90a:d510:b0:219:2f88:ae3a with SMTP id t16-20020a17090ad51000b002192f88ae3amr24756853pju.106.1669929200608; Thu, 01 Dec 2022 13:13:20 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1669929200; cv=none; d=google.com; s=arc-20160816; b=n+wwVJwIWpzwr2zTUxXJyzfmdYrP353WIHzHEoLx75LLEvlfFUmWu5fXS4GMRFPVQf 5/fCUfbjkeH1c7RiiP08Veb297VYNy/l7h+SbNkBSOSRIU62jX2p0FdFFeqWw4CWbtMq lLVf+f61CZezTesmJUjaiKW3ujQydXhar7vRWgZCd7BelTPrHQj7WLNyInhMnhMBuZEh BrjS3Nma/06gfh3yHta4lZ4YNG3qUShsYaJ9MdjsXtf0jf6Oi5UGa3udhi5jc+p+v7oC 2c0tBMrtGpYrzZPUTCUfxLbFggBZVi4M61fTckLqngX2bjXMYgP/ihV5Djj4UzYeaa2+ onyA== 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=GjdRTH/tOOqfRcgeR10agDzqdXeX6/1B2Il2FJNpk9o=; b=mIp7H1+kR1smDo/fFBI0M/n8D9AEQbWt8YaKJBrFhaqCvYH1Qrjf6K5l2nD1BqBp1w Gok2k2JapNCE4MKm3HL11D285YIRRdIBXMyD3H2jfR3CQUScp3maKLM8ackPTTSCdFbJ spwoC6StDOSHtrPl37mOa/w3x141AEHKOzFoysF7Arwg31GgzHUGq5WmYQ0MJIT29Aos vkv1EzBlpJkglbObp5iIrs30ar9YH7id0asW/dt7RHDSpFYlRmC2sbkc1BwD+pcORwis /FEA2RC2ovGunXYQF9pngbS2BKcTz3IWu525mLygP0wckf4qb64VMtJX11zVoChjRJAW J/jQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=lQLmOg9O; 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 w8-20020a63fb48000000b00476e21bc1bdsi5265253pgj.162.2022.12.01.13.13.10; Thu, 01 Dec 2022 13:13:20 -0800 (PST) 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=lQLmOg9O; 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 S229623AbiLAVBC (ORCPT + 81 others); Thu, 1 Dec 2022 16:01:02 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52840 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230105AbiLAVAx (ORCPT ); Thu, 1 Dec 2022 16:00:53 -0500 Received: from mail-ej1-x62a.google.com (mail-ej1-x62a.google.com [IPv6:2a00:1450:4864:20::62a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0AC43B3933 for ; Thu, 1 Dec 2022 13:00:53 -0800 (PST) Received: by mail-ej1-x62a.google.com with SMTP id ud5so7164878ejc.4 for ; Thu, 01 Dec 2022 13:00:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=GjdRTH/tOOqfRcgeR10agDzqdXeX6/1B2Il2FJNpk9o=; b=lQLmOg9OjSraxzekZjSgcm0t0iOOSlEZMV9S9mHYGB46UbHRWvnPNYLLg2Pqv5Gy0A FazJhKaIxO2+yKoQkR/bHdjEXiSLyVZKy5yv7aiUwvJXuVwBtDkUxF2x4I3SrzXBZIAR erJ5ii7VS5paRQ0D2v3aye1xNNntMdS4hBygo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=GjdRTH/tOOqfRcgeR10agDzqdXeX6/1B2Il2FJNpk9o=; b=oHRie2pCfnXPIEXiY3IpjP5gnwVsjgvWQpjUTJLglYbAucCxfhx70bANXb8kSCGF7k H9+Zcdp6VnSlfYuYJZNTadx3tN0K2hsvGafm+/TcSdz2FcaomtFWkS47W0QZILXWX3OC dLplljxKb30kdYGvSbaiKqPw5aFRNSmu06+3ijytx8rLDVcHa7Be2+EnHMrfSSv9ZfPp 7VFoCeO7Ex1u3rTrzQvXlWwWZjKmtql0rFCIHfN95I+86JooCSHcxNRWzWI3br1uhiQn xx/9krYBPS6LXz+YfIuon/Ys/ek0nPFc149ajDnP5p21Diuonhuadl+LGfYhSsGrJ35a k3yw== X-Gm-Message-State: ANoB5plF73STru0hSQIFGpxTLqhg+10cBH2WWX96VJKsQ/43Z9gZ2IG8 RgNZUh0sIXwcHxaFVWJgKS+DCjahYVKri1cMKGpV8Q== X-Received: by 2002:a17:906:79d3:b0:78d:b6f7:53c0 with SMTP id m19-20020a17090679d300b0078db6f753c0mr44042365ejo.527.1669928451351; Thu, 01 Dec 2022 13:00:51 -0800 (PST) MIME-Version: 1.0 References: <20221130231936.1666390-1-wonchung@google.com> In-Reply-To: From: Benson Leung Date: Thu, 1 Dec 2022 13:00:35 -0800 Message-ID: Subject: Re: [PATCH] platform/chrome: Create new USB driver for RGB keyboard in ChromeOS devices To: Prashant Malani Cc: Won Chung , linux-kernel@vger.kernel.org, chrome-platform@lists.linux.dev Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-9.3 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,USER_IN_DEF_SPF_WL autolearn=no 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 Prashant, On Thu, Dec 1, 2022 at 12:10 PM Prashant Malani wrote: > > Hi Won, > > On Wed, Nov 30, 2022 at 3:19 PM Won Chung wrote: > > > > Without any driver bound to RGB keyboard, it may not be suspended > > properly, preventing USB xHCI to be suspended and causing power drain. > > Create new USB driver for RGB keyboard so that it can be suspended > > properly. > > This seems like overkill. Can't you set this from USB's sysfs nodes > like power/control [1] ? > > [1] https://www.kernel.org/doc/html/latest/driver-api/usb/power-management.html#the-user-interface-for-dynamic-pm > > > Best regards, > > -Prashant We're seeing some behavior where a bound driver is needed in order for this USB device to properly enter suspend state. Just manipulating the power/control and other sysfs nodes for this usb device when there's no driver in the kernel doesn't seem to affect the device's ability to drop into a usb low power state. Also, I synced with Won about this offline, but the primary concern is not this prism usb device runtime suspending, it's actually it's ability to enter suspend state during system suspend. Right now, this internal usb device is keeping the whole system from entering lower S0iX states because it's not sleeping. This driver patch doesn't address that yet, but I'd like Won to dig down and see if he can get it suspending at suspend time too. -- Benson Leung Staff Software Engineer Chrome OS Kernel Google Inc. bleung@google.com Chromium OS Project bleung@chromium.org