From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: Sam Protsenko <semen.protsenko@linaro.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Tomasz Figa <tomasz.figa@gmail.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 3/3] arm64: dts: exynos: Add SPI nodes for Exynos850
Date: Tue, 30 Jan 2024 06:11:05 +0000 [thread overview]
Message-ID: <c9b01ae6-cc3f-4447-9b5a-261d234bc92a@linaro.org> (raw)
In-Reply-To: <CAPLW+4ntySsQVA5u4TNWuc0KCbhQY61XcsBqC=O8GRoXmS_NYA@mail.gmail.com>
On 1/29/24 19:39, Sam Protsenko wrote:
>>> + samsung,spi-src-clk = <0>;
>> this optional property
>>
> The reason this property is provided here despite being optional, is
> to avoid corresponding dev_warn() message from spi-s3c64xx.c driver:
>
> if (of_property_read_u32(dev->of_node, "samsung,spi-src-clk", &temp)) {
> dev_warn(dev, "spi bus clock parent not specified, using
> clock at index 0 as parent\n");
>
> The same usage (samsung,spi-src-clk = <0>) can be encountered in
> multiple other Exynos dts in arch/arm/ and arch/arm64/, and it's also
> used in bindings example. Probably for the same reason explained
> above. Even if dev_warn() is removed in the driver, I guess the older
> kernels will still print it if spi-src-clk is omitted. So I'd like to
> keep it here.
Yeah, I know. I proposed a patch switching to dev_dbg. If it's so
annoying and implies adding superfluous properties to DT, maybe it is
worth to add a fixes tag to the dev_dbg patch and backport it to stable
kernels?
Your patch looks fine. I guess the vendor specific properties shall be
last if you keep them, see:
https://www.kernel.org/doc/html/latest/devicetree/bindings/dts-coding-style.html#order-of-properties-in-device-node
If you remove the vendor properties or reorder them, one can add:
Reviewed-by: Tudor Ambarus <tudor.ambarus@linaro.org>
next prev parent reply other threads:[~2024-01-30 6:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 1:38 [PATCH v2 0/3] arm64: exynos: Enable SPI for Exynos850 Sam Protsenko
2024-01-25 1:38 ` [PATCH v2 1/3] clk: samsung: exynos850: Propagate SPI IPCLK rate change Sam Protsenko
2024-01-29 17:46 ` Tudor Ambarus
2024-02-01 10:36 ` (subset) " Krzysztof Kozlowski
2024-01-25 1:38 ` [PATCH v2 2/3] arm64: dts: exynos: Add PDMA node for Exynos850 Sam Protsenko
2024-02-01 10:36 ` (subset) " Krzysztof Kozlowski
2024-01-25 1:38 ` [PATCH v2 3/3] arm64: dts: exynos: Add SPI nodes " Sam Protsenko
2024-01-29 17:51 ` Tudor Ambarus
2024-01-29 19:39 ` Sam Protsenko
2024-01-30 6:11 ` Tudor Ambarus [this message]
2024-02-01 10:31 ` Krzysztof Kozlowski
2024-02-01 14:22 ` Sam Protsenko
2024-02-01 10:36 ` (subset) " Krzysztof Kozlowski
2024-02-01 11:56 ` Krzysztof Kozlowski
2024-02-01 18:24 ` Sam Protsenko
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=c9b01ae6-cc3f-4447-9b5a-261d234bc92a@linaro.org \
--to=tudor.ambarus@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=semen.protsenko@linaro.org \
--cc=tomasz.figa@gmail.com \
/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