| Message ID | 20230425102418.185783-6-ychuang570808@gmail.com |
|---|---|
| State | New |
| Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org>
Delivered-To: ouuuleilei@gmail.com
Received: by 2002:a59:b0ea:0:b0:3b6:4342:cba0 with SMTP id b10csp3303801vqo;
Tue, 25 Apr 2023 03:27:50 -0700 (PDT)
X-Google-Smtp-Source:
AKy350Z74SqxZXZzP2hnJtBrFd5nUyIbt5X9wgRKSoGQVPznpq4GncodaIUSgTx/1Zp/+DpwDIuj
X-Received: by 2002:a05:6a20:8427:b0:f5:b7c9:57b5 with SMTP id
c39-20020a056a20842700b000f5b7c957b5mr5130979pzd.24.1682418470276;
Tue, 25 Apr 2023 03:27:50 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1682418470; cv=none;
d=google.com; s=arc-20160816;
b=XU7k0QTNaNYGq4KtExSEroI06HK2WbQEQnLMwUrNdEUAPd7tzundtym8RzHs4bkHhe
i7K67GOrOtMewe88zrzbOP34o9l85ADMWPrnR9oYavmroVz+qhdea7osbXfmd9aC/Jp2
UtQUJrFdsKh5p+prAOaredurP+/87Px77GNE0g38bezjircb8r4a+QLj1ar/FtV/xLLN
HUAxxVQV0L35+hlbFNkwSBr9aZeghsuzjuRXEy23p6F/Nn9dsmS7phYivmNouZ0l8IcH
8z7Hf2ARqrDMXF8orxZBOgQJMNIm2v9TeaObTfQoDMkBOwKXznvxXQ6oAFjf0G6vlQwp
kMdw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com;
s=arc-20160816;
h=list-id:precedence:content-transfer-encoding:mime-version
:references:in-reply-to:message-id:date:subject:cc:to:from
:dkim-signature;
bh=9i1tMTPZLGuvknLFHUGIb9xYQZ6wKX2msp9z8wX7XkA=;
b=d/ysI1b1wL99zQUyGJRpU1hXHWoMJmBL4vmuBpUrWUZP/9kUMmvPFGqNYlH46P/Ucj
sbYQ5B+kbEfCOqxxuW6pTZ538WQyyw4q+XyZSVNirDNGgCLsO19Httj9moQxYC6x9jOP
n4uix0W7Hbm+oW+UWfdMVokjdc74BpiM9fvvUbD0tmcRVbqYZFvUnpbVqvaZeW2zYvxX
pujJgFyS4N7aEnsULGiWLA3BiksS05hzgityUr1ysPY2HLO9TsVa6Qky3/xfllSqomZL
HlLkv8XQCclcCyCiebZBInEb/3f3AJGnNGlOXMT7F4PfJNknbpk5mZFF+x8ZxVA5YSrz
8P8g==
ARC-Authentication-Results: i=1; mx.google.com;
dkim=pass header.i=@gmail.com header.s=20221208 header.b=ToHA0slX;
spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org
designates 2620:137:e000::1:20 as permitted sender)
smtp.mailfrom=linux-kernel-owner@vger.kernel.org;
dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com
Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20])
by mx.google.com with ESMTP id
10-20020a63124a000000b0051f0d0d6359si10285574pgs.118.2023.04.25.03.27.35;
Tue, 25 Apr 2023 03:27:50 -0700 (PDT)
Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org
designates 2620:137:e000::1:20 as permitted sender)
client-ip=2620:137:e000::1:20;
Authentication-Results: mx.google.com;
dkim=pass header.i=@gmail.com header.s=20221208 header.b=ToHA0slX;
spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org
designates 2620:137:e000::1:20 as permitted sender)
smtp.mailfrom=linux-kernel-owner@vger.kernel.org;
dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
id S233776AbjDYKZW (ORCPT <rfc822;zxc52fgh@gmail.com> + 99 others);
Tue, 25 Apr 2023 06:25:22 -0400
Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59754 "EHLO
lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
with ESMTP id S233779AbjDYKYy (ORCPT
<rfc822;linux-kernel@vger.kernel.org>);
Tue, 25 Apr 2023 06:24:54 -0400
Received: from mail-pf1-x433.google.com (mail-pf1-x433.google.com
[IPv6:2607:f8b0:4864:20::433])
by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D8C0413C05;
Tue, 25 Apr 2023 03:24:42 -0700 (PDT)
Received: by mail-pf1-x433.google.com with SMTP id
d2e1a72fcca58-63b73203e0aso34297524b3a.1;
Tue, 25 Apr 2023 03:24:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20221208; t=1682418282; x=1685010282;
h=content-transfer-encoding:mime-version:references:in-reply-to
:message-id:date:subject:cc:to:from:from:to:cc:subject:date
:message-id:reply-to;
bh=9i1tMTPZLGuvknLFHUGIb9xYQZ6wKX2msp9z8wX7XkA=;
b=ToHA0slXcxQ6K1hL2v1OGzCMT2aFiXx1A/CwyN78h2xkq9rN/I8rr/T+Nn7DmYep0c
G0hDTGF/tguD9wbB52uK2gQOb69CsFgbfSL9OSFEFhaGETkjMyqcJGBwQxJCn7D4g3b0
UsZ92oZVemcAwHSevPpFmKrJmGWtvsUGdJmIoi6JhF6nrOuSGtMDAfZJ+FzjtAsuOwh1
qbWffqG2o6BSYrjcBEaZbgA1V8bJI2WBfaXTpwSh2ioG1u2nhEQh3AZP1Q4cCJ2LI9Ur
lr2ZRmj8boxOf6GDB5qZ0osoWlm2C7b8bJvWb/DF4mqKnsrWM/zv9iJuy02bpRpJV8rO
Wt1g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20221208; t=1682418282; x=1685010282;
h=content-transfer-encoding:mime-version:references:in-reply-to
:message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc
:subject:date:message-id:reply-to;
bh=9i1tMTPZLGuvknLFHUGIb9xYQZ6wKX2msp9z8wX7XkA=;
b=i6yZpwpMm36OJGzz6feDXy2AC08Od8W95mVXRB70XQG3NvsurRFtwZo5Q9a/cmzvNH
TtUmdAo0JDAKx5tlyIQDvN8ei6YDuHZ+MHyco6+AxXPDbi61KRtWalH+8eaLecu7+tgd
cOFQ4VVGfVF4hd7mKXGB7uY0l6ZO0/vq3cyn9wQIEfAFJnEA0WrTtlbQxwNmiQ7SRXmM
qHw6yluJuj6A7u5sRphfWgV+KHvDKGW7V6ts54lSXGY0vKvhMYPkk97xvTJNYJUB7T6c
NFGzsiSX9vfOEomDOTf5s2TkpxK+Q9/u/Cqj0Tkbikf+j5DofziJwaGG9ynwNzKwUhzp
hbbQ==
X-Gm-Message-State: AAQBX9cx/I3cgM1JWVly1J99+yTLV17nwdCCojJzF+ewN53DnB1XCKxe
yAOYh6e0Be23TdLmwNql4GM=
X-Received: by 2002:a05:6a21:6da1:b0:f2:c1a9:ba2f with SMTP id
wl33-20020a056a216da100b000f2c1a9ba2fmr4397796pzb.25.1682418282012;
Tue, 25 Apr 2023 03:24:42 -0700 (PDT)
Received: from a28aa0606c51.. (60-250-192-107.hinet-ip.hinet.net.
[60.250.192.107])
by smtp.gmail.com with ESMTPSA id
30-20020a63125e000000b0051b70c8d446sm7644715pgs.73.2023.04.25.03.24.38
(version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
Tue, 25 Apr 2023 03:24:41 -0700 (PDT)
From: Jacky Huang <ychuang570808@gmail.com>
To: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
lee@kernel.org, mturquette@baylibre.com, sboyd@kernel.org,
p.zabel@pengutronix.de, gregkh@linuxfoundation.org,
jirislaby@kernel.org, tmaimon77@gmail.com, catalin.marinas@arm.com,
will@kernel.org
Cc: devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-serial@vger.kernel.org, arnd@arndb.de, schung@nuvoton.com,
mjchen@nuvoton.com, Jacky Huang <ychuang3@nuvoton.com>
Subject: [PATCH v8 05/11] dt-bindings: arm: Add initial bindings for Nuvoton
platform
Date: Tue, 25 Apr 2023 10:24:12 +0000
Message-Id: <20230425102418.185783-6-ychuang570808@gmail.com>
X-Mailer: git-send-email 2.25.1
In-Reply-To: <20230425102418.185783-1-ychuang570808@gmail.com>
References: <20230425102418.185783-1-ychuang570808@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_ENVFROM_END_DIGIT,
FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,
T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=ham autolearn_force=no
version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
lindbergh.monkeyblade.net
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?=
X-GMAIL-THRID: =?utf-8?q?1764143629494372193?=
X-GMAIL-MSGID: =?utf-8?q?1764143629494372193?=
|
| Series |
Introduce Nuvoton ma35d1 SoC
|
|
Commit Message
Jacky Huang
April 25, 2023, 10:24 a.m. UTC
From: Jacky Huang <ychuang3@nuvoton.com> Move 'nuvoton,npcm-gcr.yaml' from 'arm/npcm' to 'soc/nuvoton'. Rename the '/arm/npcm' directory to 'arm/nuvoton'. Additionally, add bindings for ARMv8-based Nuvoton SoCs and platform boards, and include the initial bindings for ma35d1 series development boards. Signed-off-by: Jacky Huang <ychuang3@nuvoton.com> --- .../bindings/arm/nuvoton/nuvoton,ma35d1.yaml | 30 +++++++++++++++++++ .../npcm.yaml => nuvoton/nuvoton,npcm.yaml} | 2 +- .../nuvoton/nuvoton,npcm-gcr.yaml} | 2 +- 3 files changed, 32 insertions(+), 2 deletions(-) create mode 100644 Documentation/devicetree/bindings/arm/nuvoton/nuvoton,ma35d1.yaml rename Documentation/devicetree/bindings/arm/{npcm/npcm.yaml => nuvoton/nuvoton,npcm.yaml} (93%) rename Documentation/devicetree/bindings/{arm/npcm/nuvoton,gcr.yaml => soc/nuvoton/nuvoton,npcm-gcr.yaml} (93%)
Comments
On Tue, 25 Apr 2023 10:24:12 +0000, Jacky Huang wrote: > From: Jacky Huang <ychuang3@nuvoton.com> > > Move 'nuvoton,npcm-gcr.yaml' from 'arm/npcm' to 'soc/nuvoton'. > Rename the '/arm/npcm' directory to 'arm/nuvoton'. Additionally, add > bindings for ARMv8-based Nuvoton SoCs and platform boards, and include > the initial bindings for ma35d1 series development boards. > > Signed-off-by: Jacky Huang <ychuang3@nuvoton.com> > --- > .../bindings/arm/nuvoton/nuvoton,ma35d1.yaml | 30 +++++++++++++++++++ > .../npcm.yaml => nuvoton/nuvoton,npcm.yaml} | 2 +- > .../nuvoton/nuvoton,npcm-gcr.yaml} | 2 +- > 3 files changed, 32 insertions(+), 2 deletions(-) > create mode 100644 Documentation/devicetree/bindings/arm/nuvoton/nuvoton,ma35d1.yaml > rename Documentation/devicetree/bindings/arm/{npcm/npcm.yaml => nuvoton/nuvoton,npcm.yaml} (93%) > rename Documentation/devicetree/bindings/{arm/npcm/nuvoton,gcr.yaml => soc/nuvoton/nuvoton,npcm-gcr.yaml} (93%) > Reviewed-by: Rob Herring <robh@kernel.org>
On 25/04/2023 12:24, Jacky Huang wrote: > From: Jacky Huang <ychuang3@nuvoton.com> > > Move 'nuvoton,npcm-gcr.yaml' from 'arm/npcm' to 'soc/nuvoton'. > Rename the '/arm/npcm' directory to 'arm/nuvoton'. Additionally, add > bindings for ARMv8-based Nuvoton SoCs and platform boards, and include > the initial bindings for ma35d1 series development boards. > > Signed-off-by: Jacky Huang <ychuang3@nuvoton.com> > --- > .../bindings/arm/nuvoton/nuvoton,ma35d1.yaml | 30 +++++++++++++++++++ > .../npcm.yaml => nuvoton/nuvoton,npcm.yaml} | 2 +- > .../nuvoton/nuvoton,npcm-gcr.yaml} | 2 +- > 3 files changed, 32 insertions(+), 2 deletions(-) > create mode 100644 Documentation/devicetree/bindings/arm/nuvoton/nuvoton,ma35d1.yaml I don't see any improvements here. Path in maintainers is still broken. Best regards, Krzysztof
Dear Krzysztof, On 2023/5/1 下午 05:50, Krzysztof Kozlowski wrote: > On 25/04/2023 12:24, Jacky Huang wrote: >> From: Jacky Huang <ychuang3@nuvoton.com> >> >> Move 'nuvoton,npcm-gcr.yaml' from 'arm/npcm' to 'soc/nuvoton'. >> Rename the '/arm/npcm' directory to 'arm/nuvoton'. Additionally, add >> bindings for ARMv8-based Nuvoton SoCs and platform boards, and include >> the initial bindings for ma35d1 series development boards. >> >> Signed-off-by: Jacky Huang <ychuang3@nuvoton.com> >> --- >> .../bindings/arm/nuvoton/nuvoton,ma35d1.yaml | 30 +++++++++++++++++++ >> .../npcm.yaml => nuvoton/nuvoton,npcm.yaml} | 2 +- >> .../nuvoton/nuvoton,npcm-gcr.yaml} | 2 +- >> 3 files changed, 32 insertions(+), 2 deletions(-) >> create mode 100644 Documentation/devicetree/bindings/arm/nuvoton/nuvoton,ma35d1.yaml > I don't see any improvements here. Path in maintainers is still broken. > > Best regards, > Krzysztof > Does this line cover 'Documentation/devicetree/bindings/arm/nuvoton/nuvoton,ma35d1.yaml'? ==> F: Documentation/devicetree/bindings/*/*/*ma35* I ran 'get_maintainer.pl' on this patch, and it was able to find maintainers and looked good. I also ran 'make htmldocs' and did not see any warnings or errors related to the .yaml files in this patch. However, I am still unsure where the problem lies. Can you suggest any tools I can use to check for errors? I would greatly appreciate any guidance you can provide. Best Regards, Jacky Huang
On 02/05/2023 03:31, Jacky Huang wrote: > Dear Krzysztof, > > > On 2023/5/1 下午 05:50, Krzysztof Kozlowski wrote: >> On 25/04/2023 12:24, Jacky Huang wrote: >>> From: Jacky Huang <ychuang3@nuvoton.com> >>> >>> Move 'nuvoton,npcm-gcr.yaml' from 'arm/npcm' to 'soc/nuvoton'. >>> Rename the '/arm/npcm' directory to 'arm/nuvoton'. Additionally, add >>> bindings for ARMv8-based Nuvoton SoCs and platform boards, and include >>> the initial bindings for ma35d1 series development boards. >>> >>> Signed-off-by: Jacky Huang <ychuang3@nuvoton.com> >>> --- >>> .../bindings/arm/nuvoton/nuvoton,ma35d1.yaml | 30 +++++++++++++++++++ >>> .../npcm.yaml => nuvoton/nuvoton,npcm.yaml} | 2 +- >>> .../nuvoton/nuvoton,npcm-gcr.yaml} | 2 +- >>> 3 files changed, 32 insertions(+), 2 deletions(-) >>> create mode 100644 Documentation/devicetree/bindings/arm/nuvoton/nuvoton,ma35d1.yaml >> I don't see any improvements here. Path in maintainers is still broken. >> >> Best regards, >> Krzysztof >> > > Does this line cover > 'Documentation/devicetree/bindings/arm/nuvoton/nuvoton,ma35d1.yaml'? > ==> F: Documentation/devicetree/bindings/*/*/*ma35* > > I ran 'get_maintainer.pl' on this patch, and it was able to find > maintainers and looked good. > I also ran 'make htmldocs' and did not see any warnings or errors > related to the .yaml files > in this patch. However, I am still unsure where the problem lies. Can > you suggest any > tools I can use to check for errors? I would greatly appreciate any > guidance you can provide. Apply the patches 1 to 5 and then check if all paths from maintainers are correct. I believe the path Documentation/devicetree/bindings/arm/npcm/ is not. I think I told the same last time with explanation that this patch must correct path. Best regards, Krzysztof
Dear Krzysztof, On 2023/5/2 下午 02:31, Krzysztof Kozlowski wrote: > On 02/05/2023 03:31, Jacky Huang wrote: >> Dear Krzysztof, >> >> >> On 2023/5/1 下午 05:50, Krzysztof Kozlowski wrote: >>> On 25/04/2023 12:24, Jacky Huang wrote: >>>> From: Jacky Huang <ychuang3@nuvoton.com> >>>> >>>> Move 'nuvoton,npcm-gcr.yaml' from 'arm/npcm' to 'soc/nuvoton'. >>>> Rename the '/arm/npcm' directory to 'arm/nuvoton'. Additionally, add >>>> bindings for ARMv8-based Nuvoton SoCs and platform boards, and include >>>> the initial bindings for ma35d1 series development boards. >>>> >>>> Signed-off-by: Jacky Huang <ychuang3@nuvoton.com> >>>> --- >>>> .../bindings/arm/nuvoton/nuvoton,ma35d1.yaml | 30 +++++++++++++++++++ >>>> .../npcm.yaml => nuvoton/nuvoton,npcm.yaml} | 2 +- >>>> .../nuvoton/nuvoton,npcm-gcr.yaml} | 2 +- >>>> 3 files changed, 32 insertions(+), 2 deletions(-) >>>> create mode 100644 Documentation/devicetree/bindings/arm/nuvoton/nuvoton,ma35d1.yaml >>> I don't see any improvements here. Path in maintainers is still broken. >>> >>> Best regards, >>> Krzysztof >>> >> Does this line cover >> 'Documentation/devicetree/bindings/arm/nuvoton/nuvoton,ma35d1.yaml'? >> ==> F: Documentation/devicetree/bindings/*/*/*ma35* >> >> I ran 'get_maintainer.pl' on this patch, and it was able to find >> maintainers and looked good. >> I also ran 'make htmldocs' and did not see any warnings or errors >> related to the .yaml files >> in this patch. However, I am still unsure where the problem lies. Can >> you suggest any >> tools I can use to check for errors? I would greatly appreciate any >> guidance you can provide. > Apply the patches 1 to 5 and then check if all paths from maintainers > are correct. I believe the path > Documentation/devicetree/bindings/arm/npcm/ is not. > > I think I told the same last time with explanation that this patch must > correct path. > > Best regards, > Krzysztof > Okay, I think I should combine the patch 11 (for MAINTAINER) into patch 5. Best Regards, Jacky Huang
On 02/05/2023 08:40, Jacky Huang wrote: > > Dear Krzysztof, > > > > On 2023/5/2 下午 02:31, Krzysztof Kozlowski wrote: >> On 02/05/2023 03:31, Jacky Huang wrote: >>> Dear Krzysztof, >>> >>> >>> On 2023/5/1 下午 05:50, Krzysztof Kozlowski wrote: >>>> On 25/04/2023 12:24, Jacky Huang wrote: >>>>> From: Jacky Huang <ychuang3@nuvoton.com> >>>>> >>>>> Move 'nuvoton,npcm-gcr.yaml' from 'arm/npcm' to 'soc/nuvoton'. >>>>> Rename the '/arm/npcm' directory to 'arm/nuvoton'. Additionally, add >>>>> bindings for ARMv8-based Nuvoton SoCs and platform boards, and include >>>>> the initial bindings for ma35d1 series development boards. >>>>> >>>>> Signed-off-by: Jacky Huang <ychuang3@nuvoton.com> >>>>> --- >>>>> .../bindings/arm/nuvoton/nuvoton,ma35d1.yaml | 30 +++++++++++++++++++ >>>>> .../npcm.yaml => nuvoton/nuvoton,npcm.yaml} | 2 +- >>>>> .../nuvoton/nuvoton,npcm-gcr.yaml} | 2 +- >>>>> 3 files changed, 32 insertions(+), 2 deletions(-) >>>>> create mode 100644 Documentation/devicetree/bindings/arm/nuvoton/nuvoton,ma35d1.yaml >>>> I don't see any improvements here. Path in maintainers is still broken. >>>> >>>> Best regards, >>>> Krzysztof >>>> >>> Does this line cover >>> 'Documentation/devicetree/bindings/arm/nuvoton/nuvoton,ma35d1.yaml'? >>> ==> F: Documentation/devicetree/bindings/*/*/*ma35* >>> >>> I ran 'get_maintainer.pl' on this patch, and it was able to find >>> maintainers and looked good. >>> I also ran 'make htmldocs' and did not see any warnings or errors >>> related to the .yaml files >>> in this patch. However, I am still unsure where the problem lies. Can >>> you suggest any >>> tools I can use to check for errors? I would greatly appreciate any >>> guidance you can provide. >> Apply the patches 1 to 5 and then check if all paths from maintainers >> are correct. I believe the path >> Documentation/devicetree/bindings/arm/npcm/ is not. >> >> I think I told the same last time with explanation that this patch must >> correct path. >> >> Best regards, >> Krzysztof >> > > Okay, I think I should combine the patch 11 (for MAINTAINER) into patch 5. I don't know what's there. The path which is changed (invalidated) here, should be updated here. Best regards, Krzysztof
Dear Krzysztof, On 2023/5/2 下午 02:46, Krzysztof Kozlowski wrote: > On 02/05/2023 08:40, Jacky Huang wrote: >> Dear Krzysztof, >> >> >> >> On 2023/5/2 下午 02:31, Krzysztof Kozlowski wrote: >>> On 02/05/2023 03:31, Jacky Huang wrote: >>>> Dear Krzysztof, >>>> >>>> >>>> On 2023/5/1 下午 05:50, Krzysztof Kozlowski wrote: >>>>> On 25/04/2023 12:24, Jacky Huang wrote: >>>>>> From: Jacky Huang <ychuang3@nuvoton.com> >>>>>> >>>>>> Move 'nuvoton,npcm-gcr.yaml' from 'arm/npcm' to 'soc/nuvoton'. >>>>>> Rename the '/arm/npcm' directory to 'arm/nuvoton'. Additionally, add >>>>>> bindings for ARMv8-based Nuvoton SoCs and platform boards, and include >>>>>> the initial bindings for ma35d1 series development boards. >>>>>> >>>>>> Signed-off-by: Jacky Huang <ychuang3@nuvoton.com> >>>>>> --- >>>>>> .../bindings/arm/nuvoton/nuvoton,ma35d1.yaml | 30 +++++++++++++++++++ >>>>>> .../npcm.yaml => nuvoton/nuvoton,npcm.yaml} | 2 +- >>>>>> .../nuvoton/nuvoton,npcm-gcr.yaml} | 2 +- >>>>>> 3 files changed, 32 insertions(+), 2 deletions(-) >>>>>> create mode 100644 Documentation/devicetree/bindings/arm/nuvoton/nuvoton,ma35d1.yaml >>>>> I don't see any improvements here. Path in maintainers is still broken. >>>>> >>>>> Best regards, >>>>> Krzysztof >>>>> >>>> Does this line cover >>>> 'Documentation/devicetree/bindings/arm/nuvoton/nuvoton,ma35d1.yaml'? >>>> ==> F: Documentation/devicetree/bindings/*/*/*ma35* >>>> >>>> I ran 'get_maintainer.pl' on this patch, and it was able to find >>>> maintainers and looked good. >>>> I also ran 'make htmldocs' and did not see any warnings or errors >>>> related to the .yaml files >>>> in this patch. However, I am still unsure where the problem lies. Can >>>> you suggest any >>>> tools I can use to check for errors? I would greatly appreciate any >>>> guidance you can provide. >>> Apply the patches 1 to 5 and then check if all paths from maintainers >>> are correct. I believe the path >>> Documentation/devicetree/bindings/arm/npcm/ is not. >>> >>> I think I told the same last time with explanation that this patch must >>> correct path. >>> >>> Best regards, >>> Krzysztof >>> >> Okay, I think I should combine the patch 11 (for MAINTAINER) into patch 5. > I don't know what's there. The path which is changed (invalidated) here, > should be updated here. > > Best regards, > Krzysztof > I got it and learn the rule. Thank you very much. I will fix it. Best Regards, Jacky Huang
diff --git a/Documentation/devicetree/bindings/arm/nuvoton/nuvoton,ma35d1.yaml b/Documentation/devicetree/bindings/arm/nuvoton/nuvoton,ma35d1.yaml new file mode 100644 index 000000000000..fb190db61525 --- /dev/null +++ b/Documentation/devicetree/bindings/arm/nuvoton/nuvoton,ma35d1.yaml @@ -0,0 +1,30 @@ +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/arm/nuvoton/nuvoton,ma35d1.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Nuvoton MA35 series SoC based platforms + +maintainers: + - Jacky Huang <ychuang3@nuvoton.com> + +description: | + Boards with an ARMv8 based Nuvoton MA35 series SoC shall have + the following properties. + +properties: + $nodename: + const: '/' + compatible: + oneOf: + + - description: MA35D1 based boards + items: + - enum: + - nuvoton,ma35d1-iot + - nuvoton,ma35d1-som + - const: nuvoton,ma35d1 + +additionalProperties: true +... diff --git a/Documentation/devicetree/bindings/arm/npcm/npcm.yaml b/Documentation/devicetree/bindings/arm/nuvoton/nuvoton,npcm.yaml similarity index 93% rename from Documentation/devicetree/bindings/arm/npcm/npcm.yaml rename to Documentation/devicetree/bindings/arm/nuvoton/nuvoton,npcm.yaml index 6871483947c5..d386744c8815 100644 --- a/Documentation/devicetree/bindings/arm/npcm/npcm.yaml +++ b/Documentation/devicetree/bindings/arm/nuvoton/nuvoton,npcm.yaml @@ -1,7 +1,7 @@ # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause %YAML 1.2 --- -$id: http://devicetree.org/schemas/arm/npcm/npcm.yaml# +$id: http://devicetree.org/schemas/arm/nuvoton/nuvoton,npcm.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# title: NPCM Platforms diff --git a/Documentation/devicetree/bindings/arm/npcm/nuvoton,gcr.yaml b/Documentation/devicetree/bindings/soc/nuvoton/nuvoton,npcm-gcr.yaml similarity index 93% rename from Documentation/devicetree/bindings/arm/npcm/nuvoton,gcr.yaml rename to Documentation/devicetree/bindings/soc/nuvoton/nuvoton,npcm-gcr.yaml index 94e72f25b331..23e7e4ea01ff 100644 --- a/Documentation/devicetree/bindings/arm/npcm/nuvoton,gcr.yaml +++ b/Documentation/devicetree/bindings/soc/nuvoton/nuvoton,npcm-gcr.yaml @@ -1,7 +1,7 @@ # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause %YAML 1.2 --- -$id: http://devicetree.org/schemas/arm/npcm/nuvoton,gcr.yaml# +$id: http://devicetree.org/schemas/soc/nuvoton/nuvoton,npcm-gcr.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# title: Global Control Registers block in Nuvoton SoCs