[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YbdvIPq1hKPmKXXs@sirena.org.uk>
Date: Mon, 13 Dec 2021 16:04:48 +0000
From: Mark Brown <broonie@...nel.org>
To: Tinghan Shen <tinghan.shen@...iatek.com>
Cc: robh+dt@...nel.org, linus.walleij@...aro.org,
matthias.bgg@...il.com, bgolaszewski@...libre.com,
sean.wang@...iatek.com, bayi.cheng@...iatek.com,
gch981213@...il.com, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-gpio@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, linux-spi@...r.kernel.org,
Project_Global_Chrome_Upstream_Group@...iatek.com
Subject: Re: [PATCH v6 2/4] dt-bindings: spi: add new clock name 'axi' for
spi nor
On Sun, Dec 12, 2021 at 04:40:12AM +0800, Tinghan Shen wrote:
> Some mtk spi nor has dedicated dma(s) inside. Add a new clock name, axi,
> for spi nor dma bus clock.
> clock-names:
> + minItems: 2
> items:
> - const: spi
> - const: sf
> + - const: axi
This will cause any existing DTs that don't have both spi and sf clocks
defined to fail to validate which doesn't seem great. Given that your
commit message says this is only required for some SoCs shouldn't the
minimum clocks requirement depend on which particular SoC/IP version is
being used? Not exactly sure how one specifies that in the YAML format.
Please submit patches using subject lines reflecting the style for the
subsystem, this makes it easier for people to identify relevant patches.
Look at what existing commits in the area you're changing are doing and
make sure your subject lines visually resemble what they're doing.
There's no need to resubmit to fix this alone.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists