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 94044C43219 for ; Wed, 19 Oct 2022 12:57:26 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231134AbiJSM5X (ORCPT ); Wed, 19 Oct 2022 08:57:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44400 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231991AbiJSM4x (ORCPT ); Wed, 19 Oct 2022 08:56:53 -0400 Received: from mail-qv1-xf34.google.com (mail-qv1-xf34.google.com [IPv6:2607:f8b0:4864:20::f34]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AAF11100BEC for ; Wed, 19 Oct 2022 05:40:07 -0700 (PDT) Received: by mail-qv1-xf34.google.com with SMTP id de14so11248180qvb.5 for ; Wed, 19 Oct 2022 05:40:07 -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=l6HYyoIjnUvMwU0yHagIn4/18iAr7NA//UMNayfCA+Y=; b=dOvlTzjU6BuP1xy7GcxjujxEOKHwCReRbfOLizRueBfSY4FEnUFZnc3MJQBdxAonYR cFVPgQVYkTHgCCNXwvCeexr31HkXl9SQl7x9T+RPUCiaxG4tSM/1uequdCROWB2egGVa LQmlcU/YaL1ZgPxRckvGKI33MT6lTRwcQyJuVL3tAwN7qdwIaNZUH5Jnd0ytgV6ZEbIi uEuncEuR5nDSN6XWNGqB5FbAzAfD+aapeTrfyZxkCFoqakaA5beR1rNpNBLKCa50gZnU aJcxDzxDJJpSQ6eLxBLX8JAU4NGfAMKodKevmuEHWebdpwQzz7riEHaZnRPp1/ibRyUo 4tYw== 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=l6HYyoIjnUvMwU0yHagIn4/18iAr7NA//UMNayfCA+Y=; b=CUP3dxhx3SSq64bOa25RqYPwDX9hjxN+/AGkTfgefcKmrtqPzgl8+L65dvkbxLBQIp V2xrDEqBE7UPQUPfPQND18VcPXSJk0ZpN/8I8mj5nOti1d738R5VWY4rDseE354O9sia J9bqYk0djpppFnKvPVVgPGeb4McWf/vjd0aIaKHOZJzakhj15mX8NMQbLQsnp8TwptmB ZnpygePiQrd1ojdGj3DSED93WqDXQ5VoDnayvTt4zzijUjjs1R+F2CCMyMdoc1BHRvLx BN7usSaAfC2YEQ5o02q6js6/rDDy6FzOyX/v17E2h4qc+atqJb2qs6MloFOApsQcbeQP 6Ecw== X-Gm-Message-State: ACrzQf3Q5HvRBmxdu+tTSZlzVxRTalS9qsHaPH80Q7K4fsxRtRGPXafG Ww6EPA1QcUnQsytVQFDF377jXQ== X-Google-Smtp-Source: AMsMyM6sbGZb7PJUgIQ1RnhFxi87WWEJX86EP7sxBpspPM4u/LORyoNprWbrcZrCBb0JQauxsamnLg== X-Received: by 2002:a05:6214:d4b:b0:4b1:80eb:64e2 with SMTP id 11-20020a0562140d4b00b004b180eb64e2mr6312320qvr.123.1666183154441; Wed, 19 Oct 2022 05:39:14 -0700 (PDT) Received: from [192.168.10.124] (pool-72-83-177-149.washdc.east.verizon.net. [72.83.177.149]) by smtp.gmail.com with ESMTPSA id s15-20020a05622a178f00b0035d432f5ba3sm4043604qtk.17.2022.10.19.05.39.13 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 19 Oct 2022 05:39:13 -0700 (PDT) Message-ID: Date: Wed, 19 Oct 2022 08:39:12 -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 v2 09/15] dt-bindings: phy: qcom,qmp-pcie: rename current bindings 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: <20221019113552.22353-1-johan+linaro@kernel.org> <20221019113552.22353-10-johan+linaro@kernel.org> From: Krzysztof Kozlowski In-Reply-To: <20221019113552.22353-10-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 19/10/2022 07:35, Johan Hovold wrote: > The current QMP PCIe PHY bindings are based on the original MSM8996 > binding which provided multiple PHYs per IP block and these in turn were > described by child nodes. > > Later QMP PCIe PHY blocks 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. > > This is an unnecessary level of detail which has lead to problems when > later IP blocks using different register layouts have been forced to fit > the original mould rather than updating the binding. The bindings are > arguable also incomplete as they only the describe register blocks used > by the current Linux drivers (e.g. does not include the per lane PCS > registers). > > In preparation for adding new bindings for SC8280XP which further > bindings can be based on, rename the current schema file after IPQ8074, > which was the first SoC added to the bindings after MSM8996 (which has > already been split out), and add a reference to the SC8280XP bindings. > > Signed-off-by: Johan Hovold > --- > ...om,qmp-pcie-phy.yaml => qcom,ipq8074-qmp-pcie-phy.yaml} | 7 +++++-- Reviewed-by: Krzysztof Kozlowski Best regards, Krzysztof