From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id F2D1BFA373D for ; Fri, 28 Oct 2022 02:15:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235822AbiJ1CPx (ORCPT ); Thu, 27 Oct 2022 22:15:53 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48770 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235747AbiJ1CPu (ORCPT ); Thu, 27 Oct 2022 22:15:50 -0400 Received: from mail-qv1-xf30.google.com (mail-qv1-xf30.google.com [IPv6:2607:f8b0:4864:20::f30]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DEADA6B66E for ; Thu, 27 Oct 2022 19:15:48 -0700 (PDT) Received: by mail-qv1-xf30.google.com with SMTP id mi9so3215707qvb.8 for ; Thu, 27 Oct 2022 19:15:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=vDQd0R4rcR0/FXPseJDxEhDTM5AtkC9lRAa3LdKXaSk=; b=LmDCFy1tXYjyvA0wy/YnmeJMFvgVI7Afo9lZzSpluX899cAbmH7muXYq/r1EHnRZg2 YnLntgOHKsbdjbiLq49yXbMyb6NM+2UyCBMivZWexjjxBuKJxtk8TonWab/Gv9Z1vrmm tgVNln2AO0DiW2U/SKMR4o1FX37uNNVnY8dHqhX/7cCJR9/ioBEWrQe+qvkkMKoJAfis uUMxFYlzz2GXSCmDmDF3ABevQ52p4R17GL+yqQ6DEvuDonKirHc3UiN+FahklJdf/eTN n4i64gLzGDJzkZBhLkb0FwThI23NBTf97lODoB/LzmQgGxpK5qayH+q7CeK9zvVtOSGj H9OA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=vDQd0R4rcR0/FXPseJDxEhDTM5AtkC9lRAa3LdKXaSk=; b=vB8UdgL4XeBM2Rwd9fuYYqonGoIq2QvoK5ApL+Y1uiuBIZcMS8RijeiG3W7ylHF3kF woeBx7iOyAXPboi0a23mv6Fe9V1G8QOC9T16F7tHJ7pIU3TjAF6bV8WW2N9D8SaD/9eU 8X3GyYW9XYxaZidM9EMUdlniC4hbIcAyhvPN8XCOCr1o37nX+lWDvXUFrnyPBC+2ac0+ GdZp4TeE6o3lSQO99tuMM350NtYnYTh3YplbTKYCTlLPN4h5+3vQRwqgYpRrHPsXDbe3 ivi4QLiDESkIW7O+oJdKMvZTpmp/kxv0OTRbCCMW5QyNsQnzniv9W2z3QTuuv+SvhMu2 Zs2A== X-Gm-Message-State: ACrzQf1rkDjii+iXJASQz519rFJ+iZGiUXuPBA9GygmMvzfNTC8R5uu7 PZLAQiQZC3qyaBl4jgCfr1qaTg== X-Google-Smtp-Source: AMsMyM6SCC/rxKrC2uDa16vuAPQKi5iVfXCtsMjGk5wwgTYw0H9lNcVYDyzkZ1rDhX+IapJxjaDMcA== X-Received: by 2002:a0c:e803:0:b0:4bb:a881:e7bd with SMTP id y3-20020a0ce803000000b004bba881e7bdmr3651911qvn.91.1666923348098; Thu, 27 Oct 2022 19:15:48 -0700 (PDT) Received: from [192.168.1.11] ([64.57.193.93]) by smtp.gmail.com with ESMTPSA id cj21-20020a05622a259500b003a4ec43f2b5sm1733027qtb.72.2022.10.27.19.15.46 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 27 Oct 2022 19:15:47 -0700 (PDT) Message-ID: Date: Thu, 27 Oct 2022 22:15:45 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.0 Subject: Re: [PATCH 11/13] dt-bindings: phy: qcom,qmp-usb: fix sc8280xp binding Content-Language: en-US To: Johan Hovold , Vinod Koul Cc: Andy Gross , Bjorn Andersson , Konrad Dybcio , Rob Herring , Krzysztof Kozlowski , Dmitry Baryshkov , linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org References: <20221024100632.20549-1-johan+linaro@kernel.org> <20221024100632.20549-12-johan+linaro@kernel.org> From: Krzysztof Kozlowski In-Reply-To: <20221024100632.20549-12-johan+linaro@kernel.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 24/10/2022 06:06, Johan Hovold wrote: > The current QMP USB PHY bindings are based on the original MSM8996 PCIe > PHY binding which provided multiple PHYs per IP block and these in turn > were described by child nodes. > > The QMP USB PHY block only provide a single PHY and the remnant child > node does not really reflect the hardware. > > The original MSM8996 binding also ended up describing the individual > register blocks as belonging to either the wrapper node or the PHY child > nodes. > (...) > then: > diff --git a/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-usb-phy.yaml b/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-usb-phy.yaml > new file mode 100644 > index 000000000000..95ee81d782f9 > --- /dev/null > +++ b/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-usb-phy.yaml Filename based on compatible, so in this case "qcom,sc8280xp-qmp-usb3-uni-phy.yaml", unless it's like the PCI case? Best regards, Krzysztof