All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Richard Acayan" <mailingradian@gmail.com>
Cc: krzk+dt@kernel.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v4 1/2] arm64: dts: qcom: sdm670-google: add common device tree include
Date: Thu, 14 May 2026 08:08:15 +0000	[thread overview]
Message-ID: <20260514080816.67F5AC2BCB7@smtp.kernel.org> (raw)
In-Reply-To: <20260513172549.1345-2-mailingradian@gmail.com>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] The newly added common device tree file uses the deprecated GPL-2.0 SPDX identifier, contradicting the commit message.
- [Low] The `framebuffer` node retains a unit address in its name without a `reg` property, which triggers a dtc warning.
--

commit 1f4f677fcfc2b6d8ad7bf836706a7501c4b2897b
Author: Richard Acayan <mailingradian@gmail.com>

arm64: dts: qcom: sdm670-google: add common device tree include

This commit extracts the common elements from the Pixel 3a device tree into
a shared include file to support the Pixel 3a XL. It also rewrites the
original device tree to specify only non-XL properties.

> diff --git a/arch/arm64/boot/dts/qcom/sdm670-google-common.dtsi b/arch/arm64/boot/dts/qcom/sdm670-google-common.dtsi
> new file mode 100644
> index 0000000000000..0f57b915186b7
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/sdm670-google-common.dtsi
> @@ -0,0 +1,712 @@
> +// SPDX-License-Identifier: GPL-2.0

The commit message mentions changing the SPDX license identifier from GPL-2.0
to GPL-2.0-only, but this new common include file still uses GPL-2.0. Was
this an oversight when creating the new file?

[ ... ]

> +	chosen {
> +		stdout-path = "serial0:115200n8";
> +
> +		#address-cells = <2>;
> +		#size-cells = <2>;
> +		ranges;
> +
> +		framebuffer: framebuffer@9c000000 {
> +			compatible = "simple-framebuffer";
> +			memory-region = <&fb_mem>;
> +			width = <1080>;

Since the reg property was replaced with a memory-region reference, should
the @9c000000 unit address be removed from the node name to prevent a dtc
warning about a node having a unit name but no reg property?

Additionally, are the #address-cells, #size-cells, and ranges properties in
the parent chosen node still necessary now that the child node no longer
uses a reg property?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260513172549.1345-1-mailingradian@gmail.com?part=1

  parent reply	other threads:[~2026-05-14  8:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-13 17:25 [PATCH v4 0/2] arm64: dts: qcom: pixel 3a xl support with tianma panel Richard Acayan
2026-05-13 17:25 ` [PATCH v4 1/2] arm64: dts: qcom: sdm670-google: add common device tree include Richard Acayan
2026-05-13 17:57   ` Dmitry Baryshkov
2026-05-14  8:08   ` sashiko-bot [this message]
2026-05-13 17:25 ` [PATCH v4 2/2] arm64: dts: qcom: add support for pixel 3a xl with the tianma panel Richard Acayan
2026-05-13 17:58   ` Dmitry Baryshkov

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=20260514080816.67F5AC2BCB7@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=mailingradian@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.