All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zhuxu Ran" <zhuxu_ran@zohomail.com>
To: "Yao Zi" <me@ziyao.cc>, "Zhuxu Ran" <zhuxu_ran@zohomail.com>,
	<u-boot@lists.u-boot-project.org>,
	"Chao Wei" <chao.wei@sophgo.com>,
	"Chen Wang" <unicorn_wang@outlook.com>
Cc: "Lukasz Majewski" <lukma@denx.de>,
	"Tom Rini" <trini@konsulko.com>, "Peng Fan" <peng.fan@nxp.com>,
	"Jaehoon Chung" <jh80.chung@samsung.com>,
	"Stefan Roese" <stefan.roese@mailbox.org>,
	"Hiago De Franco" <hfranco@baylibre.com>,
	"Sumit Garg" <sumit.garg@kernel.org>,
	"Inochi Amaoto" <inochiama@gmail.com>,
	"Conor Dooley" <conor.dooley@microchip.com>,
	"Chen-Yu Yeh" <chenyou910331@gmail.com>,
	"Chen Wang" <chen.wang@linux.dev>,
	"Kongyang Liu" <seashell11234455@gmail.com>,
	"Leo Liang" <leo.liang@sifive.com>,
	"Thomas Bonnefille" <thomas.bonnefille@bootlin.com>,
	"Quentin Schulz" <quentin.schulz@cherry.de>,
	"Johan Jonker" <jbx6244@gmail.com>,
	"Casey Connolly" <casey.connolly@linaro.org>,
	"Varadarajan Narayanan" <varadarajan.narayanan@oss.qualcomm.com>,
	"Alexander Koch" <akoch@initse.com>,
	"Andreas Schwab" <schwab@suse.de>,
	"Junhui Liu" <junhui.liu@pigmoral.tech>,
	"Marek Vasut" <marex@nabladev.com>,
	"Sumit Garg" <sumit.garg@oss.qualcomm.com>,
	"Peter Robinson" <pbrobinson@gmail.com>,
	"Ilias Apalodimas" <ilias.apalodimas@linaro.org>
Subject: Re: [PATCH v4 09/11] rtc: cv1800: Add RTC and system reset support
Date: Thu, 24 Sep 2026 12:05:52 +0800	[thread overview]
Message-ID: <DLN902USHBOD.1ODD26B7FLRM2@zohomail.com> (raw)
In-Reply-To: <arQRjOUExoQro4ub@pie>

On Thu Sep 24, 2026 at 1:51 AM CST, Yao Zi wrote:
> On Tue, Sep 22, 2026 at 11:46:24PM +0800, Zhuxu Ran wrote:
>> The upstream devicetrees describe the CV1800 RTC subsystem with the
>> "sophgo,cv1800b-rtc" compatible string. The RTC seconds counter and the
>> system-reset controls share the same register range.
>> 
>> Add an RTC driver which directly matches this node, enables its clock,
>> and implements reading and setting the 32-bit seconds counter. Bind the
>> CV1800B sysreset driver as a child from the RTC driver's bind callback so
>> both functions can be instantiated from the same devicetree node.
>> 
>> Initialize the RTC and sysreset register maps from their shared devicetree
>> node instead of using hard-coded MMIO addresses. Remove the board-level
>> sysreset binding from Milk-V Duo. Boards using the upstream RTC node can
>> now instantiate both functions without board-specific binding code.
>> 
>> Signed-off-by: Zhuxu Ran <zhuxu_ran@zohomail.com>
>
> This patch looks quite large, and comparing to other parts of the
> series, it adds new drivers and modifies existing driver massively, so
> I think it makes sense to separate it out of the series, i.e., send a
> separate series converting sysreset-related ABI to match upstream first.
>
>> ---
>>  board/sophgo/milkv_duo/board.c         |   5 --
>>  configs/milkv_duo_256m_defconfig       |   2 +
>>  configs/milkv_duo_defconfig            |   2 +
>>  configs/sipeed_licheerv_nano_defconfig |   2 +
>>  drivers/rtc/Kconfig                    |   9 +++
>>  drivers/rtc/Makefile                   |   1 +
>>  drivers/rtc/rtc-cv1800.c               | 122 +++++++++++++++++++++++++++++++++
>>  drivers/sysreset/Kconfig               |   6 +-
>>  drivers/sysreset/sysreset_cv1800b.c    |  86 ++++++++++++++---------
>
> This involves multiple subsystems, please separate rtc/sysreset/
> board-level changes into different patches. Bisectability might be
> broken for one or two commits, but I think it would be much clear to
> handle.
>
> Regards,
> Yao Zi

Hi Yao,

Thanks for the review.

I agree that the RTC and sysreset changes should be handled separately
from the devicetree conversion. I will prepare that work as a separate
series first, with the RTC driver, sysreset changes, and board-level
changes split into individual patches.

The next revision of this series will keep the existing board-level
sysreset setup and focus on the devicetree conversion.

-- 
Best regards,
Zhuxu Ran


  reply	other threads:[~2026-09-24  8:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260922-milkv-duo-upstream-dts-v4-0-d45b74dfad36@zohomail.com>
2026-09-22 14:59 ` [PATCH v4 01/11] clk: sophgo: cv1800b: Add SoC-specific compatible strings Zhuxu Ran
2026-09-22 14:59 ` [PATCH v4 02/11] mmc: cv1800b: Add SG2002 compatible string Zhuxu Ran
2026-09-22 14:59 ` [PATCH v4 03/11] dt-bindings: soc: sophgo: add Milk-V Duo 256M board Zhuxu Ran
2026-09-22 14:59 ` [PATCH v4 04/11] riscv: dts: sophgo: cv180x: Add PWR_GPIO controller Zhuxu Ran
2026-09-22 14:59 ` [PATCH v4 05/11] riscv: dts: sophgo: Add Milk-V Duo 256M board support Zhuxu Ran
2026-09-22 14:59 ` [PATCH v4 06/11] riscv: milkv_duo: Use upstream devicetree Zhuxu Ran
2026-09-22 15:46 ` [PATCH v4 07/11] riscv: licheerv_nano: " Zhuxu Ran
2026-09-22 15:46 ` [PATCH v4 08/11] riscv: milkv_duo_256m: " Zhuxu Ran
2026-09-24 12:45   ` Hiago De Franco
2026-09-24 14:47     ` Zhuxu Ran
2026-09-22 15:46 ` [PATCH v4 09/11] rtc: cv1800: Add RTC and system reset support Zhuxu Ran
2026-09-23 17:51   ` Yao Zi
2026-09-24  4:05     ` Zhuxu Ran [this message]
2026-09-22 15:46 ` [PATCH v4 10/11] riscv: dts: sophgo: Drop local CV18xx devicetrees Zhuxu Ran
2026-09-22 15:46 ` [PATCH v4 11/11] clk: sophgo: cv1800b: Drop legacy compatible string Zhuxu Ran

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=DLN902USHBOD.1ODD26B7FLRM2@zohomail.com \
    --to=zhuxu_ran@zohomail.com \
    --cc=akoch@initse.com \
    --cc=casey.connolly@linaro.org \
    --cc=chao.wei@sophgo.com \
    --cc=chen.wang@linux.dev \
    --cc=chenyou910331@gmail.com \
    --cc=conor.dooley@microchip.com \
    --cc=hfranco@baylibre.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=inochiama@gmail.com \
    --cc=jbx6244@gmail.com \
    --cc=jh80.chung@samsung.com \
    --cc=junhui.liu@pigmoral.tech \
    --cc=leo.liang@sifive.com \
    --cc=lukma@denx.de \
    --cc=marex@nabladev.com \
    --cc=me@ziyao.cc \
    --cc=pbrobinson@gmail.com \
    --cc=peng.fan@nxp.com \
    --cc=quentin.schulz@cherry.de \
    --cc=schwab@suse.de \
    --cc=seashell11234455@gmail.com \
    --cc=stefan.roese@mailbox.org \
    --cc=sumit.garg@kernel.org \
    --cc=sumit.garg@oss.qualcomm.com \
    --cc=thomas.bonnefille@bootlin.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.u-boot-project.org \
    --cc=unicorn_wang@outlook.com \
    --cc=varadarajan.narayanan@oss.qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.