From: Alex Elder <elder@riscstar.com>
To: Troy Mitchell <troy.mitchell@linux.spacemit.com>,
Andi Shyti <andi.shyti@kernel.org>, Yixun Lan <dlan@gentoo.org>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, spacemit@lists.linux.dev
Subject: Re: [PATCH v5 3/3] i2c: spacemit: drop warning when clock-frequency property is absent
Date: Sun, 28 Dec 2025 18:56:38 -0600 [thread overview]
Message-ID: <b09d6add-40d8-4deb-b63e-31adc9f327b1@riscstar.com> (raw)
In-Reply-To: <20251226-k1-i2c-ilcr-v5-3-b5807b7dd0e6@linux.spacemit.com>
On 12/26/25 2:32 AM, Troy Mitchell wrote:
> The clock-frequency property is optional according to the DT binding.
> Do not emit a warning when the property is missing and fall back to the
> default frequency instead.
>
> Fixes: 5ea558473fa31 ("i2c: spacemit: add support for SpacemiT K1 SoC")
> Suggested-by: Alex Elder <elder@riscstar.com>
> Signed-off-by: Troy Mitchell <troy.mitchell@linux.spacemit.com>
Any error reading the "clock-frequency" property will simply leave
i2c->clock_freq alone. This is good.
But the lines that follow this issue a warning if i2c->clock_freq
is 0. If it's optional, you should simply use a default value,
and although you could state that rate with dev_info(), you should
not warn about it.
-Alex
> ---
> drivers/i2c/busses/i2c-k1.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-k1.c b/drivers/i2c/busses/i2c-k1.c
> index f0c35e23f4f2e139da0d09f314f3eb0e0462a382..c829618a66a214a12b46d63bf06ba7947b9dbbb8 100644
> --- a/drivers/i2c/busses/i2c-k1.c
> +++ b/drivers/i2c/busses/i2c-k1.c
> @@ -651,9 +651,7 @@ static int spacemit_i2c_probe(struct platform_device *pdev)
> if (!i2c)
> return -ENOMEM;
>
> - ret = of_property_read_u32(of_node, "clock-frequency", &i2c->clock_freq);
> - if (ret && ret != -EINVAL)
> - dev_warn(dev, "failed to read clock-frequency property: %d\n", ret);
> + of_property_read_u32(of_node, "clock-frequency", &i2c->clock_freq);
>
> /* For now, this driver doesn't support high-speed. */
> if (i2c->clock_freq > SPACEMIT_I2C_MAX_STANDARD_MODE_FREQ &&
>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-12-29 0:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-26 8:31 [PATCH v5 0/3] i2c: spacemit: improve clock handling and cleanups Troy Mitchell
2025-12-26 8:31 ` [PATCH v5 1/3] i2c: spacemit: drop useless spaces Troy Mitchell
2025-12-29 0:56 ` Alex Elder
2026-01-14 23:11 ` Andi Shyti
2025-12-26 8:32 ` [PATCH v5 2/3] i2c: spacemit: configure ILCR for accurate SCL frequency Troy Mitchell
2025-12-29 0:56 ` Alex Elder
2025-12-29 1:47 ` Troy Mitchell
2025-12-26 8:32 ` [PATCH v5 3/3] i2c: spacemit: drop warning when clock-frequency property is absent Troy Mitchell
2025-12-29 0:56 ` Alex Elder [this message]
2025-12-29 1:20 ` Troy Mitchell
2026-01-14 23:04 ` Andi Shyti
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=b09d6add-40d8-4deb-b63e-31adc9f327b1@riscstar.com \
--to=elder@riscstar.com \
--cc=andi.shyti@kernel.org \
--cc=dlan@gentoo.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=spacemit@lists.linux.dev \
--cc=troy.mitchell@linux.spacemit.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