From: Heiko Schocher <hs@nabladev.com>
To: Yao Zi <me@ziyao.cc>, Junhui Liu <junhui.liu@pigmoral.tech>,
u-boot-spacemit@groups.io, u-boot@lists.u-boot-project.org
Cc: Huan Zhou <pericycle.cc@gmail.com>,
Guodong Xu <guodong.xu@oss.qualcomm.com>,
Tom Rini <trini@konsulko.com>,
Raymond Mao <raymond.mao@riscstar.com>,
Lukasz Majewski <lukma@denx.de>, Yixun Lan <dlan@kernel.org>,
Troy Mitchell <troy.mitchell@linux.spacemit.com>
Subject: Re: [PATCH v2 0/4] i2c/clk: spacemit: k1: fix I2C bus configuration and clock handling
Date: Mon, 24 Aug 2026 10:21:58 +0200 [thread overview]
Message-ID: <e4ad1d7a-ad9e-3cb1-e1ed-ad95f22b5b14@nabladev.com> (raw)
In-Reply-To: <aoQBacTKiBXUDddj@pie>
Hello Yao Zi, Junhui Liu,
On 18.08.26 08:53, Yao Zi wrote:
> On Sat, Aug 15, 2026 at 11:40:20AM +0800, Junhui Liu wrote:
>> Fix two issues in the SpacemiT K1 I2C driver and clock provider.
>>
>> The first issue is that the controller bus mode is selected using the
>> functional clock rate instead of the requested I2C bus speed from the
>> device tree.
>>
>> The second issue is that the TWSI functional clocks incorrectly include
>> the bus clock enable bit in their gate masks. As a result the I2C driver
>> can operate with only the functional clock enabled, which diverges from
>> the device tree description and the Linux driver (both expect separate
>> "func" and "bus" clocks).
>>
>> To fix the second issue without breaking intermediate states, the
>> patches are ordered as follows:
>>
>> - First add the missing bus clocks (and their parent chain) to the SPL
>> clock tree.
>> - Then update the I2C driver to acquire and enable both the functional
>> and bus clocks by name.
>> - Finally remove the bus gate bit from the functional clock definitions
>> (except TWSI8, whose write-only register requires the combined gate).
>
> Personally I think it's okay to break booting in this case as long as
> you explicitly point it out. Merging the conceptually related PATCH 2
> and PATCH 4 which together fix description of TWSI controller clocks
> would make the commit description shorter and clearer. But it depends on
> you.
For me the series is okay now, if you (Junhui Liu) have not prepared a
v3 with the merge Yao Zi explained already ... I will pick v2 up for next...
Please give me feedback, what you plan, thanks!
> For the whole series,
>
> Reviewed-by: Yao Zi <me@ziyao.cc>
Thanks!
bye,
Heiko
>
> Regards,
> Yao Zi
>
--
Nabla Software Engineering
HRB 40522 Augsburg
Phone: +49 821 45592596
E-Mail: office@nabladev.com
Geschäftsführer : Stefano Babic
next prev parent reply other threads:[~2026-08-24 8:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-15 3:40 [PATCH v2 0/4] i2c/clk: spacemit: k1: fix I2C bus configuration and clock handling Junhui Liu
2026-08-15 3:40 ` [PATCH v2 1/4] i2c: k1: fix wrong bus speed setting Junhui Liu
2026-08-17 8:29 ` Yixun Lan
2026-08-17 9:12 ` Troy Mitchell
2026-08-17 14:25 ` Junhui Liu
2026-08-18 1:03 ` Troy Mitchell
2026-08-15 3:40 ` [PATCH v2 2/4] clk: spacemit: k1: add TWSI bus clocks to SPL Junhui Liu
2026-08-15 3:40 ` [PATCH v2 3/4] i2c: k1: enable both functional and bus clocks Junhui Liu
2026-08-17 4:50 ` Heiko Schocher via U-Boot
2026-08-17 8:31 ` Yixun Lan
2026-08-17 8:56 ` Troy Mitchell
2026-08-17 9:18 ` Yixun Lan
2026-08-18 1:03 ` Troy Mitchell
2026-08-18 6:21 ` Yao Zi
2026-08-18 6:26 ` Yao Zi
2026-08-15 3:40 ` [PATCH v2 4/4] clk: spacemit: k1: remove bus gate from TWSI functional clocks Junhui Liu
2026-08-17 8:55 ` Troy Mitchell
2026-08-18 6:53 ` [PATCH v2 0/4] i2c/clk: spacemit: k1: fix I2C bus configuration and clock handling Yao Zi
2026-08-24 8:21 ` Heiko Schocher [this message]
2026-08-24 14:21 ` Junhui Liu
2026-08-25 4:40 ` Heiko Schocher
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=e4ad1d7a-ad9e-3cb1-e1ed-ad95f22b5b14@nabladev.com \
--to=hs@nabladev.com \
--cc=dlan@kernel.org \
--cc=guodong.xu@oss.qualcomm.com \
--cc=junhui.liu@pigmoral.tech \
--cc=lukma@denx.de \
--cc=me@ziyao.cc \
--cc=pericycle.cc@gmail.com \
--cc=raymond.mao@riscstar.com \
--cc=trini@konsulko.com \
--cc=troy.mitchell@linux.spacemit.com \
--cc=u-boot-spacemit@groups.io \
--cc=u-boot@lists.u-boot-project.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;
as well as URLs for NNTP newsgroup(s).