From: "Rob Herring (Arm)" <robh@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: briannorris@chromium.org, conor+dt@kernel.org,
linux-wireless@vger.kernel.org, devicetree@vger.kernel.org,
johannes@sipsolutions.net, krzk+dt@kernel.org, kvalo@kernel.org,
linux-kernel@vger.kernel.org, Frank.Li@nxp.com
Subject: Re: [PATCH] dt-bindings: net: wireless: marvell,sd8787: Relax length constraints
Date: Fri, 13 Mar 2026 19:08:18 -0500 [thread overview]
Message-ID: <177344689795.3706356.13043407533958417879.robh@kernel.org> (raw)
In-Reply-To: <20260311194531.70441-1-festevam@gmail.com>
On Wed, 11 Mar 2026 16:45:31 -0300, Fabio Estevam wrote:
> Commit 31ed9d9d71ec ("ARM: dts: rockchip: Limit WiFi TX power on
> rk3288-veyron-jerry") added calibration data for the rk3288-veyron-jerry
> platform. The commit message explicitly notes that "the length can vary
> between hw versions", as documented in the original text binding.
>
> The current YAML schema enforces fixed maximum lengths for calibration
> data arrays, which causes dtbs_check warnings for rk3288-veyron-jerry.dts.
>
> Relax the constraints for the two properties that have
> variable-length data in this platform by adding minItems based on the
> actual data used in the downstream kernel:
>
> - marvell,caldata-txpwrlimit-2g: 508 bytes (from rk3288-veyron-jerry.dts)
> - marvell,caldata-txpwrlimit-5g-sub2: 744 bytes (from
> rk3288-veyron-jerry.dts)
>
> The original maxItems values are preserved as upper bounds to maintain
> validation for other platforms while accommodating this specific
> hardware variant.
>
> Fixes: 25f855413885 ("dt-bindings: net: wireless: convert marvel-8xxx.txt to yaml format")
> Signed-off-by: Fabio Estevam <festevam@gmail.com>
> ---
> .../devicetree/bindings/net/wireless/marvell,sd8787.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
Acked-by: Rob Herring (Arm) <robh@kernel.org>
prev parent reply other threads:[~2026-03-14 0:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 19:45 Fabio Estevam
2026-03-14 0:08 ` Rob Herring (Arm) [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=177344689795.3706356.13043407533958417879.robh@kernel.org \
--to=robh@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=briannorris@chromium.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=krzk+dt@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.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
all inboxes | Powered by JetHome®