From: "Stefan Dösinger" <stefandoesinger@gmail.com>
To: sashiko-reviews@lists.linux.dev
Cc: lee@kernel.org, vkoul@kernel.org, linux-phy@lists.infradead.org,
neil.armstrong@linaro.org, linux-clk@vger.kernel.org,
conor+dt@kernel.org, devicetree@vger.kernel.org,
mfd@lists.linux.dev, robh@kernel.org, olteanv@gmail.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v12 09/12] clk: zte: Introduce a driver for zx297520v3 matrix clocks
Date: Wed, 23 Sep 2026 22:06:51 +0300 [thread overview]
Message-ID: <wditwJCDQOOx8yviJrPU5g@gmail.com> (raw)
In-Reply-To: <20260923184051.0BA291F0089E@smtp.kernel.org>
[-- Attachment #1.1: Type: text/plain, Size: 280 bytes --]
Am Mittwoch, 23. September 2026, 21:40:50 Ostafrikanische Zeit schrieb
sashiko-bot@kernel.org:
> [Severity: Medium]
> Is the mapping for ZX297520V3_RFFE_WCLK intentionally missing from
> zx297520v3_matrix_exports?
Sashiko is right about this - this clock is missing by accident.
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 870 bytes --]
[-- Attachment #2: Type: text/plain, Size: 112 bytes --]
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2026-09-23 19:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 18:28 [PATCH v12 00/12] ZTE zx297520v3 clock bindings and driver Stefan Dösinger
2026-09-23 18:28 ` [PATCH v12 01/12] dt-bindings: clk: zte: Add zx297520v3 top clock and reset controller Stefan Dösinger
2026-09-23 18:33 ` sashiko-bot
2026-09-23 18:28 ` [PATCH v12 02/12] dt-bindings: clk: zte: Add zx297520v3 matrix " Stefan Dösinger
2026-09-23 18:37 ` sashiko-bot
2026-09-23 18:28 ` [PATCH v12 03/12] dt-bindings: clk: zte: Add zx297520v3 LSP " Stefan Dösinger
2026-09-23 18:32 ` sashiko-bot
2026-09-23 18:28 ` [PATCH v12 04/12] mfd: zx297520v3: Add a clock and reset MFD driver Stefan Dösinger
2026-09-23 18:35 ` sashiko-bot
2026-09-24 14:15 ` Lee Jones
2026-09-23 18:28 ` [PATCH v12 05/12] clk: zte: Add Clock registration infrastructure Stefan Dösinger
2026-09-23 18:36 ` sashiko-bot
2026-09-23 18:28 ` [PATCH v12 06/12] clk: zte: Add regmap-based clocks Stefan Dösinger
2026-09-23 18:38 ` sashiko-bot
2026-09-23 18:28 ` [PATCH v12 07/12] clk: zte: Add zx PLL support infrastructure Stefan Dösinger
2026-09-23 18:42 ` sashiko-bot
2026-09-23 18:28 ` [PATCH v12 08/12] clk: zte: Introduce a driver for zx297520v3 top clocks Stefan Dösinger
2026-09-23 18:44 ` sashiko-bot
2026-09-23 18:28 ` [PATCH v12 09/12] clk: zte: Introduce a driver for zx297520v3 matrix clocks Stefan Dösinger
2026-09-23 18:40 ` sashiko-bot
2026-09-23 19:06 ` Stefan Dösinger [this message]
2026-09-23 18:28 ` [PATCH v12 10/12] clk: zte: Introduce a driver for zx297520v3 LSP clocks Stefan Dösinger
2026-09-23 18:40 ` sashiko-bot
2026-09-23 18:28 ` [PATCH v12 11/12] reset: zte: Add a zx297520v3 reset driver Stefan Dösinger
2026-09-23 18:45 ` sashiko-bot
2026-09-23 18:28 ` [PATCH v12 12/12] ARM: dts: zte: Declare zx297520v3 CRM device nodes Stefan Dösinger
2026-09-23 18:39 ` sashiko-bot
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=wditwJCDQOOx8yviJrPU5g@gmail.com \
--to=stefandoesinger@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=mfd@lists.linux.dev \
--cc=neil.armstrong@linaro.org \
--cc=olteanv@gmail.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=vkoul@kernel.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