From: Dinh Nguyen <dinguyen@kernel.og>
To: Khairul Anuar Romli <khairul.anuar.romli@altera.com>,
Dinh Nguyen <dinguyen@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
"open list:COMMON CLK FRAMEWORK" <linux-clk@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Ang Tien Sung <tiensung.ang@altera.com>
Subject: Re: [PATCH v2 1/1] clk: socfpga: agilex5: add clock driver for Agilex5
Date: Mon, 13 Oct 2025 14:11:48 -0500 [thread overview]
Message-ID: <b8e8ab20-d499-4eeb-8a4b-a52d366b3b09@kernel.og> (raw)
In-Reply-To: <a4e14e6002d3941fcb918053c1453eb1a757ef49.1759718838.git.khairul.anuar.romli@altera.com>
On 10/5/25 22:10, Khairul Anuar Romli wrote:
> Add the new Clock manager driver to support new Agilex5 platform. The new
> driver got rid of the clk_parent_data structures as there are no 'clock-names'
> property in the DT bindings and use parent_names internally. This is based on
> the previous feedback from the maintainer.
>
> Signed-off-by: Ang Tien Sung <tiensung.ang@altera.com>
> Signed-off-by: Khairul Anuar Romli <khairul.anuar.romli@altera.com>
> ---
> Changes in v2:
> - Add clk-agilex5 to Makefile
> - Add Kconfig to include Agilex5 clock manager
> - us of.h instead of of_device and of_address
> - use devm_platform_ioremap_resource to simplify the get resource
> - Fix bound-checking coverage struct clock_data
> - Clean up harmless TODO comment
> ---
> drivers/clk/socfpga/Kconfig | 2 +-
> drivers/clk/socfpga/Makefile | 2 +-
> drivers/clk/socfpga/clk-agilex5.c | 561 +++++++++++++++++++++++++++
> drivers/clk/socfpga/clk-gate-s10.c | 53 +++
> drivers/clk/socfpga/clk-periph-s10.c | 41 ++
> drivers/clk/socfpga/clk-pll-s10.c | 36 ++
> drivers/clk/socfpga/stratix10-clk.h | 43 ++
> 7 files changed, 736 insertions(+), 2 deletions(-)
> create mode 100644 drivers/clk/socfpga/clk-agilex5.c
>
<snip>
> +
> +static int agilex5_clkmgr_init(struct platform_device *pdev)
> +{
> + struct device_node *np = pdev->dev.of_node;
> + struct device *dev = &pdev->dev;
> + struct stratix10_clock_data *clk_data;
> + void __iomem *base;
> + int i, num_clks;
> +
> + base = devm_platform_ioremap_resource(pdev, 0);
> + if (IS_ERR(base))
> + return PTR_ERR(base);
> +
> + num_clks = AGILEX5_NUM_CLKS;
> +
> + clk_data = devm_kzalloc(dev, struct_size(clk_data, clk_data.hws,
> + num_clks), GFP_KERNEL);
Please fix these 2 warnings from checkpatch --strict:
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit
description?)
#7:
Add the new Clock manager driver to support new Agilex5 platform. The
new driver
CHECK: Alignment should match open parenthesis
#565: FILE: drivers/clk/socfpga/clk-agilex5.c:504:
+ clk_data = devm_kzalloc(dev, struct_size(clk_data, clk_data.hws,
+ num_clks), GFP_KERNEL);
total: 0 errors, 2 warnings, 1 checks, 768 lines check
Dinh
prev parent reply other threads:[~2025-10-13 19:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1759718838.git.khairul.anuar.romli@altera.com>
2025-10-06 3:10 ` [PATCH v2 1/1] clk: socfpga: agilex5: add clock driver for Agilex5 Khairul Anuar Romli
2025-10-13 19:11 ` Dinh Nguyen [this message]
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=b8e8ab20-d499-4eeb-8a4b-a52d366b3b09@kernel.og \
--to=dinguyen@kernel.og \
--cc=dinguyen@kernel.org \
--cc=khairul.anuar.romli@altera.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=tiensung.ang@altera.com \
/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