public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Lukasz Majewski <lukma@denx.de>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	devicetree@vger.kernel.org, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dts: nxp: mxs: Update device tree description for LWE imx28 based devices
Date: Tue, 27 Aug 2024 14:38:44 +0200	[thread overview]
Message-ID: <9c032005-556d-4466-beff-9e9c3ca60aa1@kernel.org> (raw)
In-Reply-To: <20240827142608.36961a3d@wsk>

On 27/08/2024 14:26, Lukasz Majewski wrote:
>>>  
>>> -			partition@100000 {
>>> -				label = "kernel";
>>> -				reg = <0x100000 0x400000>;
>>> +			partition@3 {  
>>
>> This does not look right. It is neither explained in commit msg, nor
>> matching reg.
> 
> The SPI-NOR memory layout has evolved during time lifetime of the
> device - for example special partitions to keep track of booted devices
> for A/B booting scheme was added.
> 
>>
>> It does not look like you tested the DTS against bindings. Please run
>> `make dtbs_check W=1` (see
>> Documentation/devicetree/bindings/writing-schema.rst or
>> https://www.linaro.org/blog/tips-and-tricks-for-validating-devicetree-sources-with-the-devicetree-schema/
>> for instructions).
> 
> Could you be more specific here?

The @3 does not match "reg" as I wrote above. reg property and unit
address should match.

> 
> For example:
> CROSS_COMPILE="*-gcc" ARCH=arm make -j4 dtbs_check W=1
> 
> Show:
> arch/arm/boot/dts/nxp/mxs/imx28-xea.dtb:
> /apb@80000000/apbx@80040000/saif@80042000: failed to match any schema
> with compatible: ['fsl,imx28-saif']
> 
> Where the 'saif' sound driver is already supported:
> git grep -n "fsl,imx28-saif"
> Documentation/devicetree/bindings/sound/mxs-saif.txt:27: compatible = "fsl,imx28-saif";
> Documentation/devicetree/bindings/sound/mxs-saif.txt:35: compatible = "fsl,imx28-saif";
> arch/arm/boot/dts/nxp/mxs/imx28.dtsi:1110: compatible = "fsl,imx28-saif";
> arch/arm/boot/dts/nxp/mxs/imx28.dtsi:1127: compatible = "fsl,imx28-saif";
> 
> Changes from this patch do not touch the generic imx28.{dtsi} code at
> all.
> 
> I would assume, that the portion of my patch shall not bring any new,
> extra warnings/errors?

Heh, I would swear we have a warning for this... well, still this should
be fixed.


Best regards,
Krzysztof


      reply	other threads:[~2024-08-27 12:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-27  8:42 [PATCH] dts: nxp: mxs: Update device tree description for LWE imx28 based devices Lukasz Majewski
2024-08-27  9:00 ` Krzysztof Kozlowski
2024-08-27 12:26   ` Lukasz Majewski
2024-08-27 12:38     ` Krzysztof Kozlowski [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=9c032005-556d-4466-beff-9e9c3ca60aa1@kernel.org \
    --to=krzk@kernel.org \
    --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=lukma@denx.de \
    --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