From: Brian Masney <bmasney@redhat.com>
To: dongxuyang@eswincomputing.com
Cc: mturquette@baylibre.com, sboyd@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, p.zabel@pengutronix.de,
huangyifeng@eswincomputing.com, ningyu@eswincomputing.com,
linmin@eswincomputing.com, pinkesh.vaghela@einfochips.com
Subject: Re: [PATCH 2/3] clk: eswin: Add eic7700 HSP clock driver
Date: Fri, 3 Apr 2026 10:00:14 -0400 [thread overview]
Message-ID: <ac_H7kSCgzz5HRxV@redhat.com> (raw)
In-Reply-To: <20260403093612.725-1-dongxuyang@eswincomputing.com>
Hi Xuyang,
On Fri, Apr 03, 2026 at 05:36:12PM +0800, dongxuyang@eswincomputing.com wrote:
> From: Xuyang Dong <dongxuyang@eswincomputing.com>
>
> Add driver for the ESWIN EIC7700 high-speed peripherals system
> clock controller and register an auxiliary device for system
> reset controller which is named as "hsp-reset".
>
> Signed-off-by: Xuyang Dong <dongxuyang@eswincomputing.com>
> ---
> drivers/clk/eswin/Kconfig | 12 +
> drivers/clk/eswin/Makefile | 1 +
> drivers/clk/eswin/clk-eic7700-hsp.c | 339 ++++++++++++++++++++++++++++
> 3 files changed, 352 insertions(+)
> create mode 100644 drivers/clk/eswin/clk-eic7700-hsp.c
>
> diff --git a/drivers/clk/eswin/Kconfig b/drivers/clk/eswin/Kconfig
> index 0406ec499ec9..e6cc2a407bac 100644
> --- a/drivers/clk/eswin/Kconfig
> +++ b/drivers/clk/eswin/Kconfig
> @@ -13,3 +13,15 @@ config COMMON_CLK_EIC7700
> SoC. The clock controller generates and supplies clocks to various
> peripherals within the SoC.
> Say yes here to support the clock controller on the EIC7700 SoC.
> +
> +config COMMON_CLK_EIC7700_HSP
> + tristate "EIC7700 HSP Clock Driver"
> + depends on ARCH_ESWIN || COMPILE_TEST
> + select AUXILIARY_BUS
> + select COMMON_CLK_EIC7700
> + select RESET_EIC7700_HSP if RESET_CONTROLLER
> + help
> + This driver provides support for clock controller on ESWIN EIC7700
> + HSP. The clock controller generates and supplies clocks to high
> + speed peripherals within the SoC.
> + Say yes here to support the clock controller on the EIC7700 HSP.
> diff --git a/drivers/clk/eswin/Makefile b/drivers/clk/eswin/Makefile
> index 4a7c2af82164..21a09a3396df 100644
> --- a/drivers/clk/eswin/Makefile
> +++ b/drivers/clk/eswin/Makefile
> @@ -6,3 +6,4 @@
> obj-$(CONFIG_COMMON_CLK_ESWIN) += clk.o
>
> obj-$(CONFIG_COMMON_CLK_EIC7700) += clk-eic7700.o
> +obj-$(CONFIG_COMMON_CLK_EIC7700_HSP) += clk-eic7700-hsp.o
> diff --git a/drivers/clk/eswin/clk-eic7700-hsp.c b/drivers/clk/eswin/clk-eic7700-hsp.c
> new file mode 100644
> index 000000000000..65ad9e762ee9
> --- /dev/null
> +++ b/drivers/clk/eswin/clk-eic7700-hsp.c
> @@ -0,0 +1,339 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * Copyright 2026, Beijing ESWIN Computing Technology Co., Ltd..
> + * All rights reserved.
> + *
> + * ESWIN EIC7700 HSP Clock Driver
> + *
> + * Authors: Xuyang Dong <dongxuyang@eswincomputing.com>
> + */
> +
> +#include <linux/auxiliary_bus.h>
> +#include <linux/clk-provider.h>
> +#include <linux/io.h>
> +#include <linux/platform_device.h>
> +
> +#include <dt-bindings/clock/eswin,eic7700-hspcrg.h>
> +
> +#include "common.h"
> +
> +#define EIC7700_HSP_SATA_REG 0x300
> +#define EIC7700_HSP_MSHC0_REG 0x510
> +#define EIC7700_HSP_MSHC1_REG 0x610
> +#define EIC7700_HSP_MSHC2_REG 0x710
> +#define EIC7700_HSP_USB0_REG 0x800
> +#define EIC7700_HSP_USB0_REF_REG 0x83c
> +#define EIC7700_HSP_USB1_REG 0x900
> +#define EIC7700_HSP_USB1_REF_REG 0x93c
> +
> +#define USB_REF_XTAL24M 0x2a
> +#define EIC7700_HSP_NR_CLKS (EIC7700_HSP_CLK_GATE_SATA + 1)
> +
> +struct eic7700_hsp_clk_gate {
> + struct clk_hw hw;
> + unsigned int id;
> + void __iomem *reg;
> + void __iomem *ref_reg;
> + const char *name;
> + const struct clk_parent_data *parent_data;
> + unsigned long flags;
> + unsigned long offset;
> + unsigned long ref_offset;
> + u8 bit_idx;
> + u8 gate_flags;
> + spinlock_t *lock; /* protect register read-modify-write cycle */
> +};
> +
> +static inline struct eic7700_hsp_clk_gate *to_gate_clk(struct clk_hw *hw)
> +{
> + return container_of(hw, struct eic7700_hsp_clk_gate, hw);
> +}
> +
> +#define EIC7700_HSP_GATE(_id, _name, _pdata, _flags, _offset, _idx, \
> + _ref_offset) \
> + { \
> + .id = _id, \
> + .name = _name, \
> + .parent_data = _pdata, \
> + .flags = _flags, \
> + .offset = _offset, \
> + .ref_offset = _ref_offset, \
> + .bit_idx = _idx, \
> + }
> +
> +static void hsp_clk_gate_endisable(struct clk_hw *hw, int enable)
> +{
> + struct eic7700_hsp_clk_gate *gate = to_gate_clk(hw);
> + unsigned long flags;
> + u32 reg;
> +
> + spin_lock_irqsave(gate->lock, flags);
> +
> + reg = readl(gate->reg);
> +
> + if (enable)
> + reg |= BIT(gate->bit_idx);
> + else
> + reg &= ~BIT(gate->bit_idx);
> +
> + /*
> + * Hardware bug: The reference clock is 24MHz, but the reference clock
> + * register reset to an incorrect default value.
> + * Workaround: Rewrite the correct value before enabling/disabling
> + * the gate clock.
> + */
> + writel(USB_REF_XTAL24M, gate->ref_reg);
> + writel(reg, gate->reg);
> +
> + spin_unlock_irqrestore(gate->lock, flags);
> +}
> +
> +static int hsp_clk_gate_enable(struct clk_hw *hw)
> +{
> + hsp_clk_gate_endisable(hw, 1);
> +
> + return 0;
> +}
> +
> +static void hsp_clk_gate_disable(struct clk_hw *hw)
> +{
> + hsp_clk_gate_endisable(hw, 0);
> +}
> +
> +static int hsp_clk_gate_is_enabled(struct clk_hw *hw)
> +{
> + struct eic7700_hsp_clk_gate *gate = to_gate_clk(hw);
> + u32 reg;
> +
> + reg = readl(gate->reg);
> +
> + reg &= BIT(gate->bit_idx);
Personally I would remove the newline between the two reg lines
since it's the same variable.
> +
> + return reg ? 1 : 0;
> +}
> +
> +static const struct clk_ops hsp_clk_gate_ops = {
> + .enable = hsp_clk_gate_enable,
> + .disable = hsp_clk_gate_disable,
> + .is_enabled = hsp_clk_gate_is_enabled,
> +};
> +
> +static struct clk_hw *
> +hsp_clk_register_gate(struct device *dev, unsigned int id, const char *name,
> + const struct clk_parent_data *parent_data,
> + unsigned long flags, void __iomem *reg,
> + void __iomem *ref_reg, u8 bit_idx, u8 clk_gate_flags,
> + spinlock_t *lock)
> +{
> + struct eic7700_hsp_clk_gate *gate;
> + struct clk_init_data init;
struct clk_init_data init = {};
I posted a fix earlier this week with some details about a potential
issue.
https://lore.kernel.org/linux-clk/20260330-clk-visconti-init-v1-1-ac3e825e54b5@redhat.com/
> + struct clk_hw *hw;
> + int ret;
> +
> + gate = devm_kzalloc(dev, sizeof(*gate), GFP_KERNEL);
> + if (!gate)
> + return ERR_PTR(-ENOMEM);
> +
> + init.name = name;
> + init.ops = &hsp_clk_gate_ops;
> + init.flags = flags;
> + init.parent_data = parent_data;
> + init.num_parents = 1;
> +
> + gate->id = id;
> + gate->reg = reg;
> + gate->ref_reg = ref_reg;
> + gate->bit_idx = bit_idx;
> + gate->gate_flags = clk_gate_flags;
> + gate->lock = lock;
> + gate->hw.init = &init;
> +
> + hw = &gate->hw;
> + ret = devm_clk_hw_register(dev, hw);
> + if (ret)
> + hw = ERR_PTR(ret);
> +
> + return hw;
> +}
> +
> +static struct clk_parent_data hsp_cfg[] = {
static const here and below?
> + { .fw_name = "hsp_cfg" }
> +};
> +
> +static struct clk_parent_data hsp_mmc[] = {
> + { .fw_name = "hsp_mmc" }
> +};
Sashiko brought up a good question:
https://sashiko.dev/#/patchset/20260403093459.612-1-dongxuyang%40eswincomputing.com
Will these clocks be registered to their intended parents?
If eswin_clk_register_fixed_factor() ignores the .fw_name field and
registers using devm_clk_hw_register_fixed_factor_index(), it will use the
.index field.
Since .index is implicitly 0 for both hsp_cfg and hsp_mmc, won't all
these fixed factor clocks be incorrectly parented to the clock at index 0
of the DT clocks property instead of hsp_mmc and hsp_cfg?
> +
> +static struct clk_parent_data hsp_usb_sata[] = {
> + { .fw_name = "hsp_sata" }
> +};
> +
> +static struct eswin_fixed_factor_clock eic7700_hsp_factor_clks[] = {
More places for static const? I'll leave out the others.
> + ESWIN_FACTOR(EIC7700_HSP_CLK_FAC_CFG_DIV2, "factor_hsp_cfg_div2",
> + hsp_cfg, 1, 2, 0),
> + ESWIN_FACTOR(EIC7700_HSP_CLK_FAC_CFG_DIV4, "factor_hsp_cfg_div4",
> + hsp_cfg, 1, 4, 0),
> + ESWIN_FACTOR(EIC7700_HSP_CLK_FAC_MMC_DIV10, "factor_hsp_mmc_div10",
> + hsp_mmc, 1, 10, 0),
> +};
> +
> +static struct eswin_gate_clock eic7700_hsp_gate_clks[] = {
> + ESWIN_GATE(EIC7700_HSP_CLK_GATE_SATA, "gate_clk_hsp_sata", hsp_usb_sata,
> + CLK_SET_RATE_PARENT, EIC7700_HSP_SATA_REG, 28, 0),
> + ESWIN_GATE(EIC7700_HSP_CLK_GATE_MSHC0_TMR, "gate_clk_hsp_mshc0_tmr",
> + hsp_mmc, CLK_SET_RATE_PARENT, EIC7700_HSP_MSHC0_REG, 8, 0),
> + ESWIN_GATE(EIC7700_HSP_CLK_GATE_MSHC1_TMR, "gate_clk_hsp_mshc1_tmr",
> + hsp_mmc, CLK_SET_RATE_PARENT, EIC7700_HSP_MSHC1_REG, 8, 0),
> + ESWIN_GATE(EIC7700_HSP_CLK_GATE_MSHC2_TMR, "gate_clk_hsp_mshc2_tmr",
> + hsp_mmc, CLK_SET_RATE_PARENT, EIC7700_HSP_MSHC2_REG, 8, 0),
> +};
> +
> +static struct eic7700_hsp_clk_gate eic7700_hsp_spec_gate_clks[] = {
> + EIC7700_HSP_GATE(EIC7700_HSP_CLK_GATE_USB0, "gate_clk_hsp_usb0",
> + hsp_usb_sata, CLK_SET_RATE_PARENT,
> + EIC7700_HSP_USB0_REG, 28, EIC7700_HSP_USB0_REF_REG),
> + EIC7700_HSP_GATE(EIC7700_HSP_CLK_GATE_USB1, "gate_clk_hsp_usb1",
> + hsp_usb_sata, CLK_SET_RATE_PARENT,
> + EIC7700_HSP_USB1_REG, 28, EIC7700_HSP_USB1_REF_REG),
> +};
> +
> +static const struct clk_parent_data mux_mmc_3mux1_p[] = {
> + { .fw_name = "hsp_cfg" },
> + { .hw = &eic7700_hsp_factor_clks[0].hw },
> + { .hw = &eic7700_hsp_factor_clks[1].hw },
> +};
> +
> +static const struct clk_parent_data mux_mmc_2mux1_p[] = {
> + { .fw_name = "hsp_mmc" },
> + { .hw = &eic7700_hsp_factor_clks[2].hw },
> +};
> +
> +static u32 mux_mmc_3mux1_tbl[] = { 0x0, 0x1, 0x3 };
> +
> +static struct eswin_mux_clock eic7700_hsp_mux_clks[] = {
> + ESWIN_MUX_TBL(EIC7700_HSP_CLK_MUX_EMMC_3MUX1, "mux_hsp_emmc_3mux1",
> + mux_mmc_3mux1_p, ARRAY_SIZE(mux_mmc_3mux1_p),
> + CLK_SET_RATE_PARENT, EIC7700_HSP_MSHC0_REG, 16, 2, 0,
> + mux_mmc_3mux1_tbl),
> + ESWIN_MUX_TBL(EIC7700_HSP_CLK_MUX_SD0_3MUX1, "mux_hsp_sd0_3mux1",
> + mux_mmc_3mux1_p, ARRAY_SIZE(mux_mmc_3mux1_p),
> + CLK_SET_RATE_PARENT, EIC7700_HSP_MSHC1_REG, 16, 2, 0,
> + mux_mmc_3mux1_tbl),
> + ESWIN_MUX_TBL(EIC7700_HSP_CLK_MUX_SD1_3MUX1, "mux_hsp_sd1_3mux1",
> + mux_mmc_3mux1_p, ARRAY_SIZE(mux_mmc_3mux1_p),
> + CLK_SET_RATE_PARENT, EIC7700_HSP_MSHC2_REG, 16, 2, 0,
> + mux_mmc_3mux1_tbl),
> + ESWIN_MUX(EIC7700_HSP_CLK_MUX_EMMC_CQE_2MUX1, "mux_hsp_emmc_cqe_2mux1",
> + mux_mmc_2mux1_p, ARRAY_SIZE(mux_mmc_2mux1_p),
> + CLK_SET_RATE_PARENT, EIC7700_HSP_MSHC0_REG, 0, 1, 0),
> + ESWIN_MUX(EIC7700_HSP_CLK_MUX_SD0_CQE_2MUX1, "mux_hsp_sd0_cqe_2mux1",
> + mux_mmc_2mux1_p, ARRAY_SIZE(mux_mmc_2mux1_p),
> + CLK_SET_RATE_PARENT, EIC7700_HSP_MSHC1_REG, 0, 1, 0),
> + ESWIN_MUX(EIC7700_HSP_CLK_MUX_SD1_CQE_2MUX1, "mux_hsp_sd1_cqe_2mux1",
> + mux_mmc_2mux1_p, ARRAY_SIZE(mux_mmc_2mux1_p),
> + CLK_SET_RATE_PARENT, EIC7700_HSP_MSHC2_REG, 0, 1, 0),
> +};
> +
> +static struct eswin_clk_info eic7700_hsp_clks[] = {
> + ESWIN_GATE_TYPE(EIC7700_HSP_CLK_GATE_EMMC, "gate_clk_hsp_emmc",
> + EIC7700_HSP_CLK_MUX_EMMC_3MUX1,
> + CLK_SET_RATE_PARENT | CLK_IGNORE_UNUSED,
> + EIC7700_HSP_MSHC0_REG, 24, 0),
> + ESWIN_GATE_TYPE(EIC7700_HSP_CLK_GATE_SD0, "gate_clk_hsp_sd0",
> + EIC7700_HSP_CLK_MUX_SD0_3MUX1,
> + CLK_SET_RATE_PARENT | CLK_IGNORE_UNUSED,
> + EIC7700_HSP_MSHC1_REG, 24, 0),
> + ESWIN_GATE_TYPE(EIC7700_HSP_CLK_GATE_SD1, "gate_clk_hsp_sd1",
> + EIC7700_HSP_CLK_MUX_SD1_3MUX1,
> + CLK_SET_RATE_PARENT | CLK_IGNORE_UNUSED,
> + EIC7700_HSP_MSHC2_REG, 24, 0),
> +};
> +
> +static int eic7700_hsp_clk_probe(struct platform_device *pdev)
> +{
> + struct device *dev = &pdev->dev;
> + struct auxiliary_device *adev;
> + struct eswin_clock_data *data;
> + struct clk_hw *hw;
> + int i, ret;
> +
> + data = eswin_clk_init(pdev, EIC7700_HSP_NR_CLKS);
> + if (IS_ERR(data))
> + return dev_err_probe(dev, PTR_ERR(data),
> + "failed to get clk data!\n");
> +
> + ret = eswin_clk_register_fixed_factor
> + (dev, eic7700_hsp_factor_clks,
> + ARRAY_SIZE(eic7700_hsp_factor_clks), data);
The first two lines can be combined together to improve the formatting:
ret = eswin_clk_register_fixed_factor(dev, eic7700_hsp_factor_clks,
> + if (ret)
> + return dev_err_probe(dev, ret,
> + "failed to register fixed factor clock\n");
> +
> + ret = eswin_clk_register_gate(dev, eic7700_hsp_gate_clks,
> + ARRAY_SIZE(eic7700_hsp_gate_clks), data);
> + if (ret)
> + return dev_err_probe(dev, ret,
> + "failed to register gate clock\n");
> +
> + ret = eswin_clk_register_mux(dev, eic7700_hsp_mux_clks,
> + ARRAY_SIZE(eic7700_hsp_mux_clks),
> + data);
> + if (ret)
> + return dev_err_probe(dev, ret,
> + "failed to register mux clock\n");
> +
> + ret = eswin_clk_register_clks(dev, eic7700_hsp_clks,
> + ARRAY_SIZE(eic7700_hsp_clks), data);
> + if (ret)
> + return dev_err_probe(dev, ret,
> + "failed to register clock\n");
> +
> + for (i = 0; i < ARRAY_SIZE(eic7700_hsp_spec_gate_clks); i++) {
> + struct eic7700_hsp_clk_gate *gate;
> +
> + gate = &eic7700_hsp_spec_gate_clks[i];
> + hw = hsp_clk_register_gate(dev, gate->id, gate->name,
> + gate->parent_data, gate->flags,
> + data->base + gate->offset,
> + data->base + gate->ref_offset,
> + gate->bit_idx, 0, &data->lock);
> + if (IS_ERR(hw))
> + return dev_err_probe(dev, PTR_ERR(hw),
> + "failed to register gate clock\n");
> +
> + data->clk_data.hws[gate->id] = hw;
> + }
> +
> + ret = devm_of_clk_add_hw_provider(dev, of_clk_hw_onecell_get,
> + &data->clk_data);
> + if (ret)
> + return dev_err_probe(dev, ret, "add clk provider failed\n");
> +
> + adev = devm_auxiliary_device_create(dev, "hsp-reset",
> + (__force void *)data->base);
So this driver is sharing the same register space with the reset driver,
and the reset driver calls devm_regmap_init_mmio(). What do you think
about having a shared regmap between the two drivers so that the __force
is not needed?
Brian
> + if (!adev)
> + return dev_err_probe(dev, -ENODEV,
> + "register hsp-reset device failed\n");
> +
> + return 0;
> +}
> +
> +static const struct of_device_id eic7700_hsp_clock_dt_ids[] = {
> + { .compatible = "eswin,eic7700-hspcrg", },
> + { /* sentinel */ }
> +};
> +MODULE_DEVICE_TABLE(of, eic7700_hsp_clock_dt_ids);
> +
> +static struct platform_driver eic7700_hsp_clock_driver = {
> + .probe = eic7700_hsp_clk_probe,
> + .driver = {
> + .name = "eic7700-hsp-clock",
> + .of_match_table = eic7700_hsp_clock_dt_ids,
> + },
> +};
> +
> +module_platform_driver(eic7700_hsp_clock_driver);
> +
> +MODULE_LICENSE("GPL");
> +MODULE_AUTHOR("Xuyang Dong <dongxuyang@eswincomputing.com>");
> +MODULE_DESCRIPTION("ESWIN EIC7700 HSP clock controller driver");
> --
> 2.34.1
>
next prev parent reply other threads:[~2026-04-03 14:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 9:34 [PATCH 0/3] Add driver support for ESWIN EIC7700 HSP clock and reset generator dongxuyang
2026-04-03 9:35 ` [PATCH 1/3] dt-bindings: clock: Add ESWIN eic7700 " dongxuyang
2026-04-05 7:24 ` Krzysztof Kozlowski
2026-04-03 9:36 ` [PATCH 2/3] clk: eswin: Add eic7700 HSP clock driver dongxuyang
2026-04-03 13:00 ` Benoît Monin
2026-04-03 14:00 ` Brian Masney [this message]
2026-04-14 2:36 ` Xuyang Dong
2026-04-03 9:36 ` [PATCH 3/3] reset: eswin: Add eic7700 HSP reset driver dongxuyang
2026-04-08 9:19 ` Philipp Zabel
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=ac_H7kSCgzz5HRxV@redhat.com \
--to=bmasney@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dongxuyang@eswincomputing.com \
--cc=huangyifeng@eswincomputing.com \
--cc=krzk+dt@kernel.org \
--cc=linmin@eswincomputing.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=ningyu@eswincomputing.com \
--cc=p.zabel@pengutronix.de \
--cc=pinkesh.vaghela@einfochips.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 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.