From: Krzysztof Kozlowski <krzk@kernel.org>
To: Lukasz Majewski <lukma@denx.de>, 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>
Cc: 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 11:00:35 +0200 [thread overview]
Message-ID: <737edb34-688d-4800-bb50-2374ac94ac75@kernel.org> (raw)
In-Reply-To: <20240827084255.2120864-1-lukma@denx.de>
On 27/08/2024 10:42, Lukasz Majewski wrote:
> The description for imx28 based devices needs to be updated after some
> further development.
Everything is an update, please be specific in commit subject and message.
>
> Signed-off-by: Lukasz Majewski <lukma@denx.de>
> ---
> arch/arm/boot/dts/nxp/mxs/imx28-lwe.dtsi | 38 +++++++++---------------
> 1 file changed, 14 insertions(+), 24 deletions(-)
>
> diff --git a/arch/arm/boot/dts/nxp/mxs/imx28-lwe.dtsi b/arch/arm/boot/dts/nxp/mxs/imx28-lwe.dtsi
> index 69fcb0dde940..6fa1f3e25b08 100644
> --- a/arch/arm/boot/dts/nxp/mxs/imx28-lwe.dtsi
> +++ b/arch/arm/boot/dts/nxp/mxs/imx28-lwe.dtsi
> @@ -55,23 +55,6 @@ &i2c0 {
> status = "okay";
> };
>
> -&saif0 {
> - pinctrl-names = "default";
> - pinctrl-0 = <&saif0_pins_a>;
> - #sound-dai-cells = <0>;
> - assigned-clocks = <&clks 53>;
> - assigned-clock-rates = <12000000>;
> - status = "okay";
> -};
> -
> -&saif1 {
> - pinctrl-names = "default";
> - pinctrl-0 = <&saif1_pins_a>;
> - fsl,saif-master = <&saif0>;
> - #sound-dai-cells = <0>;
> - status = "okay";
> -};
> -
> &spi3_pins_a {
> fsl,pinmux-ids = <
> MX28_PAD_AUART2_RX__SSP3_D4
> @@ -109,7 +92,7 @@ &ssp3 {
>
> flash@0 {
> compatible = "jedec,spi-nor";
> - spi-max-frequency = <40000000>;
> + spi-max-frequency = <20000000>;
> reg = <0>;
>
> partitions {
> @@ -133,14 +116,21 @@ partition@90000 {
> reg = <0x90000 0x10000>;
> };
>
> - partition@100000 {
> - label = "kernel";
> - reg = <0x100000 0x400000>;
> + partition@3 {
This does not look right. It is neither explained in commit msg, nor
matching reg.
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).
> + label = "rescue";
> + reg = <0xA0000 0xF40000>;
Lowercase hex
> + };
> +
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-08-27 9:00 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 [this message]
2024-08-27 12:26 ` Lukasz Majewski
2024-08-27 12:38 ` Krzysztof Kozlowski
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=737edb34-688d-4800-bb50-2374ac94ac75@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