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 4CD39C43334 for ; Mon, 13 Jun 2022 13:33:25 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 719AC10E7C3; Mon, 13 Jun 2022 13:33:24 +0000 (UTC) Received: from mail-il1-f182.google.com (mail-il1-f182.google.com [209.85.166.182]) by gabe.freedesktop.org (Postfix) with ESMTPS id 007D410E7C3 for ; Mon, 13 Jun 2022 13:33:22 +0000 (UTC) Received: by mail-il1-f182.google.com with SMTP id y17so4232124ilj.11 for ; Mon, 13 Jun 2022 06:33:22 -0700 (PDT) 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:in-reply-to:references:subject:date :message-id; bh=n5jciRFgHV7TEd2xOcxd5PlRxTUMR+//Y01eSUV2T1g=; b=Hj4xt2oDMmCZuQRzsPyVRgf72H59ZUbAE4UWDtgKdhEomRg3gJcJcletLiI2iaXo67 oYsIuNzA0xox5veXK83WPo22Bv1GMyskz6HyZ3szWQliXUo/kX90XYpAHsKMv11Fq7qn ysr64eQBf33Dhf6aWFTGHSJfpc29VRJFlx4jnJHQlbIAYfjCTMKT0xroWOkCk3E9GXdv tl6RvLtADzqUZGKI6enm4BWkaW6YdPUjKUXTXjVc2Ys5AK3yACsxbVHRjClE8epbDH/j ngpGow6mkrmbOq+LxhVjPEkfS+VVCi8j3AAAvAVTcGL08xpNeAWYcnLscJ/q+gut7ArI 8GyA== X-Gm-Message-State: AOAM531JW/e/AriVyAp9kM6RuQatToz2P0MVx2XHhyBNVPl8p4HkiCeh KpMQ/Ri9vfXs8UvGXsjkPg== X-Google-Smtp-Source: ABdhPJwPF2UYqCLy0MjugVo/d0pZuzKLj39QY8kf66rRczmdaVGt+15ynEKyrpTTZPzJBoKuuGYMHw== X-Received: by 2002:a05:6e02:1b04:b0:2d1:af55:eb92 with SMTP id i4-20020a056e021b0400b002d1af55eb92mr33611511ilv.227.1655127201997; Mon, 13 Jun 2022 06:33:21 -0700 (PDT) Received: from robh.at.kernel.org ([64.188.179.251]) by smtp.gmail.com with ESMTPSA id i2-20020a02ca02000000b0032e79d23f8fsm3510831jak.156.2022.06.13.06.33.20 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 13 Jun 2022 06:33:21 -0700 (PDT) Received: (nullmailer pid 3564135 invoked by uid 1000); Mon, 13 Jun 2022 13:33:17 -0000 From: Rob Herring To: Bo-Chen Chen In-Reply-To: <20220613064841.10481-2-rex-bc.chen@mediatek.com> References: <20220613064841.10481-1-rex-bc.chen@mediatek.com> <20220613064841.10481-2-rex-bc.chen@mediatek.com> Subject: Re: [PATCH v11 01/12] dt-bindings: mediatek, dpi: Add DP_INTF compatible Date: Mon, 13 Jun 2022 07:33:17 -0600 Message-Id: <1655127197.559996.3564134.nullmailer@robh.at.kernel.org> 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: chunkuang.hu@kernel.org, granquet@baylibre.com, jitao.shi@mediatek.com, krzysztof.kozlowski+dt@linaro.org, devicetree@vger.kernel.org, airlied@linux.ie, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, msp@baylibre.com, Project_Global_Chrome_Upstream_Group@mediatek.com, robh+dt@kernel.org, linux-mediatek@lists.infradead.org, wenst@chromium.org, matthias.bgg@gmail.com, linux-arm-kernel@lists.infradead.org, angelogioacchino.delregno@collabora.com Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" On Mon, 13 Jun 2022 14:48:30 +0800, Bo-Chen Chen wrote: > From: Markus Schneider-Pargmann > > DP_INTF is similar to DPI but does not have the exact same feature set > or register layouts. > > DP_INTF is the sink of the display pipeline that is connected to the > DisplayPort controller and encoder unit. It takes the same clocks as > DPI. > > In this patch, we also do these string replacement: > - s/mediatek/MediaTek/ in title. > - s/Mediatek/MediaTek/ in description. > > Signed-off-by: Markus Schneider-Pargmann > Signed-off-by: Guillaume Ranquet > Signed-off-by: Bo-Chen Chen > --- > .../bindings/display/mediatek/mediatek,dpi.yaml | 13 ++++++++----- > 1 file changed, 8 insertions(+), 5 deletions(-) > My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check' on your patch (DT_CHECKER_FLAGS is new in v5.13): yamllint warnings/errors: dtschema/dtc warnings/errors: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.example.dtb: dpi@1401d000: clocks: [[4294967295, 40], [4294967295, 41], [4294967295, 8]] is too short From schema: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.example.dtb: dpi@1401d000: clock-names: ['pixel', 'engine', 'pll'] is too short From schema: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml doc reference errors (make refcheckdocs): See https://patchwork.ozlabs.org/patch/ This check can fail if there are any dependencies. The base for a patch series is generally the most recent rc1. If you already ran 'make dt_binding_check' and didn't see the above error(s), then make sure 'yamllint' is installed and dt-schema is up to date: pip3 install dtschema --upgrade Please check and re-submit.