Linux wireless drivers development
 help / color / mirror / Atom feed
From: Brian Norris <briannorris@chromium.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: "Rob Herring (Arm)" <robh@kernel.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: Mon, 16 Nov 2026 18:45:09 -0800	[thread overview]
Message-ID: <avu_tZSgwxgnLvla@google.com> (raw)
In-Reply-To: <CAOMZO5BdxG2_raZ--ZrrTn=_i2HKTM=pCB0hWi4+CBRno3DGtw@mail.gmail.com>

On Mon, Nov 16, 2026 at 10:18:48PM -0300, Fabio Estevam wrote:
> Hi Rob,
> 
> On Fri, Mar 13, 2026 at 9:08 PM Rob Herring (Arm) <robh@kernel.org> wrote:
> >
> >
> > 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>
> 
> Can you pick this one, please?

This must have hit my spam filter.

And it looks like Johannes has this set to be filtered out ("not a local
patch"):

https://patchwork.kernel.org/project/linux-wireless/patch/20260311194531.70441-1-festevam@gmail.com/

Anyway:

Acked-by: Brian Norris <briannorris@chromium.org>

      reply	other threads:[~2026-11-17  2:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-11 19:45 [PATCH] dt-bindings: net: wireless: marvell,sd8787: Relax length constraints Fabio Estevam
2026-03-14  0:08 ` Rob Herring (Arm)
2026-11-17  1:18   ` Fabio Estevam
2026-11-17  2:45     ` Brian Norris [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=avu_tZSgwxgnLvla@google.com \
    --to=briannorris@chromium.org \
    --cc=Frank.Li@nxp.com \
    --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 \
    --cc=robh@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