Received: by 10.213.65.68 with SMTP id h4csp1560imn; Tue, 27 Mar 2018 14:59:36 -0700 (PDT) X-Google-Smtp-Source: AIpwx4++Y7QTuUmKCVuhNASLq6N1HuLQI078I2cEBQ6AieGWx8lQmUslLbYCVQPO9riLcIL9hjMV X-Received: by 2002:a17:902:f24:: with SMTP id 33-v6mr1019018ply.242.1522187976578; Tue, 27 Mar 2018 14:59:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522187976; cv=none; d=google.com; s=arc-20160816; b=oJUjM1leH1MvalWpI7PPD7vZNiVdskKnCMgJ5kZPRr2tWVgwcGFSk/aWsj5kv/uCtD R/PWAkO1FyivdmY39hu/e74S97tVL37vgefmLCjqdoSb43LnnQWBHICqGHAQo/+sFw5w RjYUIij5NcxyTDjW9w/U2bMeHX7LF0CQFl123cl4qoEBXPRPsRIUfXGi4IfwUcqcIsb1 tVyyWTZgy+8y0EXVQz0iyZSHnW4UgFdz0ZT7KU7gQyUUZvuKfDXxMZ8MXP/PgIAO3ytU K6agJTfNQFpRNemjEuYTb9HlS8H6KhMMVsrkCcNETRR9cPFctcOHJH+6wNmUahRFYdP9 APbw== 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 :references:in-reply-to:mime-version:dkim-signature:dkim-signature :arc-authentication-results; bh=rfYPSAhmbUct3rNIWXVDQg1ILAKDei38cFBYN0XeA3U=; b=W9CG1sqsAmVEziNsw3/yq4BRqFQLhUJz3yil/npkqLH/1FhNGtjwG+pF8XVoxM9Phb LJrPIdud80M650GMVTMTCaCyd3CjPS1gz71IKqzyOTlnkeFhbMsYJoMb3BMcAfyMer7u LVJP9Q1qkQbhqCU5/Hj8fsR1432OY2M8mYPQIAVv//KVFRBOBuooO+7JC0RXGXINwZ5J 5YoJ/efV4cR0AxEhURBTILf5fs9VNJGFeMqr6ChVvQgT+5ZXJmTNKk7YJDnQsbxtMc3x vQHnbHVMBgjZmg9DVd+r5zjTqfMhQwq/gxdMKNCCUt8R77ZLfbC9oxe8vI3/yvSnephe BSTg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@google.com header.s=20161025 header.b=hIt00Z+2; dkim=fail header.i=@chromium.org header.s=google header.b=UTRyhNAX; 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=fail (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y2-v6si2131780pli.242.2018.03.27.14.59.22; Tue, 27 Mar 2018 14:59:36 -0700 (PDT) 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=fail header.i=@google.com header.s=20161025 header.b=hIt00Z+2; dkim=fail header.i=@chromium.org header.s=google header.b=UTRyhNAX; 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=fail (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752179AbeC0V6B (ORCPT + 99 others); Tue, 27 Mar 2018 17:58:01 -0400 Received: from mail-ua0-f177.google.com ([209.85.217.177]:44363 "EHLO mail-ua0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751167AbeC0V56 (ORCPT ); Tue, 27 Mar 2018 17:57:58 -0400 Received: by mail-ua0-f177.google.com with SMTP id s92so272183uas.11 for ; Tue, 27 Mar 2018 14:57:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=rfYPSAhmbUct3rNIWXVDQg1ILAKDei38cFBYN0XeA3U=; b=hIt00Z+2lZIvy+mhkjXBWCNYynzAigqzfFQsCb8wkzJRGZI3SQR+OTW3iDLIUI3NdT xnk/KlhZ15iPU9t1BFeGWgp6R9nruEcNaBZEsaaqUFzXJ3luq6JV9WHaFp40hmBL7TUj vXtXrS12PVlmbS7cKxNBg3k2Tfdhl3+GKqeDc1mFrzy/fYCFiuEnRSUUTlMCS1XhxjP5 QsH8/vXhQarkEC0/Tca8SYPGyKN8IL66LOIDVXpY3muhs0h78OmTE82xdla6glaIZGl1 2/5v9jXHCOMGZAG13Sbege4A7YnpQ4WYY65haahPdIHUxe9Tnr3U00lGmIKOYphFp3pY ETDg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=rfYPSAhmbUct3rNIWXVDQg1ILAKDei38cFBYN0XeA3U=; b=UTRyhNAXmUtN6lIAWZcVl7HS6uDgyZVTHZnUarZGgw9qgKQ3lAcWKSD0oncrsECaxH VU66BwCenf7PqJg4jN7lJmz1CZ0VgSWnWOXIE7VMJiukJPlwl3jNXvtYEz4JNaqyS/GL pUw2QaYiI5hLQ1/I4INYL3NNM2lSZrKuXu/A0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=rfYPSAhmbUct3rNIWXVDQg1ILAKDei38cFBYN0XeA3U=; b=AKQXS571zJXzxvuD3HD2VpbaDGVwlrnbD+HlG2Jw3tgnl7VW5inAj7oEnnT9ZvlMpB wSU4l9nxeibHabgcO0UHXSpaMMMKaUj0LByeOIjqYXeAglCY0wh+UUNlI5rZvDN8MwK6 s6140XA5GFclpKY04al/DeMgjSiz8/imptU1C7kHbW2eVr9ApmWPsNtyF3bY6/KP5CVi UhZHZ/gR5gfZYwGmry5qvdV4/OnDg1QkMRmxaTVQYl4Cg+0dWfcYLAqCwJOzP0CNdafv zZrZVHmBT3P4dySxBsf9baDv44wk5Ca/uVBdvEC/DolKDH6yugRG4SY9UABCZuM9gzja aXeA== X-Gm-Message-State: AElRT7GrT21Nb0ZqkEoLPHAskTevn7dvQpVok3nIdPs9VgaJoAXHMpSm IXIU5/ukb/XXeYj5BnQ8k+LGE36BSRlQVb1PHkQuqg== X-Received: by 10.159.60.161 with SMTP id s33mr874038uai.64.1522187876473; Tue, 27 Mar 2018 14:57:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.31.4.8 with HTTP; Tue, 27 Mar 2018 14:57:55 -0700 (PDT) In-Reply-To: <1521785487-29866-6-git-send-email-mgautam@codeaurora.org> References: <1521785487-29866-1-git-send-email-mgautam@codeaurora.org> <1521785487-29866-6-git-send-email-mgautam@codeaurora.org> From: Doug Anderson Date: Tue, 27 Mar 2018 14:57:55 -0700 X-Google-Sender-Auth: 41lKj8kyFwqMyvWtYo0A-hKdUmk Message-ID: Subject: Re: [PATCH v3 5/6] dt-bindings: phy-qcom-usb2: Update bindings for sdm845 To: Manu Gautam , Rob Herring Cc: Kishon Vijay Abraham I , LKML , devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org, Mark Rutland , Vivek Gautam , Stephen Boyd 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 Hi, On Thu, Mar 22, 2018 at 11:11 PM, Manu Gautam wrote: > Update compatible strings for USB2 PHYs on sdm845. > There are two QUSB2 PHYs present on sdm845. Few PHY registers > programming is different for these PHYs related to electrical > parameters, otherwise both are same. > > Signed-off-by: Manu Gautam > --- > Documentation/devicetree/bindings/phy/qcom-qusb2-phy.txt | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > > diff --git a/Documentation/devicetree/bindings/phy/qcom-qusb2-phy.txt b/Documentation/devicetree/bindings/phy/qcom-qusb2-phy.txt > index 42c9742..b99a57f 100644 > --- a/Documentation/devicetree/bindings/phy/qcom-qusb2-phy.txt > +++ b/Documentation/devicetree/bindings/phy/qcom-qusb2-phy.txt > @@ -6,7 +6,9 @@ QUSB2 controller supports LS/FS/HS usb connectivity on Qualcomm chipsets. > Required properties: > - compatible: compatible list, contains > "qcom,msm8996-qusb2-phy" for 14nm PHY on msm8996, > - "qcom,qusb2-v2-phy" for QUSB2 V2 PHY. > + "qcom,qusb2-v2-phy" for QUSB2 V2 PHY, > + "qcom,sdm845-qusb2-phy-1" for primary PHY on sdm845, > + "qcom,sdm845-qusb2-phy-2" for secondary PHY on sdm845. Similar question to the one I posed on for the QMP PHY. What is "qcom,qusb2-v2-phy"? Is it some ideal abstract version of the PHY? Do we expect that anyone would actually use that compatible string? In this case in it looks as if you're using the same settings as "qcom,sdm845-qusb2-phy-2", so presumably "qcom,qusb2-v2-phy" should just be deleted. -Doug