From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Ralph Siemsen <ralph.siemsen@linaro.org>
Cc: linux-renesas-soc@vger.kernel.org, linux-clk@vger.kernel.org,
Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH v2 4/4] clk: renesas: r9a06g032: improve clock tables
Date: Thu, 2 Mar 2023 09:23:27 +0100 [thread overview]
Message-ID: <20230302092327.234a360e@xps-13> (raw)
In-Reply-To: <20230301215520.828455-5-ralph.siemsen@linaro.org>
Hi Ralph,
ralph.siemsen@linaro.org wrote on Wed, 1 Mar 2023 16:55:20 -0500:
> Each entry in the clock table specifies a number of individual bits in
> registers, for contolling clock reset, gaiting, etc. These reg/bit were
> packed into a u16 to save space. The combined value is difficult to
> understand when reviewing the clock table entries.
>
> Introduce a "struct regbit" which still occupies only 16 bits, but
> allows the register and bit values to be specified explicitly. Convert
> all previous uses of u16 for reg/bit into "struct regbit".
>
> The bulk of this patch converts the clock table to use struct regbit,
> making use of the RB() helper macro. The conversion was automated by
> script, and as a further verification, the compiled binary of the table
> was compared before/after the change (with objdump -D).
>
> The clk_rdesc_set() function now checks for zero reg/bit internally.
> This allows callers of that function to remove those checks.
>
> Signed-off-by: Ralph Siemsen <ralph.siemsen@linaro.org>
Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com>
Thanks,
Miquèl
next prev parent reply other threads:[~2023-03-02 8:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 21:55 [PATCH v2 0/4] Renesas r9a06g032 clock table improvements Ralph Siemsen
2023-03-01 21:55 ` [PATCH v2 1/4] clk: renesas: r9a06g032: improve readability Ralph Siemsen
2023-03-10 13:54 ` Geert Uytterhoeven
2023-03-01 21:55 ` [PATCH v2 2/4] clk: renesas: r9a06g032: drop unused fields Ralph Siemsen
2023-03-10 13:54 ` Geert Uytterhoeven
2023-03-01 21:55 ` [PATCH v2 3/4] clk: renesas: r9a06g032: document structs Ralph Siemsen
2023-03-02 8:23 ` Miquel Raynal
2023-03-10 13:55 ` Geert Uytterhoeven
2023-03-01 21:55 ` [PATCH v2 4/4] clk: renesas: r9a06g032: improve clock tables Ralph Siemsen
2023-03-02 8:23 ` Miquel Raynal [this message]
2023-03-10 13:56 ` 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=20230302092327.234a360e@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=geert+renesas@glider.be \
--cc=linux-clk@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=ralph.siemsen@linaro.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 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.