Received: by 2002:ac0:e350:0:0:0:0:0 with SMTP id g16csp418172imn; Wed, 3 Aug 2022 09:20:15 -0700 (PDT) X-Google-Smtp-Source: AA6agR4DndU32CMrP+/Tm3J5CmowZ7lN4C6/0pNMsIG7FjA5+riahh7aET1IWd4cFI+8iNxU8rme X-Received: by 2002:a05:6402:2398:b0:43d:fd2c:b0a2 with SMTP id j24-20020a056402239800b0043dfd2cb0a2mr4053713eda.172.1659543614992; Wed, 03 Aug 2022 09:20:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1659543614; cv=none; d=google.com; s=arc-20160816; b=abAaO4MjEh8EdD8z/XwN+2D9kZMsv6GnLa0bicctMcZ8LA1yRtlS5l3assElT3tJzK mEikHnLfYoqTlWltkspXxvn9ophwyUO2mURoCxY46otnCYeX98cJUbOSaKQAGA5aiRLm 1NU5OjQB9x7adEUfkgsKmeQ9VKvdBDgxH/EIbPNRg0ovPib57CoKb+NgtsFLOE4nMKsp HQ82HKjptuBgQFd+5+uMBw526jaTsZVJqwf7H6UKHp5gWn24mOPaJq+VN20qKtycPvNA kuJxdej8rhYBUWF6bKM7n5ujl/KxwImlr73fQahX+ZLD3Iz95v+iIQx/up7O+jCtg0iR tmZw== 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=c0dODDqh2BTDWkcsm8LvyYtAPhqLVD3DnY18bWz12SQ=; b=VymbJUoYof3W921ySWM2kKvhJmWvL6X8pz2ISG6MRAcsADd2+U1nha6vRSlgjislIN l5J4aElw/sOknZoBmjzfgVWksmpNZ5dDOIgNEsQ8yZWkDLKufgja6dUX8CCDiGD6yFiU PsdbLkWRDNXkP4ghuY/wtYdkg1VrdHql8VcrWmywtTBeYRG+gA4WgVI1/mv1RI0uTq9R 1HdZGyJSsrXZ/L8QJUhnPvpGG/0rHJ5ze3fHXRv72aZU5NW833eLQ4CY3vuFjtHGD6GM ykJ2EOCZnm3U/bZaz1ptx0pLAkQJJC8a+gAtbVTGnoMxfHjLA/BtXAMa36zyH26D/XBh iBEw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=QbLDW4Ym; 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=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id hr9-20020a1709073f8900b007309e8d567fsi6621304ejc.145.2022.08.03.09.19.47; Wed, 03 Aug 2022 09:20:14 -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=@intel.com header.s=Intel header.b=QbLDW4Ym; 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=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238090AbiHCP5v (ORCPT + 99 others); Wed, 3 Aug 2022 11:57:51 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59296 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238094AbiHCP5t (ORCPT ); Wed, 3 Aug 2022 11:57:49 -0400 Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7E2465FBB; Wed, 3 Aug 2022 08:57:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1659542268; x=1691078268; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=mOIJWP9CHMh9BXUsNu+7KhdpzZU4fbVzJUvkLwDE/es=; b=QbLDW4YmZiS65dZx1CEWrJvy79Ep5fHw6NRbMfoKG2x7kGTK7/BY9h6x 4wOzSyXCu4Yttk7YXpHABiHcQeP1ccKivAF9ajUtM2IAtaDeFTXQqgZH9 3G6wg+5dsLfVYjJk1XM6SgU1owwjSHYty/DBhKZWt1AZSAkz5zpq3cfPY PVSoQEhX5Kq6cih3ZnGk99CaHgS9i/QXq2WdNN/zyAW1JpakaRN4jV7uf aFGnNS31xAV0B5CN4q1WsBUKqH1PnqzwXMc3z6uCwp9Rlg7YZ1X1RDt/B aie24LNOk7vE8wdI3IBU83h0SnFW7qr2Etc8hZPH6p0CNzWYWcVsaoWvM g==; X-IronPort-AV: E=McAfee;i="6400,9594,10428"; a="287270048" X-IronPort-AV: E=Sophos;i="5.93,214,1654585200"; d="scan'208";a="287270048" Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 Aug 2022 08:57:48 -0700 X-IronPort-AV: E=Sophos;i="5.93,214,1654585200"; d="scan'208";a="729250577" Received: from lahna.fi.intel.com (HELO lahna) ([10.237.72.162]) by orsmga004-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 Aug 2022 08:57:44 -0700 Received: by lahna (sSMTP sendmail emulation); Wed, 03 Aug 2022 18:57:42 +0300 Date: Wed, 3 Aug 2022 18:57:42 +0300 From: Mika Westerberg To: Benson Leung Cc: Rajat Khandelwal , andreas.noever@gmail.com, michael.jamet@intel.com, YehezkelShB@gmail.com, linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org, pmalani@google.com Subject: Re: [PATCH] Supporting wake on DP hot events behind TBT/USB4 routers Message-ID: References: <20220803010139.GA32634@rajth-NUC10i7FNH> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo X-Spam-Status: No, score=-7.6 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,RCVD_IN_DNSWL_HI,SPF_HELO_NONE, SPF_NONE 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 Hi Benson, On Wed, Aug 03, 2022 at 08:15:49AM -0700, Benson Leung wrote: > Hi Mika, > > On Tue, Aug 2, 2022 at 10:37 PM Mika Westerberg > wrote: > > > > Hi, > > > > On Wed, Aug 03, 2022 at 06:31:39AM +0530, Rajat Khandelwal wrote: > > > Current implementation doesn't allow user to go into system suspend > > > and simultaneously project the screen on an external display connected > > > to a TBT/USB4 device. This patch enables this feature. > > > > > > Let me know what you think about this. > > > > Please prefix patches to follow the sybsystem style. For Thunderbolt it > > should be "thunderbolt: ....". > > > > This will cause any monitor plug to wake up the system and I'm not sure > > we want that, at least to be default behaviour. If you have a regular > > Type-C (non-USB4/TBT) dock and you plug in a monitor to that, does it > > wake up? > > Speaking for Google and our ChromeOS USB-C policy, yes, if the host is > in S0iX or S3, an already attached USB-C docking station in DP Alt > Mode will respond to a display attach via HPD via an Alert message in > USB PD. We called this feature wake-on-dock. > > We implemented wake-on-dock for DP Alt Mode in the EC, since our EC > handles USB PD anyway, and is handling the PD Alert message which > contains the HPD status. > > However, when the dock supports USB4 or Thunderbolt, those modes don't > involve USB PD for device attach, so our EC doesn't have the role of > waking the system, so something else on the system must, which is this > feature being discussed. Okay understood. Thanks for explaining!