Received: by 2002:ac0:8845:0:0:0:0:0 with SMTP id g63csp877034img; Tue, 26 Feb 2019 10:05:07 -0800 (PST) X-Google-Smtp-Source: AHgI3IZepjG86IYipuyWWO0Z9Tckk8Ji03wB1l247FRPWlizrL998dSu9GDSNT6nbh75ybSk0p5F X-Received: by 2002:a63:ce:: with SMTP id 197mr25200457pga.212.1551204307773; Tue, 26 Feb 2019 10:05:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551204307; cv=none; d=google.com; s=arc-20160816; b=Hcia6UHNHiV40rUqu5OQbXvEuJdDv+ukKAYSzKiF4KTcX9YOasVFbcyCJie+2CnLBn EZFNM07tnankgU8skmgo77EPAs6fOktMTCbhHKoASpSaK9fZnr1r65DR0SM4oD7U/CSh 9rB3R38oycuy9l3PJFc3iaAqNZQTW6qpG3TxWvhi8jxNXMGO2iPuXOKor5rD4rzn9syF 8J9AbmrJ1uPwbP2v7LRDGpuC8AL2EmYrH0Ov9o+892ScxRotM5xv765D4P0i9byg6SxA jdveqNt2hFgPNBxkl7obmoz4umyIhLNf15qYlpjRd5m0nx0rTIVhCswhfypuhWdJ10io l/AQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=DLMUfRftcdA+z4DtHkcvhwkfGUAIA8BZR3fRlZmdzRg=; b=tgPxtBedAqtB9mBIOEHX1XH/UJ2Lfedb+15QEOnyk24OBouj4GRbX+XMDVCw07106c d/f9uLrD3Fo8lm+iNOUi2mwU2tZbilopbFHkos6xZIvRFz8UVv9FdhesA6YfPpFjRt6B 2N53hZAWIo0yiUjixldNs/0IQnd4GgGvoGUqzZmJf2c6tetKk8qHYkW/JKBL24T6gRxx 9Ra2UgmfXqRwUBK8fk6wegEqt6uecUY6Sg954ANm3kH2s+kwb1H0JHCDqGmNPA3demGb woo1VNOcTYx5UUvI1ZeiC32Y8dPzbeJBB4YpbixunwXD9CVWRIwltwBSE8pjV44SFz+u 1wjA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=GBNIrSXT; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i6si1243293pgq.423.2019.02.26.10.04.51; Tue, 26 Feb 2019 10:05:07 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=GBNIrSXT; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728853AbfBZSDJ (ORCPT + 99 others); Tue, 26 Feb 2019 13:03:09 -0500 Received: from mail.kernel.org ([198.145.29.99]:39870 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727801AbfBZSDI (ORCPT ); Tue, 26 Feb 2019 13:03:08 -0500 Received: from mail-qt1-f174.google.com (mail-qt1-f174.google.com [209.85.160.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 3F6BF21850; Tue, 26 Feb 2019 18:03:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1551204187; bh=xGi7ixqN94VIJrKEmRQzMD2uzjcIFe7qUvsMWOhLngA=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=GBNIrSXT481Kkj6jUi2M7/pZfDK4HgbElGDOijq5ntKf01f7vCjfmg2lNH/hJsFlk IeODhfTRIML8VlwjfZIz580U0vXe2NqBLeuQmrZnvpdrTwym5A1UNGrXHnUKaQ1Dbj PXmUxFwr0sd37ZsYKYuEWtS5tdHzgF/C7YHq50BM= Received: by mail-qt1-f174.google.com with SMTP id u7so6745994qtg.9; Tue, 26 Feb 2019 10:03:07 -0800 (PST) X-Gm-Message-State: AHQUAubEmMcQrFEM1N36ayRwaYpFMqV4kkqYEJSyuI2nOh1tcRyLnsXt +pfWh7u5cZTZAB2GiEZrFk6MYVGwhkpvojlayQ== X-Received: by 2002:a0c:8c8a:: with SMTP id p10mr19280940qvb.218.1551204186468; Tue, 26 Feb 2019 10:03:06 -0800 (PST) MIME-Version: 1.0 References: <1549347534-11320-1-git-send-email-srinath.mannam@broadcom.com> <1549347534-11320-2-git-send-email-srinath.mannam@broadcom.com> <20190225213807.GA18852@bogus> In-Reply-To: From: Rob Herring Date: Tue, 26 Feb 2019 12:02:55 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 1/2] dt-bindings: usb-xhci: Add usb-phy-port-reset property To: Srinath Mannam Cc: Greg Kroah-Hartman , Mathias Nyman , Mark Rutland , Linux USB List , devicetree@vger.kernel.org, Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 25, 2019 at 10:57 PM Srinath Mannam wrote: > > Hi Rob, > Thanks for the review, Please see my comments below in line. > > Regards, > Srinath. > On Tue, Feb 26, 2019 at 3:08 AM Rob Herring wrote: > > > > On Tue, Feb 05, 2019 at 11:48:53AM +0530, Srinath Mannam wrote: > > > Add usb-phy-port-reset optional property to set quirk in xhci platform > > > driver which forces USB port PHY reset on port disconnect event. > > > > > > Signed-off-by: Srinath Mannam > > > Reviewed-by: Ray Jui > > > --- > > > Documentation/devicetree/bindings/usb/usb-xhci.txt | 1 + > > > 1 file changed, 1 insertion(+) > > > > > > diff --git a/Documentation/devicetree/bindings/usb/usb-xhci.txt b/Documentation/devicetree/bindings/usb/usb-xhci.txt > > > index fea8b15..ecbdb15 100644 > > > --- a/Documentation/devicetree/bindings/usb/usb-xhci.txt > > > +++ b/Documentation/devicetree/bindings/usb/usb-xhci.txt > > > @@ -40,6 +40,7 @@ Optional properties: > > > - usb3-lpm-capable: determines if platform is USB3 LPM capable > > > - quirk-broken-port-ped: set if the controller has broken port disable mechanism > > > - imod-interval-ns: default interrupt moderation interval is 5000ns > > > + - usb-phy-port-reset: set this to do USB PORT PHY reset while disconnect > > > - phys : see usb-hcd.txt in the current directory > > > > This should be implied by the HCI or phy compatible string (depending > > on who exactly needs the quirky behavior). > Stingray USB HS PHY connected to xHCI port has an issue, if full speed > devices connected to this port then > after all High Speed devices connected to this port are detected at > full speed instead of high speed. > So that we need to do PHY (which is connected to port) reset on xHCI > port disconnect event. > That is the reason we required to add quirk in xHCI. So, by looking at the xhci host and phy compatible strings (or maybe just the phy) you can determine whether you need to reset the port or not. All the information you need is in DT already. Rob