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 gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 1F242ECAAD3 for ; Sun, 11 Sep 2022 13:45:53 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 1A97110E470; Sun, 11 Sep 2022 13:45:52 +0000 (UTC) Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) by gabe.freedesktop.org (Postfix) with ESMTPS id 1AE3310E470 for ; Sun, 11 Sep 2022 13:45:47 +0000 (UTC) Received: by mail-yb1-xb2a.google.com with SMTP id c9so9181021ybf.5 for ; Sun, 11 Sep 2022 06:45:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=5HqIOcG8x4likLdUFYhKV2vDY9FYKtBGRhEqTmUcrsY=; b=S0L2CvFshXTcGx2gV46rtMsvefTjoiczN+TXYgfWm41bgtY5+1jOsw23Zi37N3K9xE aA8oemxSJ8X44ndvDESNHxSgYaNeJ7mTyK/aBqONVba0zXB5J2mORlp/g6atZvc8N1Mb pfJPM8bY+vqXL5sIpUA9OZk1TvH7z/LBReR+5OpkdsnvDD5LPw4a0Dz5vWOfcbssPthJ jPy4+g0+7UGuUZ7leUeqENKSWArOTdfzeVt0Ta8cDtnKhGhgDl8O43G8pmbzi1veftNs ihWjWQW2XqbphhnfvFev+xbJsd3vzfxS6HPhACJsORvpF26WEIJie9CdMYt6fEJtk23Y uNbA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=5HqIOcG8x4likLdUFYhKV2vDY9FYKtBGRhEqTmUcrsY=; b=C8/ZsTqVOdCfKXNYKivSPKfRmT6g/3zP8zZ6kPwPiX9+MnsKjxyRzKNQL5ofXIF4oN YFr32QtaaSi6EC1pWB+lD8OU6cioszn6dNwqKfHvOvJGXSulueViKKu7nGcqCBQ3+pO2 +2mcrWd7N+7wLsbuL/kt3CTgHRYkbcNN+PxDMcIIPRRrlNZ9RvVKM201HxEp3YAYqHuH qOSylHJeLuTJ6Ix8BSHjPWX+3DvuN+VPoGUR/eZa3imEhGAzzRSoPCRuMFpNSq5N/aX0 omhKqhkUusjWeGWjJe7AZnnEQfiK/xv94GiZ+zgtU4wQt7/6SiP1B6l+5HYpeTX2kPMs ZcQQ== X-Gm-Message-State: ACgBeo1u7rAmZM/DHa9vQW2CwBY7sdZBf1l5O7YORQ7WCYuG0gjzovWM YB8tw5i4OJOZlAmFhI48Mo7jtuTT7fFxk1ymm0MU6A== X-Google-Smtp-Source: AA6agR5b3srfz+0UXFR6VD9/hRFnzkydunMZcHEgtygrOZCAfrlPx9UUN7wz0ndz1t7d1pWP7P7GK4PEl9YOqEl2K/0= X-Received: by 2002:a05:6902:1029:b0:6af:2c99:4630 with SMTP id x9-20020a056902102900b006af2c994630mr696449ybt.516.1662903946156; Sun, 11 Sep 2022 06:45:46 -0700 (PDT) MIME-Version: 1.0 References: <20220901102312.2005553-1-dmitry.baryshkov@linaro.org> <20220901102312.2005553-2-dmitry.baryshkov@linaro.org> <3e525135-d205-eddc-ff2d-98c8321386e3@linaro.org> <20220908193705.GA3002673-robh@kernel.org> <1ebe64a3-fab9-1dd7-517a-01001a176d9f@linaro.org> <2204eab4-b22d-8ee7-4595-49139cb387a8@linaro.org> In-Reply-To: From: Dmitry Baryshkov Date: Sun, 11 Sep 2022 16:45:35 +0300 Message-ID: Subject: Re: [PATCH v6 01/12] dt-bindings: display/msm: split qcom, mdss bindings To: Krzysztof Kozlowski Content-Type: text/plain; charset="UTF-8" X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Loic Poulain , devicetree@vger.kernel.org, David Airlie , linux-arm-msm , Bjorn Andersson , Konrad Dybcio , Abhinav Kumar , dri-devel , Stephen Boyd , Andy Gross , Krzysztof Kozlowski , freedreno , Sean Paul , AngeloGioacchino Del Regno Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" On Sun, 11 Sept 2022 at 14:27, Krzysztof Kozlowski wrote: > > On 10/09/2022 14:54, Dmitry Baryshkov wrote: > >> > >> However I think there is no such problem, as Dmitry said, that ref > >> changes anything. There will be always failure - either from parent > >> schema (using $ref) or from device child schema (the one which actually > >> misses the property). > > > > Initially I stumbled upon this issue with the dsi and dsi_phy nodes > > for msm8996 devices. If I have $ref here, dsi1/dsi1_phy nodes will > > emit warnings regarding the missing -supply properties despite nodes > > being disabled. If I use `compatible' here, the schema checks pass. > > Thus I'd prefer to leave `compatible' here. Not to mention that it > > also allows specifying a tighter binding than just using the $ref. > > I don't think we understood each other. I claim that error will be there > anyway, just from different schema. So your change fixes nothing in > total schema check... If the node is disabled, there will be no different schema check. -- With best wishes Dmitry