From: Ninad Palsule <ninad@linux.ibm.com>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: linux-aspeed@lists.ozlabs.org, davem@davemloft.net,
edumazet@google.com, andrew@codeconstruct.com.au,
netdev@vger.kernel.org, kuba@kernel.org, joel@jms.id.au,
linux-arm-kernel@lists.infradead.org,
openipmi-developer@lists.sourceforge.net, conor+dt@kernel.org,
linux-kernel@vger.kernel.org, pabeni@redhat.com,
ratbert@faraday-tech.com, eajames@linux.ibm.com,
devicetree@vger.kernel.org, andrew+netdev@lunn.ch,
minyard@acm.org, krzk+dt@kernel.org
Subject: Re: [PATCH v3 00/10] DTS updates for system1 BMC
Date: Mon, 13 Jan 2025 13:52:01 -0600 [thread overview]
Message-ID: <a8893ef1-251d-447c-b42f-8f1ebc9623bb@linux.ibm.com> (raw)
In-Reply-To: <173637565834.1164228.2385240280664730132.robh@kernel.org>
Hello,
On 1/8/25 16:34, Rob Herring (Arm) wrote:
> On Wed, 08 Jan 2025 10:36:28 -0600, Ninad Palsule wrote:
>> Hello,
>>
>> Please review the patch set.
>>
>> V3:
>> ---
>> - Fixed dt_binding_check warnings in ipmb-dev.yaml
>> - Updated title and description in ipmb-dev.yaml file.
>> - Updated i2c-protocol description in ipmb-dev.yaml file.
>>
>> V2:
>> ---
>> Fixed CHECK_DTBS errors by
>> - Using generic node names
>> - Documenting phy-mode rgmii-rxid in ftgmac100.yaml
>> - Adding binding documentation for IPMB device interface
>>
>> NINAD PALSULE (7):
>> ARM: dts: aspeed: system1: Add IPMB device
>> ARM: dts: aspeed: system1: Add GPIO line name
>> ARM: dts: aspeed: system1: Add RGMII support
>> ARM: dts: aspeed: system1: Reduce sgpio speed
>> ARM: dts: aspeed: system1: Update LED gpio name
>> ARM: dts: aspeed: system1: Remove VRs max8952
>> ARM: dts: aspeed: system1: Mark GPIO line high/low
>>
>> Ninad Palsule (3):
>> dt-bindings: net: faraday,ftgmac100: Add phys mode
>> bindings: ipmi: Add binding for IPMB device intf
>> ARM: dts: aspeed: system1: Disable gpio pull down
>>
>> .../devicetree/bindings/ipmi/ipmb-dev.yaml | 44 +++++
>> .../bindings/net/faraday,ftgmac100.yaml | 3 +
>> .../dts/aspeed/aspeed-bmc-ibm-system1.dts | 177 ++++++++++++------
>> 3 files changed, 165 insertions(+), 59 deletions(-)
>> create mode 100644 Documentation/devicetree/bindings/ipmi/ipmb-dev.yaml
>>
>> --
>> 2.43.0
>>
>>
>>
>
> My bot found new DTB warnings on the .dts files added or changed in this
> series.
>
> Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
> are fixed by another series. Ultimately, it is up to the platform
> maintainer whether these warnings are acceptable or not. No need to reply
> unless the platform maintainer has comments.
>
> If you already ran DT checks and didn't see these error(s), then
> make sure dt-schema is up to date:
>
> pip3 install dtschema --upgrade
>
>
> New warnings running 'make CHECK_DTBS=y aspeed/aspeed-bmc-ibm-system1.dtb' for 20250108163640.1374680-1-ninad@linux.ibm.com:
>
> arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-system1.dtb: gpio@1e780000: 'hog-0', 'hog-1', 'hog-2', 'hog-3' do not match any of the regexes: 'pinctrl-[0-9]+'
> from schema $id: http://devicetree.org/schemas/gpio/aspeed,ast2400-gpio.yaml#
This is a false positive. So ignoring it.
Regards,
Ninad
>
>
>
>
>
>
next prev parent reply other threads:[~2025-01-13 20:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 16:36 [PATCH v3 00/10] DTS updates for system1 BMC Ninad Palsule
2025-01-08 16:36 ` [PATCH v3 01/10] dt-bindings: net: faraday,ftgmac100: Add phys mode Ninad Palsule
2025-01-10 16:02 ` Rob Herring (Arm)
2025-01-13 19:49 ` Ninad Palsule
2025-01-08 16:36 ` [PATCH v3 02/10] bindings: ipmi: Add binding for IPMB device intf Ninad Palsule
2025-01-10 16:07 ` Rob Herring
2025-01-10 17:53 ` Corey Minyard
2025-01-13 19:50 ` Ninad Palsule
2025-01-14 14:21 ` Ninad Palsule
2025-01-13 19:49 ` Ninad Palsule
2025-01-08 16:36 ` [PATCH v3 03/10] ARM: dts: aspeed: system1: Add IPMB device Ninad Palsule
2025-01-08 16:36 ` [PATCH v3 04/10] ARM: dts: aspeed: system1: Add GPIO line name Ninad Palsule
2025-01-08 16:36 ` [PATCH v3 05/10] ARM: dts: aspeed: system1: Add RGMII support Ninad Palsule
2025-01-08 17:03 ` Andrew Lunn
2025-01-08 18:43 ` Ninad Palsule
2025-01-08 20:13 ` Andrew Lunn
2025-01-08 20:42 ` Ninad Palsule
2025-01-13 19:51 ` Ninad Palsule
2025-01-08 16:36 ` [PATCH v3 06/10] ARM: dts: aspeed: system1: Reduce sgpio speed Ninad Palsule
2025-01-08 16:36 ` [PATCH v3 07/10] ARM: dts: aspeed: system1: Update LED gpio name Ninad Palsule
2025-01-08 16:36 ` [PATCH v3 08/10] ARM: dts: aspeed: system1: Remove VRs max8952 Ninad Palsule
2025-01-08 16:36 ` [PATCH v3 09/10] ARM: dts: aspeed: system1: Mark GPIO line high/low Ninad Palsule
2025-01-08 16:36 ` [PATCH v3 10/10] ARM: dts: aspeed: system1: Disable gpio pull down Ninad Palsule
2025-01-08 22:34 ` [PATCH v3 00/10] DTS updates for system1 BMC Rob Herring (Arm)
2025-01-13 19:52 ` Ninad Palsule [this message]
2025-01-14 0:07 ` Rob Herring
2025-01-14 22:09 ` Ninad Palsule
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a8893ef1-251d-447c-b42f-8f1ebc9623bb@linux.ibm.com \
--to=ninad@linux.ibm.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.com \
--cc=edumazet@google.com \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=netdev@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=pabeni@redhat.com \
--cc=ratbert@faraday-tech.com \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).