Received: by 2002:a05:6602:2086:0:0:0:0 with SMTP id a6csp3331223ioa; Tue, 26 Apr 2022 01:13:12 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxPE6Vuu5Nn7MxPwAwuKY4NO2Lg8PqHMSPlUNjBosLTVjKlreKyX3lSCD8ma0U5dz9f/LlI X-Received: by 2002:a05:6402:2789:b0:423:fe09:c252 with SMTP id b9-20020a056402278900b00423fe09c252mr24037268ede.11.1650960791914; Tue, 26 Apr 2022 01:13:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1650960791; cv=none; d=google.com; s=arc-20160816; b=D4rZwqfZ8IOFjvIHu0VS6YpVShu9lZv6pFI9uQ10Qd6cXiDMnarVfM49vCG3VfrEkz BS03VzGniA32nQ8iuFFt+wiL+3DWN6OFd18o6rEzLLGOr3tvMW+6nO0xVciMhbzkpjQN 1r5IIkIg4CoKdIPXkwJbEen9hT/Q/PofR6IFp2XII0cFBMbeMcvUsqQKTdUWgShagXRL m9+QGbwGlt9RBtMrDP2Ygl8iQTYznCe2EG7cWMsfEB3NH+etYggnehtwpCUAkAKuIjoY nF8ys39iNECsHD8ab4a57EpDafilUPriXYgaqcj6Ss5Sjzuv7Q2RB77RRwSNfeYkU4/3 pYaQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=ho4lFHBriP83EBuh7im6oUALrBEwYKd1HOs+QqrsoEY=; b=F++xlUhsafj0LjoL4HnzVGi7SQXVzjklhT1rYr2QZ60sBwp4kgFMcMBxAa4SCRRFbe PQWinR6S3/xFfMos9VSppqtQQdGlvU7NIjlnd4ZA8gbk1HVpno/bn7e9sw4Cr36GCyhe BE87U22Cgt5mzyPhXagl3HgRuC9W0iAFMOf+UVy+KOzuD8Ox+n0gmmHyheuYYVmjC3Y+ X9ZWWXh2UlSh9tK+E7Qb6TFKvQcAsmDz+j0kdf6KssN8EealKcK/5pr9FBUNh/tjp6mU VOs93x2Z/zsNErS/xufWhzNx/XJ+xkrl9PCtuvN3Wu6RBFtiWUnEhzoQa9u7vvist4ML FO4Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b="akQVBkH/"; 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 b16-20020a170906709000b006e7ee1a3502si15417290ejk.955.2022.04.26.01.12.47; Tue, 26 Apr 2022 01:13:11 -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=@chromium.org header.s=google header.b="akQVBkH/"; 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 S245253AbiDYVKU (ORCPT + 99 others); Mon, 25 Apr 2022 17:10:20 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48124 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229437AbiDYVKS (ORCPT ); Mon, 25 Apr 2022 17:10:18 -0400 Received: from mail-pl1-x630.google.com (mail-pl1-x630.google.com [IPv6:2607:f8b0:4864:20::630]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DEA0764714 for ; Mon, 25 Apr 2022 14:07:11 -0700 (PDT) Received: by mail-pl1-x630.google.com with SMTP id c23so28368814plo.0 for ; Mon, 25 Apr 2022 14:07:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=ho4lFHBriP83EBuh7im6oUALrBEwYKd1HOs+QqrsoEY=; b=akQVBkH/VtMlmKfIuInlT+qJDziMVsZPpZ+hQ5uV3NeVNRFOVaH7CY1xTOQH14tJuw 9+tODS+z8YOYzTHVdwEEGgsej/Zlk7M/54/cctu2l86RumWCo+GvIQ1ryP6QoC8Fzvx0 WV/ceo4PnlqfPWY3LRXcb3JxC7fsxQyjQwzzE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=ho4lFHBriP83EBuh7im6oUALrBEwYKd1HOs+QqrsoEY=; b=rL+Z9z5khffOppwLfHKQbKKktqbpzbSi+p6bz6lAhCKXr0BwjrwBiftkr5XHyXOSGW vWFKrONAjNObJAnNeSOQByOdJwHLPJGwSpmNDAQfNH+tsi/BplpmXWefqICB6cJlEIf7 jqlanGrHEDU7jBWnG0cMvovmlV6DANjGqQlCil1DCu2ZKfuXyAGtzgJk5YaLeE1GhjC0 UQdPVBj1Q+8fkOaQ1bisHQXqQEDYndGNCVvN2Kki4eJdI/OudlauC4JEQ6ywwwATKalt D4uRAxt0+ZiDhaf0X6yv+Np91vfvOZQm3eKOCusEmoB6iBOnQJOceTrUI66V6jcNzSi3 fI+A== X-Gm-Message-State: AOAM531VVu/Lk1recRYPiAk70cWiYEvArIsCdMFLn9ytXd7ZLk0epTPa cqmO5hYaYmX7MyCxqy1NeTJU6w== X-Received: by 2002:a17:903:181:b0:15c:9035:2b18 with SMTP id z1-20020a170903018100b0015c90352b18mr16668520plg.8.1650920831241; Mon, 25 Apr 2022 14:07:11 -0700 (PDT) Received: from tictac2.mtv.corp.google.com ([2620:15c:202:201:b820:7f63:f3dd:3da]) by smtp.gmail.com with ESMTPSA id b20-20020a62a114000000b0050d231e08ffsm8523202pff.37.2022.04.25.14.07.09 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 25 Apr 2022 14:07:10 -0700 (PDT) From: Douglas Anderson To: Bjorn Andersson , Vinod Koul , Rob Herring , Dmitry Baryshkov , Rob Clark Cc: Abhinav Kumar , linux-phy@lists.infradead.org, Stephen Boyd , dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org, Kishon Vijay Abraham I , Sankeerth Billakanti , Krzysztof Kozlowski , linux-arm-msm@vger.kernel.org, quic_kalyant@quicinc.com, Kuogee Hsieh , Douglas Anderson , Andy Gross , Daniel Vetter , David Airlie , Rob Clark , Sean Paul , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH 0/2] dt-bindings: List supplies needed for sc7280 eDP Date: Mon, 25 Apr 2022 14:06:41 -0700 Message-Id: <20220425210643.2420919-1-dianders@chromium.org> X-Mailer: git-send-email 2.36.0.rc2.479.g8af0fa9b8e-goog MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS autolearn=unavailable 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 While looking through dts changes for sc7280 eDP I found that none of the regulators that were being defined were listed in the bindings. That being said, the current Linux drivers _were_ looking for regulators. This series tries to document the reality to the best of my ability. If someone from Qualcomm has better documentation than I do and wants to correct anything here then I'd be more than happy. For the PHY patch especially I don't have a great way to map what I see in datasheets / schematics to figure out which is the supply for the "phy" and the "pll". Assuming these look OK, I'd expect the PHY patch to land through the PHY tree and the display patch to land through msm-next. I can split the series up if need be--the two patches are just in one series because they have a similar topic--there are no actual dependencies here. Douglas Anderson (2): dt-bindings: msm/dp: List supplies in the bindings dt-bindings: phy: List supplies for qcom,edp-phy .../devicetree/bindings/display/msm/dp-controller.yaml | 6 ++++++ Documentation/devicetree/bindings/phy/qcom,edp-phy.yaml | 6 ++++++ 2 files changed, 12 insertions(+) -- 2.36.0.rc2.479.g8af0fa9b8e-goog