From: Philipp Zabel <p.zabel@pengutronix.de>
To: gabriel.fernandez@foss.st.com,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 4/5] clk: stm32: introduce clocks for STM32MP257 platform
Date: Wed, 06 Dec 2023 15:20:20 +0100 [thread overview]
Message-ID: <ec1912eab8bead59f520c48b6d73a084fd07732d.camel@pengutronix.de> (raw)
In-Reply-To: <20231206140029.492906-5-gabriel.fernandez@foss.st.com>
Hi Gabriel,
On Mi, 2023-12-06 at 15:00 +0100, gabriel.fernandez@foss.st.com wrote:
> From: Gabriel Fernandez <gabriel.fernandez@foss.st.com>
>
> This driver is intended for the STM32MP25 clock family and utilizes
> the stm32-core API, similar to the stm32mp13 clock driver.
>
> Signed-off-by: Gabriel Fernandez <gabriel.fernandez@foss.st.com>
> ---
[...]
> diff --git a/drivers/clk/stm32/stm32mp25_rcc.h b/drivers/clk/stm32/stm32mp25_rcc.h
> new file mode 100644
> index 000000000000..b1aca78a0b22
> --- /dev/null
> +++ b/drivers/clk/stm32/stm32mp25_rcc.h
> @@ -0,0 +1,4977 @@
> +/* SPDX-License-Identifier: GPL-2.0-only */
> +/*
> + * Copyright (C) STMicroelectronics 2023 - All Rights Reserved
> + * Author: Gabriel Fernandez <gabriel.fernandez@foss.st.com> for STMicroelectronics.
> + */
> +
> +#ifndef STM32MP25_RCC_H
> +#define STM32MP25_RCC_H
> +
> +#define RCC_SECCFGR0 0x0
[...]
What is the purpose of all the unused #defines?
I initially wanted to point out that the _SHIFT #defines are redundant
because the same information is already contained in the corresponding
_MASK #defines, but it seems like neither of the register field
definitions are used anywhere. It appears only some of the *CFGR
register offset #defines are actually used.
regards
Philipp
next prev parent reply other threads:[~2023-12-06 14:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 14:00 [PATCH v5 0/5] Introduce STM32MP257 clock driver gabriel.fernandez
2023-12-06 14:00 ` [PATCH v5 1/5] clk: stm32mp1: move stm32mp1 clock driver into stm32 directory gabriel.fernandez
2023-12-06 14:00 ` [PATCH v5 2/5] clk: stm32mp1: use stm32mp13 reset driver gabriel.fernandez
2023-12-06 14:00 ` [PATCH v5 3/5] dt-bindings: stm32: add clocks and reset binding for stm32mp25 platform gabriel.fernandez
2023-12-06 14:00 ` [PATCH v5 4/5] clk: stm32: introduce clocks for STM32MP257 platform gabriel.fernandez
2023-12-06 14:20 ` Philipp Zabel [this message]
2023-12-06 14:50 ` Gabriel FERNANDEZ
2023-12-06 14:00 ` [PATCH v5 5/5] arm64: dts: st: add rcc support in stm32mp251 gabriel.fernandez
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=ec1912eab8bead59f520c48b6d73a084fd07732d.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gabriel.fernandez@foss.st.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@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).