Received: by 2002:a05:6358:9144:b0:117:f937:c515 with SMTP id r4csp4087968rwr; Mon, 8 May 2023 02:40:53 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ6goE7GGHt0Y0YEyThEsR5JonLn/CBL6i65RAb2FQ/5tgJ4Acf7nUDWzlMDw3KMaFzyvOZn X-Received: by 2002:a05:6a21:32a8:b0:100:8258:1679 with SMTP id yt40-20020a056a2132a800b0010082581679mr3017638pzb.0.1683538853613; Mon, 08 May 2023 02:40:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1683538853; cv=none; d=google.com; s=arc-20160816; b=mTzYg+xUgUFOKqx1fTHWt+BmZ02bpZVaWd4RjvXT3kqeTaazq5fvBvnngj8ApGljj+ cpC1urJvr1383zN6IQ7V84MLHkrljKJ1QkPN9qu3auQPoq5gyUZOJyGSiXIbLi3bEfWa hi8/qyrO5S2+d1ELiWfg1r4VsdpgGMF4XWBDci4//x4cRNcJZJauGSTGapDccBIo9Xh6 3GOkyuL2A2vGCyESrFLQczFOGLisMDhKdO9jQe0Pkq8l2yHRC2MH898iL4A7Wd2iKDnm qCLfwSu4dMjvf3xWRxrDb1nhICzKm2FczmeBmQj69/wMOxJgO9yuvXroeGdHghLRZD2N mfSg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id; bh=+/a6G2UoUzN7ROYqIMkZUX/9XAp2OeuV0RGHUUiGb4k=; b=xrn1/pgGhKEOqETHXRrfPQrmq2IHwUYL9f1OELw1t7VeVsSIwZH2/UTrNgnJswUZqu 1UkyWL/AjsQ+psu3Loi34xoXwNKMy0N3Vg4cILsISJ/CRxtrUNRlGjbexZnEbmphOKwc ghWBGZS5uQ1WG8TJpKI9EtPTdfvKvKQ3WIvLJW3gh7vcqPY2K6ziqUpKX03/WeNU9402 2BCCUMDpAmyZWCPiFfgImYPu39rhXbwunB68mDLm4an+7G5gKNFKm5h7J0tnPEH1/5UK AFjBVxwJA6lD63sKrS9bTuXWFiItuSNa4yzul7/xz1I7BxFYP4RBKXIHHUUuRWVcx6Db jw4A== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id z68-20020a633347000000b00509461bbf1csi7705630pgz.79.2023.05.08.02.40.40; Mon, 08 May 2023 02:40:53 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233468AbjEHJeG (ORCPT + 99 others); Mon, 8 May 2023 05:34:06 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36540 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229491AbjEHJeE (ORCPT ); Mon, 8 May 2023 05:34:04 -0400 Received: from mx1.zhaoxin.com (MX1.ZHAOXIN.COM [210.0.225.12]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5543BFD for ; Mon, 8 May 2023 02:34:01 -0700 (PDT) X-ASG-Debug-ID: 1683538437-086e237e516de40001-xx1T2L Received: from ZXSHMBX2.zhaoxin.com (ZXSHMBX2.zhaoxin.com [10.28.252.164]) by mx1.zhaoxin.com with ESMTP id Yl6PW2wbkHolTVsk (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 08 May 2023 17:33:57 +0800 (CST) X-Barracuda-Envelope-From: WeitaoWang-oc@zhaoxin.com X-Barracuda-RBL-Trusted-Forwarder: 10.28.252.164 Received: from zxbjmbx1.zhaoxin.com (10.29.252.163) by ZXSHMBX2.zhaoxin.com (10.28.252.164) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.16; Mon, 8 May 2023 17:33:57 +0800 Received: from [192.168.3.72] (222.128.104.110) by zxbjmbx1.zhaoxin.com (10.29.252.163) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.16; Mon, 8 May 2023 17:33:56 +0800 X-Barracuda-RBL-Trusted-Forwarder: 10.28.252.164 Message-ID: <734023dc-3001-3653-399f-aa66b99ba27e@zhaoxin.com> X-Barracuda-RBL-Trusted-Forwarder: 192.168.3.72 Date: Tue, 9 May 2023 01:33:54 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 Subject: Re: [PATCH v3 1/4] xhci: Add some quirks for zhaoxin xhci to fix issues Content-Language: en-US X-ASG-Orig-Subj: Re: [PATCH v3 1/4] xhci: Add some quirks for zhaoxin xhci to fix issues To: Mathias Nyman , , , , CC: , , References: <20230506201536.7362-1-WeitaoWang-oc@zhaoxin.com> <20230506201536.7362-2-WeitaoWang-oc@zhaoxin.com> <71834813-4f59-a453-5d17-1a44010047ad@linux.intel.com> From: "WeitaoWang-oc@zhaoxin.com" In-Reply-To: <71834813-4f59-a453-5d17-1a44010047ad@linux.intel.com> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [222.128.104.110] X-ClientProxiedBy: ZXSHCAS1.zhaoxin.com (10.28.252.161) To zxbjmbx1.zhaoxin.com (10.29.252.163) X-Barracuda-Connect: ZXSHMBX2.zhaoxin.com[10.28.252.164] X-Barracuda-Start-Time: 1683538437 X-Barracuda-Encrypted: ECDHE-RSA-AES128-GCM-SHA256 X-Barracuda-URL: https://10.28.252.35:4443/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at zhaoxin.com X-Barracuda-Scan-Msg-Size: 1589 X-Barracuda-BRTS-Status: 1 X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210 X-Barracuda-Spam-Score: 1.09 X-Barracuda-Spam-Status: No, SCORE=1.09 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests=DATE_IN_FUTURE_06_12, DATE_IN_FUTURE_06_12_2 X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.108481 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.01 DATE_IN_FUTURE_06_12 Date: is 6 to 12 hours after Received: date 3.10 DATE_IN_FUTURE_06_12_2 DATE_IN_FUTURE_06_12_2 X-Spam-Status: No, score=-1.8 required=5.0 tests=BAYES_00,DATE_IN_FUTURE_06_12, NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE 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 2023/5/8 17:01, Mathias Nyman wrote: > On 6.5.2023 23.15, Weitao Wang wrote: >> Add a quirk XHCI_ZHAOXIN_HOST for zhaoxin xhci to fix issues, >> there are two cases will be used. >> - add u1/u2 support. >> - fix xHCI root hub speed show issue in zhaoxin platform. >> >> Add a quirk XHCI_ZHAOXIN_TRB_FETCH to fix TRB prefetch issue. >> >> On Zhaoxin ZX-100 project, xHCI can't work normally after resume >> from system Sx state. To fix this issue, when resume from system >> Sx state, reinitialize xHCI instead of restore. >> So, Add XHCI_RESET_ON_RESUME quirk for ZX-100 to fix issue of >> resuming from system Sx state. >> >> Cc: stable@vger.kernel.org >> Signed-off-by: Weitao Wang > > > I'd split this series into different logical parts: > > patch 1/4 >   Set XHCI_RESET_ON_RESUME quirk to ZHAOXIN host to fix resume issue. >   cc: stable > > patch 2/4 >   Add XHCI_ZHAOXIN_TRB_FETCH quirk flag together with code that allocates double pages >   cc: stable > > patch 3/4 >   Add XHCI_ZHAOXIN_HOST quirk flag together with code that corrects USB3 roothub minor > version >   cc: stable > > patch 4/4 >   Set XHCI_LPM_SUPPORT quirk together with code that sets tier policy and u1/u2 timeouts, >   Don't add stable as this is about adding feature support. > Okay,no problem, I'll modify this patch series according to above solution and order in the next version. Best Regards, Weitao > (Accidentally replied to older v2 series with the above comments) > > Thanks > -Mathias > > .