public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@nxp.com>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, imx@lists.linux.dev,
	Shawn Guo <shawnguo@kernel.org>,
	linux-kernel@vger.kernel.org, Fabio Estevam <festevam@gmail.com>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	devicetree@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>
Subject: Re: [PATCH 1/6] arm64: dts: imx8qxp-mek: add bluetooth audio codec
Date: Fri, 18 Oct 2024 15:39:02 -0400	[thread overview]
Message-ID: <ZxK5VqKzvZLE8DHM@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <172784021530.525807.17173207157125562594.robh@kernel.org>

On Tue, Oct 01, 2024 at 10:51:01PM -0500, Rob Herring (Arm) wrote:
>
> On Mon, 30 Sep 2024 17:25:58 -0400, Frank Li wrote:
> > Add bluetooth audio codec.
> >
> > Signed-off-by: Frank Li <Frank.Li@nxp.com>
> > ---
> >  arch/arm64/boot/dts/freescale/imx8qxp-mek.dts | 24 +++++++++++++++++++
> >  1 file changed, 24 insertions(+)
> >

shawn:
	Do you have chance to check these patches. The below warning is not
caused by these patches. And this warning's fixed patch already in mail
list.

Frank

>
>
> 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 freescale/imx8qxp-mek.dtb' for 20240930212604.118756-1-Frank.Li@nxp.com:
>
> arch/arm64/boot/dts/freescale/imx8qxp-mek.dtb: usbphy@5b100000: 'nxp,sim' is a required property
> 	from schema $id: http://devicetree.org/schemas/phy/fsl,mxs-usbphy.yaml#
>
>
>
>
>


      reply	other threads:[~2024-10-18 19:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-30 21:25 [PATCH 1/6] arm64: dts: imx8qxp-mek: add bluetooth audio codec Frank Li
2024-09-30 21:25 ` [PATCH 2/6] arm64: dts: imx8qxp-mek: add esai, cs42888 and related node Frank Li
2024-10-21  3:01   ` Shawn Guo
2024-09-30 21:26 ` [PATCH 3/6] arm64: dts: imx8qxp-mek: enable jpeg encode and deconde Frank Li
2024-09-30 21:26 ` [PATCH 4/6] arm64: dts: imx8qxp-mek: add flexcan1 and flexcan2 Frank Li
2024-09-30 21:26 ` [PATCH 5/6] arm64: dts: imx8qxp-mek: add usbotg1 and related node Frank Li
2024-09-30 21:26 ` [PATCH 6/6] arm64: dts: imx8qxp-mek: add cm4 and related nodes Frank Li
2024-10-21  3:06   ` Shawn Guo
2024-10-02  3:51 ` [PATCH 1/6] arm64: dts: imx8qxp-mek: add bluetooth audio codec Rob Herring (Arm)
2024-10-18 19:39   ` Frank Li [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=ZxK5VqKzvZLE8DHM@lizhi-Precision-Tower-5810 \
    --to=frank.li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@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