Received-SPF: pass (google.com: domain of linux-kernel+bounces-32542-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Precedence: bulk
MIME-Version: 1.0
References: <20240122080631.2880-1-qiujingbao.dlmu@gmail.com>
 <20240122081722868bdda5@mail.local> <CAJRtX8QU8iHY1oQJ1uDN3YOmCeN7SH+vPC8nD29WS5+2DT1oKQ@mail.gmail.com>
 <fcd64bbb-9f3c-4e62-96a4-84cb1e3ac59d@linaro.org>
In-Reply-To: <fcd64bbb-9f3c-4e62-96a4-84cb1e3ac59d@linaro.org>
From: Jingbao Qiu <qiujingbao.dlmu@gmail.com>
Date: Mon, 22 Jan 2024 16:42:53 +0800
Message-ID: <CAJRtX8R9bZZyU_6XZ+G_rctRu3TTEAUamVbq1h8q+Fzzd6SZiw@mail.gmail.com>
Subject: Re: [PATCH v7 2/3] rtc: sophgo: add rtc support for Sophgo CV1800 SoC
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>, robh+dt@kernel.org, 
	krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org, chao.wei@sophgo.com, 
	unicorn_wang@outlook.com, paul.walmsley@sifive.com, palmer@dabbelt.com, 
	aou@eecs.berkeley.edu, linux-rtc@vger.kernel.org, devicetree@vger.kernel.org, 
	linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org, 
	dlan@gentoo.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Jan 22, 2024 at 4:37=E2=80=AFPM Krzysztof Kozlowski
<krzysztof.kozlowski@linaro.org> wrote:
>
> On 22/01/2024 09:34, Jingbao Qiu wrote:
> > On Mon, Jan 22, 2024 at 4:17=E2=80=AFPM Alexandre Belloni
> > <alexandre.belloni@bootlin.com> wrote:
> >>
> >> On 22/01/2024 16:06:30+0800, Jingbao Qiu wrote:
> >>> Implement the RTC driver for CV1800, which able to provide time alarm
> >>> and calibrate functionality.
> >>>
> >>> Signed-off-by: Jingbao Qiu <qiujingbao.dlmu@gmail.com>
> >>> ---
> >>>
> >>> Depends on https://lore.kernel.org/all/IA1PR20MB4953C774D41EDF1EADB6E=
C18BB6D2@IA1PR20MB4953.namprd20.prod.outlook.com/
> >>
> >> What is the dependency?
> >>
> >
> > Thank you, this driver requires support from the CLK driver.
>
> How? This is really unusual. Just to remind: we talk about build
> dependencies. Other do not matter for new drivers, right? Otherwise what
> is being broken and how it could be even broken?
>
yes, you're right. This is wrong, I will drop it.

Best regards,
Jingbao Qiu