From: Abel Vesa <abel.vesa@nxp.com>
To: Jacky Bai <ping.bai@nxp.com>
Cc: shawnguo@kernel.org, robh+dt@kernel.org, sboyd@kernel.org,
s.hauer@pengutronix.de, p.zabel@pengutronix.de,
kernel@pengutronix.de, linux-imx@nxp.com,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 9/9] clk: imx: Add the pcc reset controller support on imx8ulp
Date: Tue, 14 Sep 2021 15:09:42 +0300 [thread overview]
Message-ID: <YUCRBtdgDMs3WeQk@ryzen> (raw)
In-Reply-To: <20210914065208.3582128-10-ping.bai@nxp.com>
On 21-09-14 14:52:08, Jacky Bai wrote:
> diff --git a/drivers/clk/imx/clk-imx8ulp.c b/drivers/clk/imx/clk-imx8ulp.c
> index 6aad04114658..6699437e17b8 100644
> --- a/drivers/clk/imx/clk-imx8ulp.c
> +++ b/drivers/clk/imx/clk-imx8ulp.c
> @@ -9,6 +9,7 @@
> #include <linux/module.h>
> #include <linux/of_device.h>
> #include <linux/platform_device.h>
> +#include <linux/reset-controller.h>
> #include <linux/slab.h>
>
> #include "clk.h"
> @@ -48,6 +49,99 @@ static const char * const nic_per_divplat[] = { "nic_per_divplat" };
> static const char * const lpav_axi_div[] = { "lpav_axi_div" };
> static const char * const lpav_bus_div[] = { "lpav_bus_div" };
>
> +struct pcc_reset_dev {
> + void __iomem *base;
> + struct reset_controller_dev rcdev;
> + const u32 *resets;
> + /* Set to imx_ccm_lock to protect register access shared with clock control */
> + spinlock_t *lock;
> +};
> +
> +#define PCC_SW_RST BIT(28)
> +#define to_pcc_reset_dev(_rcdev) container_of(_rcdev, struct pcc_reset_dev, rcdev)
> +
> +static const u32 pcc3_resets[] = {
> + 0xa8, 0xac, 0xc8, 0xcc, 0xd0,
> + 0xd4, 0xd8, 0xdc, 0xe0, 0xe4,
> + 0xe8, 0xec, 0xf0
> +};
> +
> +static const u32 pcc4_resets[] = {
> + 0x4, 0x8, 0xc, 0x10, 0x14,
> + 0x18, 0x1c, 0x20, 0x24, 0x34,
> + 0x38, 0x3c, 0x40, 0x44, 0x48,
> + 0x4c, 0x54
> +};
> +
> +static const u32 pcc5_resets[] = {
> + 0xa0, 0xa4, 0xa8, 0xac, 0xb0,
> + 0xb4, 0xbc, 0xc0, 0xc8, 0xcc,
> + 0xd0, 0xf0, 0xf4, 0xf8
> +};
> +
I believe this could be avoided entirely by having something like:
PCCx_RESETS_OFFSET + (index * 4)
and then:
#define PCC3_RESETS_OFFSET 0xa8
#define PCC4_RESETS_OFFSET 0x4
#define PCC5_RESETS_OFFSET 0xa0
#define PCC3_RESETS_NUM 13
#define PCC4_RESETS_NUM 17
#define PCC5_RESETS_NUM 14
Then we could pass on the PCCx_RESETS_OFFSET and the PCCx_RESETS_NUM and
that's it.
> +static int imx8ulp_pcc_assert(struct reset_controller_dev *rcdev, unsigned long id)
> +{
> + struct pcc_reset_dev *pcc_reset = to_pcc_reset_dev(rcdev);
> + u32 offset = pcc_reset->resets[id];
> + unsigned long flags;
> + u32 val;
> +
> + spin_lock_irqsave(pcc_reset->lock, flags);
> +
> + val = readl(pcc_reset->base + offset);
> + val &= ~PCC_SW_RST;
> + writel(val, pcc_reset->base + offset);
> +
> + spin_unlock_irqrestore(pcc_reset->lock, flags);
> +
> + return 0;
> +}
> +
> +static int imx8ulp_pcc_deassert(struct reset_controller_dev *rcdev, unsigned long id)
> +{
> + struct pcc_reset_dev *pcc_reset = to_pcc_reset_dev(rcdev);
> + u32 offset = pcc_reset->resets[id];
> + unsigned long flags;
> + u32 val;
> +
> + spin_lock_irqsave(pcc_reset->lock, flags);
> +
> + val = readl(pcc_reset->base + offset);
> + val |= PCC_SW_RST;
> + writel(val, pcc_reset->base + offset);
> +
> + spin_unlock_irqrestore(pcc_reset->lock, flags);
> +
> + return 0;
> +}
> +
> +static const struct reset_control_ops imx8ulp_pcc_reset_ops = {
> + .assert = imx8ulp_pcc_assert,
> + .deassert = imx8ulp_pcc_deassert,
> +};
> +
> +static int imx8ulp_pcc_reset_init(struct platform_device *pdev, void __iomem *base,
> + const u32 *resets, unsigned int nr_resets)
> +{
> + struct device_node *np = pdev->dev.of_node;
> + struct device *dev = &pdev->dev;
> + struct pcc_reset_dev *pcc_reset;
> +
> + pcc_reset = devm_kzalloc(dev, sizeof(*pcc_reset), GFP_KERNEL);
> + if (!pcc_reset)
> + return -ENOMEM;
> +
> + pcc_reset->base = base;
> + pcc_reset->lock = &imx_ccm_lock;
> + pcc_reset->resets = resets;
> + pcc_reset->rcdev.owner = THIS_MODULE;
> + pcc_reset->rcdev.nr_resets = nr_resets;
> + pcc_reset->rcdev.ops = &imx8ulp_pcc_reset_ops;
> + pcc_reset->rcdev.of_node = np;
> +
> + return devm_reset_controller_register(dev, &pcc_reset->rcdev);
> +}
> +
...
> --
> 2.26.2
>
next prev parent reply other threads:[~2021-09-14 12:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 6:51 [PATCH v3 0/9] Add imx8ulp clock & reset driver support Jacky Bai
2021-09-14 6:52 ` [PATCH v3 1/9] dt-bindings: clock: Add imx8ulp clock support Jacky Bai
2021-09-14 11:25 ` Abel Vesa
2021-09-14 13:11 ` Jacky Bai
2021-09-14 15:30 ` Abel Vesa
2021-09-20 21:44 ` Rob Herring
2021-09-14 6:52 ` [PATCH v3 2/9] clk: imx: Update the pllv4 to support imx8ulp Jacky Bai
2021-09-14 11:29 ` Abel Vesa
2021-09-14 6:52 ` [PATCH v3 3/9] clk: imx: Update the compsite driver " Jacky Bai
2021-09-14 11:30 ` Abel Vesa
2021-09-14 6:52 ` [PATCH v3 4/9] clk: imx: disable i.mx7ulp composite clock during initialization Jacky Bai
2021-09-14 11:32 ` Abel Vesa
2021-09-14 6:52 ` [PATCH v3 5/9] clk: imx: Add 'CLK_SET_RATE_NO_REPARENT' for composite-7ulp Jacky Bai
2021-09-14 11:33 ` Abel Vesa
2021-09-14 6:52 ` [PATCH v3 6/9] clk: imx: disable the pfd when set pfdv2 clock rate Jacky Bai
2021-09-14 11:34 ` Abel Vesa
2021-09-14 6:52 ` [PATCH v3 7/9] clk: imx: Update the pfdv2 for 8ulp specific support Jacky Bai
2021-09-14 11:35 ` Abel Vesa
2021-09-14 6:52 ` [PATCH v3 8/9] clk: imx: Add clock driver for imx8ulp Jacky Bai
2021-09-14 11:55 ` Abel Vesa
2021-09-14 6:52 ` [PATCH v3 9/9] clk: imx: Add the pcc reset controller support on imx8ulp Jacky Bai
2021-09-14 12:09 ` Abel Vesa [this message]
2021-09-14 13:07 ` Jacky Bai
2021-09-14 15:19 ` Abel Vesa
2021-09-14 11:17 ` [PATCH v3 0/9] Add imx8ulp clock & reset driver support Abel Vesa
2021-09-16 6:46 ` Abel Vesa
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=YUCRBtdgDMs3WeQk@ryzen \
--to=abel.vesa@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-imx@nxp.com \
--cc=p.zabel@pengutronix.de \
--cc=ping.bai@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@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).