Received: by 2002:a05:6a11:4021:0:0:0:0 with SMTP id ky33csp2185501pxb; Fri, 24 Sep 2021 23:49:17 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx20OD9odAhahP79th5RIhoIcHBbrIsa/URA5CKqHoCoBl8oFi1Af3I81zmsTxhJFBmYnBt X-Received: by 2002:a17:906:eb56:: with SMTP id mc22mr15176922ejb.542.1632552557438; Fri, 24 Sep 2021 23:49:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1632552557; cv=none; d=google.com; s=arc-20160816; b=cnEbh8NmKjo1bkmemIUaTve6CeAuZM1iAzuaAMY+n5fTUPBLvkucZoLJGSB5poAvpe mmKIBOMFR+HeoRv39DFupxlgsblWsupCI8ui21L4pkQez0joCyGUrAV9CNCaHl60rOPi YB0a5hp4TEA3hKm5J5hyiHRKq0/w3OW80C5Kt2/xRUpoPQjpD9XcTUqVYUhinp/Qvs2I rkSTphZuvcC0+tZKilbue39JR5JmLSCyDvqbxrHMWQ1MvNdQdd2qzBFzEzQbRUV0NC0z HVKUorBRjT8icdIMixm3mVvM7gOA5nj9LnLebMF/CTNWcrDUea9UFEJFosY/iSQ9V9ed fIkA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=Nm/9G72nwdsmEUfR7k001HxYCONgqI+2jC46H8F4ZAk=; b=kKp0h89Gq97GCtMfA/Roeu33BXGzM7IOnOcL8djAwRt/pRIFXExdiknCoOalml+KtY XlSXB/CIecWxgEvqN2zErsYvcbt2LiaEZFzyb4oFoinLwF5JD8eAoHYMICBSuoOIh813 3WL7yUUVnOq6Jml7tVrJR4oC7pV7N0Nwh0pEqsOW8VGRZI611nKBsohl0cPmP1ZuVYfC 1k4B/ESlKP5v7yCR65WTZkd2d9jFUnYTdTzr7e4OvZi5kLhgLwKbjoTHBYg24FuaUMAv tbL21/EgVsGFLfUAfJjmYNsf0/gHI/uDQ2MCdgEStI2rNRHtCa+r81Mq+qhvHvZhWy1S dqXg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=kmg+frBh; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id 13si1576082edv.149.2021.09.24.23.48.54; Fri, 24 Sep 2021 23:49:17 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=kmg+frBh; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1347542AbhIYCYZ (ORCPT + 99 others); Fri, 24 Sep 2021 22:24:25 -0400 Received: from mail.kernel.org ([198.145.29.99]:56492 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1343687AbhIYCYZ (ORCPT ); Fri, 24 Sep 2021 22:24:25 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 40D976105A; Sat, 25 Sep 2021 02:22:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1632536571; bh=iC6T0DpgPQkNthlfRd9HIITiQDWjQJziefXuN46+sU4=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=kmg+frBhpG5jEZ6Npg8a8kvwXfwUYmxqBBEgsZFJgH/c8fHmw68iPKapvO0k0V9wu vDxlj2+qwDeONU2yJ4CuhUFrShYzEO8lcIegPwWJl2uKEr5pVMYDchE4n3ovVTpZFM W5HBgSbTp+JDqisd7CPf/apRTY7yokuFB+w92+gxVYo27jPCWnb7+PL6DD5KvGYjXm xKvrSrxmKbMnztSX25lh8UVx+n5tHjU8jkKi3DBNhOQBVQbQ1w05c0jRMIPpwpAEAR 96DgnKfSFmsg+9Brwhs3iMg7pLttZf9OycH6Alb11g2VM5N5JIM3ibT/+cs20VHpAQ x19EbFJGRrifQ== Received: by mail-ed1-f53.google.com with SMTP id y89so32450876ede.2; Fri, 24 Sep 2021 19:22:51 -0700 (PDT) X-Gm-Message-State: AOAM533Jj12cU1dw8r8KsciRbbPsMBCBZwwPoi0rXfGo6CMzX2XhBCCG yHhFVAp6ISxv37iaJbYn17oAPVcp8tIPrYjmYw== X-Received: by 2002:a17:907:995a:: with SMTP id kl26mr15504212ejc.6.1632536569784; Fri, 24 Sep 2021 19:22:49 -0700 (PDT) MIME-Version: 1.0 References: <20210921155218.10387-1-jason-jh.lin@mediatek.com> <20210921155218.10387-8-jason-jh.lin@mediatek.com> In-Reply-To: <20210921155218.10387-8-jason-jh.lin@mediatek.com> From: Chun-Kuang Hu Date: Sat, 25 Sep 2021 10:22:38 +0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v11 07/16] dt-bindings: arm: mediatek: move common module from display folder To: "jason-jh.lin" Cc: Rob Herring , Matthias Brugger , Chun-Kuang Hu , Philipp Zabel , Enric Balletbo i Serra , Maxime Coquelin , David Airlie , Daniel Vetter , Alexandre Torgue , Hsin-Yi Wang , fshao@chromium.org, Moudy Ho , roy-cw.yeh@mediatek.com, Fabien Parent , Yongqiang Niu , Nancy Lin , singo.chang@mediatek.com, DTML , linux-stm32@st-md-mailman.stormreply.com, Linux ARM , "moderated list:ARM/Mediatek SoC support" , linux-kernel , DRI Development Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Jason: jason-jh.lin =E6=96=BC 2021=E5=B9=B49=E6=9C=882= 1=E6=97=A5 =E9=80=B1=E4=BA=8C =E4=B8=8B=E5=8D=8811:52=E5=AF=AB=E9=81=93=EF= =BC=9A > > AAL, COLOR, CCORR, MUTEX, WDMA could be used by other modules, > such as MDP, so move their binding document into the common folder. Reviewed-by: Chun-Kuang Hu > > Signed-off-by: jason-jh.lin > --- > .../{display =3D> arm}/mediatek/mediatek,aal.yaml | 9 ++++----- > .../{display =3D> arm}/mediatek/mediatek,ccorr.yaml | 9 ++++----- > .../{display =3D> arm}/mediatek/mediatek,color.yaml | 11 +++++------ > .../{display =3D> arm}/mediatek/mediatek,mutex.yaml | 12 +++++------- > .../{display =3D> arm}/mediatek/mediatek,wdma.yaml | 9 ++++----- > 5 files changed, 22 insertions(+), 28 deletions(-) > rename Documentation/devicetree/bindings/{display =3D> arm}/mediatek/med= iatek,aal.yaml (88%) > rename Documentation/devicetree/bindings/{display =3D> arm}/mediatek/med= iatek,ccorr.yaml (87%) > rename Documentation/devicetree/bindings/{display =3D> arm}/mediatek/med= iatek,color.yaml (86%) > rename Documentation/devicetree/bindings/{display =3D> arm}/mediatek/med= iatek,mutex.yaml (85%) > rename Documentation/devicetree/bindings/{display =3D> arm}/mediatek/med= iatek,wdma.yaml (90%) > > diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,= aal.yaml b/Documentation/devicetree/bindings/arm/mediatek/mediatek,aal.yaml > similarity index 88% > rename from Documentation/devicetree/bindings/display/mediatek/mediatek,a= al.yaml > rename to Documentation/devicetree/bindings/arm/mediatek/mediatek,aal.yam= l > index 311bbf05a967..ab6eb9b550a4 100644 > --- a/Documentation/devicetree/bindings/display/mediatek/mediatek,aal.yam= l > +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,aal.yaml > @@ -1,17 +1,16 @@ > # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > %YAML 1.2 > --- > -$id: http://devicetree.org/schemas/display/mediatek/mediatek,aal.yaml# > +$id: http://devicetree.org/schemas/arm/mediatek/mediatek,aal.yaml# > $schema: http://devicetree.org/meta-schemas/core.yaml# > > -title: Mediatek display adaptive ambient light processor > +title: MediaTek adaptive ambient light processor > > maintainers: > - - Chun-Kuang Hu > - - Philipp Zabel > + - Matthias Brugger > > description: | > - Mediatek display adaptive ambient light processor, namely AAL, > + MediaTek adaptive ambient light processor, namely AAL, > is responsible for backlight power saving and sunlight visibility impr= oving. > AAL device node must be siblings to the central MMSYS_CONFIG node. > For a description of the MMSYS_CONFIG binding, see > diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,= ccorr.yaml b/Documentation/devicetree/bindings/arm/mediatek/mediatek,ccorr.= yaml > similarity index 87% > rename from Documentation/devicetree/bindings/display/mediatek/mediatek,c= corr.yaml > rename to Documentation/devicetree/bindings/arm/mediatek/mediatek,ccorr.y= aml > index 60752ce45d49..de86e9ae35f3 100644 > --- a/Documentation/devicetree/bindings/display/mediatek/mediatek,ccorr.y= aml > +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,ccorr.yaml > @@ -1,17 +1,16 @@ > # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > %YAML 1.2 > --- > -$id: http://devicetree.org/schemas/display/mediatek/mediatek,ccorr.yaml# > +$id: http://devicetree.org/schemas/arm/mediatek/mediatek,ccorr.yaml# > $schema: http://devicetree.org/meta-schemas/core.yaml# > > -title: Mediatek display color correction > +title: MediaTek color correction > > maintainers: > - - Chun-Kuang Hu > - - Philipp Zabel > + - Matthias Brugger > > description: | > - Mediatek display color correction, namely CCORR, reproduces correct co= lor > + MediaTek color correction, namely CCORR, reproduces correct color > on panels with different color gamut. > CCORR device node must be siblings to the central MMSYS_CONFIG node. > For a description of the MMSYS_CONFIG binding, see > diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,= color.yaml b/Documentation/devicetree/bindings/arm/mediatek/mediatek,color.= yaml > similarity index 86% > rename from Documentation/devicetree/bindings/display/mediatek/mediatek,c= olor.yaml > rename to Documentation/devicetree/bindings/arm/mediatek/mediatek,color.y= aml > index f6636869909c..73be301b50d2 100644 > --- a/Documentation/devicetree/bindings/display/mediatek/mediatek,color.y= aml > +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,color.yaml > @@ -1,18 +1,17 @@ > # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > %YAML 1.2 > --- > -$id: http://devicetree.org/schemas/display/mediatek/mediatek,color.yaml# > +$id: http://devicetree.org/schemas/arm/mediatek/mediatek,color.yaml# > $schema: http://devicetree.org/meta-schemas/core.yaml# > > -title: Mediatek display color processor > +title: MediaTek color processor > > maintainers: > - - Chun-Kuang Hu > - - Philipp Zabel > + - Matthias Brugger > > description: | > - Mediatek display color processor, namely COLOR, provides hue, luma and > - saturation adjustments to get better picture quality and to have one p= anel > + MediaTek color processor, namely COLOR, provides hue, luma and saturat= ion > + adjustments to get better picture quality and to have one panel > resemble the other in their output characteristics. > COLOR device node must be siblings to the central MMSYS_CONFIG node. > For a description of the MMSYS_CONFIG binding, see > diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,= mutex.yaml b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mutex.= yaml > similarity index 85% > rename from Documentation/devicetree/bindings/display/mediatek/mediatek,m= utex.yaml > rename to Documentation/devicetree/bindings/arm/mediatek/mediatek,mutex.y= aml > index 6eca525eced0..713c7485e11a 100644 > --- a/Documentation/devicetree/bindings/display/mediatek/mediatek,mutex.y= aml > +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mutex.yaml > @@ -1,19 +1,17 @@ > # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > %YAML 1.2 > --- > -$id: http://devicetree.org/schemas/display/mediatek/mediatek,mutex.yaml# > +$id: http://devicetree.org/schemas/arm/mediatek/mediatek,mutex.yaml# > $schema: http://devicetree.org/meta-schemas/core.yaml# > > -title: Mediatek mutex > +title: MediaTek mutex > > maintainers: > - - Chun-Kuang Hu > - - Philipp Zabel > + - Matthias Brugger > > description: | > - Mediatek mutex, namely MUTEX, is used to send the triggers signals cal= led > - Start Of Frame (SOF) / End Of Frame (EOF) to each sub-modules on the d= isplay > - data path or MDP data path. > + MediaTek mutex, namely MUTEX, is used to send the triggers signals cal= led > + Start Of Frame(SOF) / End Of Frame(EOF) to each sub-modules on the dat= a path. > In some SoC, such as mt2701, MUTEX could be a hardware mutex which pro= tects > the shadow register. > MUTEX device node must be siblings to the central MMSYS_CONFIG node. > diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,= wdma.yaml b/Documentation/devicetree/bindings/arm/mediatek/mediatek,wdma.ya= ml > similarity index 90% > rename from Documentation/devicetree/bindings/display/mediatek/mediatek,w= dma.yaml > rename to Documentation/devicetree/bindings/arm/mediatek/mediatek,wdma.ya= ml > index 25f9a63fe7af..5222535d98c6 100644 > --- a/Documentation/devicetree/bindings/display/mediatek/mediatek,wdma.ya= ml > +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,wdma.yaml > @@ -1,17 +1,16 @@ > # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > %YAML 1.2 > --- > -$id: http://devicetree.org/schemas/display/mediatek/mediatek,wdma.yaml# > +$id: http://devicetree.org/schemas/arm/mediatek/mediatek,wdma.yaml# > $schema: http://devicetree.org/meta-schemas/core.yaml# > > -title: Mediatek display WDMA > +title: MediaTek WDMA > > maintainers: > - - Chun-Kuang Hu > - - Philipp Zabel > + - Matthias Brugger > > description: | > - Mediatek display WDMA stands for Write Direct Memory Access. > + MediaTek WDMA stands for Write Direct Memory Access. > It can write the data in display pipeline into DRAM. > WDMA device node must be siblings to the central MMSYS_CONFIG node. > For a description of the MMSYS_CONFIG binding, see > -- > 2.18.0 >