Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Bhargav Joshi" <j.bhargav.u@gmail.com>
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] ARM: dts: ti: keystone-k2l: Remove obsolete ti,davinci-spi-num-cs property
Date: Sat, 15 Aug 2026 21:57:39 +0000	[thread overview]
Message-ID: <20260815215740.5D0411F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260816-ti-davinci-spi-v1-1-a7f57dfd5262@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Removing `ti,davinci-spi-num-cs` without replacing it with the standard `num-cs` property permanently discards the correct hardware capability limits, such as the 5 chip selects for `spi2`.
--

--- Patch [1]: [PATCH 1/2] ARM: dts: ti: keystone-k2l: Remove obsolete ti,davinci-spi-num-cs property ---
commit 09741cd34d52c73b4d50caafab226d5b1bedeba4
Author: Bhargav Joshi <j.bhargav.u@gmail.com>

ARM: dts: ti: keystone-k2l: Remove obsolete ti,davinci-spi-num-cs property

The commit removes the obsolete ti,davinci-spi-num-cs property from the SPI
nodes in keystone-k2l.dtsi, as it is not documented or used by the driver.
The driver relies on the standard num-cs property instead.

> diff --git a/arch/arm/boot/dts/ti/keystone/keystone-k2l.dtsi b/arch/arm/boot/dts/ti/keystone/keystone-k2l.dtsi
> index 330b437b667f6..65fdb45e83681 100644
> --- a/arch/arm/boot/dts/ti/keystone/keystone-k2l.dtsi
> +++ b/arch/arm/boot/dts/ti/keystone/keystone-k2l.dtsi
> @@ -400,16 +400,7 @@ mdio: mdio@26200f00 {
>  		/include/ "keystone-k2l-netcp.dtsi"
>  };
>  
> -&spi0 {
> -       ti,davinci-spi-num-cs = <5>;
> -};
> -
> -&spi1 {
> -       ti,davinci-spi-num-cs = <3>;
> -};
> -
>  &spi2 {
> -       ti,davinci-spi-num-cs = <5>;

[Severity: Medium]
Does removing this property instead of converting it to the standard num-cs
property permanently discard the correct hardware limits?

By removing the property entirely, these nodes will silently inherit the default
num-cs = <4> from keystone.dtsi. This discards the intended capabilities
(5 chip selects for spi0/spi2, 3 for spi1) rather than fixing them. The file
itself documents SPI2CS4 (the 5th chip select) for spi2 pinmux.

Should these be replaced with num-cs = <5> and num-cs = <3> respectively?

>         /* Pin muxed. Enabled and configured by Bootloader */
>         status = "disabled";
>  };

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260816-ti-davinci-spi-v1-0-a7f57dfd5262@gmail.com?part=1

  reply	other threads:[~2026-08-15 21:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-15 21:49 [PATCH 0/2] spi: davinci: Convert bindings to dt-schema and clean up DTS Bhargav Joshi
2026-08-15 21:49 ` [PATCH 1/2] ARM: dts: ti: keystone-k2l: Remove obsolete ti,davinci-spi-num-cs property Bhargav Joshi
2026-08-15 21:57   ` sashiko-bot [this message]
2026-08-15 21:49 ` [PATCH 2/2] dt-bindings: spi: ti,davinci-spi: convert to DT schema Bhargav Joshi
2026-08-15 21:58   ` sashiko-bot

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=20260815215740.5D0411F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=j.bhargav.u@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox