Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Aleksander Jan Bajkowski" <olek2@wp.pl>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH] arm: dts: xilinx: parallella: Enable QSPI and NOR flash
Date: Thu, 17 Sep 2026 23:00:58 +0000	[thread overview]
Message-ID: <20260917230058.D47EF1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260917225317.319745-1-olek2@wp.pl>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] dts: uboot-env partition is marked read-only preventing fw_setenv updates
--

commit be87c0d3af6ecbab826ce9e10b9f662f4e9662e5
Author: Aleksander Jan Bajkowski <olek2@wp.pl>

arm: dts: xilinx: parallella: Enable QSPI and NOR flash

This commit enables the QSPI controller on the Parallella board and adds the
corresponding SPI-NOR flash node along with its fixed partitions.

> diff --git a/arch/arm/boot/dts/xilinx/zynq-parallella.dts b/arch/arm/boot/dts/xilinx/zynq-parallella.dts
> --- a/arch/arm/boot/dts/xilinx/zynq-parallella.dts
> +++ b/arch/arm/boot/dts/xilinx/zynq-parallella.dts
[ ... ]
> +		partitions {
> +			compatible = "fixed-partitions";
> +			#address-cells = <1>;
> +			#size-cells = <1>;
> +
> +			partition@0 {
> +				label = "uboot";
> +				reg = <0x0 0x4e0000>;
> +				read-only;
> +			};
> +
> +			partition@4e0000 {
> +				label = "uboot-env";
> +				reg = <0x4e0000 0x10000>;
> +				read-only;

[Severity: Medium]
Will this prevent standard userspace tools like fw_setenv from updating the
U-Boot environment?

The kernel MTD subsystem parses the read-only property and clears the
MTD_WRITEABLE flag for this partition. If a root user attempts to open or
write to the corresponding /dev/mtdX device, the operation will fail with
-EROFS or -EPERM.

While some board configurations intentionally restrict write access to the
bootloader environment as a policy choice, is it intended to structurally
prevent dynamic updates from Linux on the Parallella board?

> +			};
> +		};
> +	};
> +};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260917225317.319745-1-olek2@wp.pl?part=1

      reply	other threads:[~2026-09-17 23:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-17 22:53 [PATCH] arm: dts: xilinx: parallella: Enable QSPI and NOR flash Aleksander Jan Bajkowski
2026-09-17 23:00 ` sashiko-bot [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=20260917230058.D47EF1F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=olek2@wp.pl \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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