From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Prabhakar <prabhakar.csengg@gmail.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
linux-renesas-soc@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Biju Das <biju.das.jz@bp.renesas.com>,
Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [PATCH v2 4/6] clk: renesas: rzv2h: Add fixed-factor module clocks with status reporting
Date: Tue, 1 Jul 2025 14:38:50 +0200 [thread overview]
Message-ID: <CAMuHMdU+E_AJRL=cmARemBy+3Npf2PKnhmXx74DzRc+N7b75gQ@mail.gmail.com> (raw)
In-Reply-To: <20250627204237.214635-5-prabhakar.mahadev-lad.rj@bp.renesas.com>
Hi Prabhakar,
On Fri, 27 Jun 2025 at 22:42, Prabhakar <prabhakar.csengg@gmail.com> wrote:
> From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
>
> Add support for fixed-factor module clocks that can report their enable
> status through the module status monitor. Introduce a new clock type,
> CLK_TYPE_FF_MOD_STATUS, and define the associated structure,
> rzv2h_ff_mod_status_clk, to manage these clocks.
>
> Implement the .is_enabled callback by reading the module status register
> using monitor index and bit definitions. Provide a helper macro,
> DEF_FIXED_MOD_STATUS, to simplify the definition of such clocks.
>
> Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Thanks for the update!
> Note, this patch generates below checkpatch warning but this is
> not a problem.
> `WARNING: struct clk_ops should normally be const`
This is indeed a false positive.
> v1->v2:
> - Moved rzv2h_clk_ff_mod_status_ops to the CPG private data structure
> and initialized it in the CPG probe function.
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
i.e. will queue in renesas-clk for v6.17.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2025-07-01 12:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 20:42 [PATCH v2 0/6] clk: renesas: Add XSPI clock support for RZ/V2N and RZ/V2H(P) Prabhakar
2025-06-27 20:42 ` [PATCH v2 1/6] dt-bindings: clock: renesas,r9a09g056/57-cpg: Add XSPI core clock Prabhakar
2025-07-01 12:34 ` Geert Uytterhoeven
2025-07-02 18:22 ` Geert Uytterhoeven
2025-07-02 19:27 ` Lad, Prabhakar
2025-06-27 20:42 ` [PATCH v2 2/6] clk: renesas: r9a09g056: Add support for xspi mux and divider Prabhakar
2025-07-01 12:39 ` Geert Uytterhoeven
2025-06-27 20:42 ` [PATCH v2 3/6] clk: renesas: r9a09g057: " Prabhakar
2025-07-01 12:39 ` Geert Uytterhoeven
2025-06-27 20:42 ` [PATCH v2 4/6] clk: renesas: rzv2h: Add fixed-factor module clocks with status reporting Prabhakar
2025-07-01 12:38 ` Geert Uytterhoeven [this message]
2025-06-27 20:42 ` [PATCH v2 5/6] clk: renesas: r9a09g056: Add XSPI clock/reset Prabhakar
2025-07-01 12:40 ` Geert Uytterhoeven
2025-06-27 20:42 ` [PATCH v2 6/6] clk: renesas: r9a09g057: " Prabhakar
2025-07-01 12:40 ` Geert Uytterhoeven
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='CAMuHMdU+E_AJRL=cmARemBy+3Npf2PKnhmXx74DzRc+N7b75gQ@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fabrizio.castro.jz@renesas.com \
--cc=krzk+dt@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mturquette@baylibre.com \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh@kernel.org \
--cc=sboyd@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;
as well as URLs for NNTP newsgroup(s).