Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: "Rob Herring (Arm)" <robh@kernel.org>
To: Andreas Kemnade <andreas@kemnade.info>
Cc: linux-kernel@vger.kernel.org,
	Aaro Koskinen <aaro.koskinen@iki.fi>,
	 devicetree@vger.kernel.org, Kevin Hilman <khilman@baylibre.com>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Tony Lindgren <tony@atomide.com>,
	 Roger Quadros <rogerq@kernel.org>,
	linux-omap@vger.kernel.org,  Conor Dooley <conor+dt@kernel.org>
Subject: Re: [PATCH 0/2] ARM: dts: omap4: panda: TiWilink improvements
Date: Mon, 30 Dec 2024 12:17:11 -0600	[thread overview]
Message-ID: <173558214240.2262575.18233884215338168789.robh@kernel.org> (raw)
In-Reply-To: <20241229230125.85787-1-andreas@kemnade.info>


On Mon, 30 Dec 2024 00:01:23 +0100, Andreas Kemnade wrote:
> Add proper definitions for 32k clock and enable bluetooth
> everywhere.
> 
> Andreas Kemnade (2):
>   ARM: dts: omap4: panda: fix resources needed for Panda
>   ARM: dts: omap4: panda: cleanup bluetooth
> 
>  .../boot/dts/ti/omap/omap4-panda-common.dtsi  | 38 ++++++++++++++++++-
>  arch/arm/boot/dts/ti/omap/omap4-panda-es.dts  | 32 ----------------
>  2 files changed, 36 insertions(+), 34 deletions(-)
> 
> --
> 2.39.5
> 
> 
> 


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 ti/omap/omap4-panda-es.dtb' for 20241229230125.85787-1-andreas@kemnade.info:

arch/arm/boot/dts/ti/omap/omap4-panda-es.dtb: serial@0: {'compatible': ['ti,omap4-uart'], 'reg': [[0, 256]], 'interrupts': [[0, 73, 4]], 'clock-frequency': 48000000, 'pinctrl-names': ['default'], 'pinctrl-0': [[119]], 'interrupts-extended': [[1, 0, 73, 4], [117, 220]], 'bluetooth': {'compatible': ['ti,wl1271-st'], 'pinctrl-names': ['default'], 'pinctrl-0': [[120]], 'enable-gpios': [[121, 14, 0]], 'clocks': [[122, 0]], 'clock-names': ['ext_clock']}, '$nodename': ['serial@0']} is valid under each of {'required': ['interrupts-extended']}, {'required': ['interrupts']}
	from schema $id: http://devicetree.org/schemas/serial/8250_omap.yaml#






      parent reply	other threads:[~2024-12-30 18:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-29 23:01 [PATCH 0/2] ARM: dts: omap4: panda: TiWilink improvements Andreas Kemnade
2024-12-29 23:01 ` [PATCH 1/2] ARM: dts: omap4: panda: fix resources needed for Panda Andreas Kemnade
2024-12-29 23:01 ` [PATCH 2/2] ARM: dts: omap4: panda: cleanup bluetooth Andreas Kemnade
2025-01-04 17:29   ` Roger Quadros
2025-01-04 18:41     ` Andreas Kemnade
2025-01-07 12:33       ` Roger Quadros
2024-12-30 18:17 ` Rob Herring (Arm) [this message]

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=173558214240.2262575.18233884215338168789.robh@kernel.org \
    --to=robh@kernel.org \
    --cc=aaro.koskinen@iki.fi \
    --cc=andreas@kemnade.info \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=khilman@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=rogerq@kernel.org \
    --cc=tony@atomide.com \
    /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