From: sashiko-bot@kernel.org
To: "Gregor Herburger" <gregor.herburger@linutronix.de>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v4 1/4] firmware: raspberrypi: reorder rpi_firmware_property_tag enum
Date: Fri, 04 Sep 2026 07:51:08 +0000 [thread overview]
Message-ID: <20260904075109.17A191F00A3D@smtp.kernel.org> (raw)
In-Reply-To: <20260904-rpi-tryboot-v4-1-fdee8bc53ff7@linutronix.de>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The patch claims to reorder the `rpi_firmware_property_tag` enum by tag values but introduces a new sorting error by moving higher values immediately before lower ones.
--
commit 5b5e3e4d76c8fceb817f997acacf1b16bf561c0e
Author: Gregor Herburger <gregor.herburger@linutronix.de>
firmware: raspberrypi: reorder rpi_firmware_property_tag enum
This patch reorders the tags in the rpi_firmware_property_tag enum to
sort them by their tag values. It claims no functional change is intended.
> diff --git a/include/soc/bcm2835/raspberrypi-firmware.h b/include/soc/bcm2835/raspberrypi-firmware.h
> index 975bef529854a..8ad1cdbf5e9f5 100644
> --- a/include/soc/bcm2835/raspberrypi-firmware.h
> +++ b/include/soc/bcm2835/raspberrypi-firmware.h
[ ... ]
> @@ -125,10 +125,10 @@ enum rpi_firmware_property_tag {
> RPI_FIRMWARE_FRAMEBUFFER_SET_VIRTUAL_OFFSET = 0x00048009,
> RPI_FIRMWARE_FRAMEBUFFER_SET_OVERSCAN = 0x0004800a,
> RPI_FIRMWARE_FRAMEBUFFER_SET_PALETTE = 0x0004800b,
> - RPI_FIRMWARE_FRAMEBUFFER_SET_TOUCHBUF = 0x0004801f,
> - RPI_FIRMWARE_FRAMEBUFFER_SET_GPIOVIRTBUF = 0x00048020,
> RPI_FIRMWARE_FRAMEBUFFER_SET_VSYNC = 0x0004800e,
> RPI_FIRMWARE_FRAMEBUFFER_SET_BACKLIGHT = 0x0004800f,
> + RPI_FIRMWARE_FRAMEBUFFER_SET_TOUCHBUF = 0x0004801f,
> + RPI_FIRMWARE_FRAMEBUFFER_SET_GPIOVIRTBUF = 0x00048020,
>
> RPI_FIRMWARE_VCHIQ_INIT = 0x00048010,
>
[Severity: Medium]
The commit message mentions that the enum is being ordered by tag values,
but does this actually break the ordering for these values?
The new placement moves RPI_FIRMWARE_FRAMEBUFFER_SET_TOUCHBUF (0x0004801f)
and RPI_FIRMWARE_FRAMEBUFFER_SET_GPIOVIRTBUF (0x00048020) immediately before
RPI_FIRMWARE_VCHIQ_INIT (0x00048010) in rpi_firmware_property_tag.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260904-rpi-tryboot-v4-0-fdee8bc53ff7@linutronix.de?part=1
next prev parent reply other threads:[~2026-09-04 7:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 7:46 [PATCH v4 0/4] firmware: raspberrypi: Add support for the tryboot mode Gregor Herburger
2026-09-04 7:46 ` [PATCH v4 1/4] firmware: raspberrypi: reorder rpi_firmware_property_tag enum Gregor Herburger
2026-09-04 7:51 ` sashiko-bot [this message]
2026-09-04 11:11 ` Gregor Herburger
2026-09-04 7:46 ` [PATCH v4 2/4] dt-bindings: raspberrypi,bcm2835-firmware: Include 'reboot-mode.yaml' Gregor Herburger
2026-09-04 7:46 ` [PATCH v4 3/4] firmware: raspberrypi: Add reboot mode support Gregor Herburger
2026-09-04 16:39 ` Stefan Wahren
2026-09-04 7:46 ` [PATCH v4 4/4] arm64: dts: broadcom: bcm2712: Add reboot modes to firmware node Gregor Herburger
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=20260904075109.17A191F00A3D@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregor.herburger@linutronix.de \
--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