From: Stephen Boyd <sboyd@kernel.org>
To: Shengjiu Wang <shengjiu.wang@nxp.com>,
abelvesa@kernel.org, conor+dt@kernel.org, festevam@gmail.com,
kernel@pengutronix.de, krzysztof.kozlowski+dt@linaro.org,
linux-imx@nxp.com, mturquette@baylibre.com, peng.fan@nxp.com,
robh+dt@kernel.org, s.hauer@pengutronix.de, shawnguo@kernel.org,
shengjiu.wang@gmail.com
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 3/3] clk: imx: imx8: add audio clock mux driver
Date: Wed, 19 Jul 2023 13:17:02 -0700 [thread overview]
Message-ID: <ad757ed215d8f098472be370e3bbd961.sboyd@kernel.org> (raw)
In-Reply-To: <1689322259-13504-4-git-send-email-shengjiu.wang@nxp.com>
Quoting Shengjiu Wang (2023-07-14 01:10:59)
> diff --git a/drivers/clk/imx/clk-imx8-acm.c b/drivers/clk/imx/clk-imx8-acm.c
> new file mode 100644
> index 000000000000..445a0b38281c
> --- /dev/null
> +++ b/drivers/clk/imx/clk-imx8-acm.c
> @@ -0,0 +1,477 @@
> +// SPDX-License-Identifier: GPL-2.0+
> +//
> +// Copyright 2023 NXP
> +//
> +
> +#include <dt-bindings/clock/imx8-clock.h>
> +#include <linux/clk-provider.h>
> +#include <linux/device.h>
> +#include <linux/err.h>
> +#include <linux/io.h>
> +#include <linux/module.h>
> +#include <linux/of.h>
> +#include <linux/of_device.h>
> +#include <linux/platform_device.h>
> +#include <linux/pm_domain.h>
> +#include <linux/pm_runtime.h>
> +#include <linux/slab.h>
> +
> +#include "clk.h"
> +
> +/**
> + * struct clk_imx_acm_pm_domains: structure for multi power domain
> + * @pd_dev: power domain device
> + * @pd_dev_link: power domain device link
> + * @num_domains: power domain nummber
> + */
> +struct clk_imx_acm_pm_domains {
> + struct device **pd_dev;
> + struct device_link **pd_dev_link;
> + int num_domains;
> +};
> +
> +/**
> + * struct clk_imx8_acm_sel: for clock mux
> + * @name: clock name
> + * @clkid: clock id
> + * @parents: clock parents
> + * @num_parents: clock parents number
> + * @reg: register offset
> + * @shift: bit shift in register
> + * @width: bits width
> + */
> +struct clk_imx8_acm_sel {
> + const char *name;
> + int clkid;
> + const struct clk_parent_data *parents; /* For mux */
> + int num_parents;
> + u32 reg;
> + u8 shift;
> + u8 width;
> +};
> +
> +/**
> + * struct imx8_acm_soc_data: soc specific data
> + * @sels: pointer to struct clk_imx8_acm_sel
> + * @num_sels: numbers of items
> + */
> +struct imx8_acm_soc_data {
> + struct clk_imx8_acm_sel *sels;
> + unsigned int num_sels;
> +};
> +
> +/**
> + * struct imx8_acm_priv: private structure
Compile with W=1 and see that this isn't kerneldoc. Please fix.
> + * @dev_pm: multi power domain
> + * @soc_data: pointer to soc data
> + * @reg: base address of registers
> + * @regs: save registers for suspend
> + */
> +struct imx8_acm_priv {
> + struct clk_imx_acm_pm_domains dev_pm;
> + const struct imx8_acm_soc_data *soc_data;
> + void __iomem *reg;
> + u32 regs[IMX_ADMA_ACM_CLK_END];
> +};
> +
> +static const struct clk_parent_data imx8qm_aud_clk_sels[] = {
> + {.fw_name = "aud_rec_clk0_lpcg_clk", .name = "aud_rec_clk0_lpcg_clk" },
There should only be fw_name here, or use an index. Presumably this
isn't migrating old code or bindings. Also, please add space after { and
before }.
> + {.fw_name = "aud_rec_clk1_lpcg_clk", .name = "aud_rec_clk1_lpcg_clk" },
> + {.fw_name = "mlb_clk", .name = "mlb_clk" },
> + {.fw_name = "hdmi_rx_mclk", .name = "hdmi_rx_mclk" },
> + {.fw_name = "ext_aud_mclk0", .name = "ext_aud_mclk0" },
> + {.fw_name = "ext_aud_mclk1", .name = "ext_aud_mclk1" },
> + {.fw_name = "esai0_rx_clk", .name = "esai0_rx_clk" },
> + {.fw_name = "esai0_rx_hf_clk", .name = "esai0_rx_hf_clk" },
> + {.fw_name = "esai0_tx_clk", .name = "esai0_tx_clk" },
> + {.fw_name = "esai0_tx_hf_clk", .name = "esai0_tx_hf_clk" },
> + {.fw_name = "esai1_rx_clk", .name = "esai1_rx_clk" },
> + {.fw_name = "esai1_rx_hf_clk", .name = "esai1_rx_hf_clk" },
> + {.fw_name = "esai1_tx_clk", .name = "esai1_tx_clk" },
> + {.fw_name = "esai1_tx_hf_clk", .name = "esai1_tx_hf_clk" },
> + {.fw_name = "spdif0_rx", .name = "spdif0_rx" },
> + {.fw_name = "spdif1_rx", .name = "spdif1_rx" },
> + {.fw_name = "sai0_rx_bclk", .name = "sai0_rx_bclk" },
> + {.fw_name = "sai0_tx_bclk", .name = "sai0_tx_bclk" },
> + {.fw_name = "sai1_rx_bclk", .name = "sai1_rx_bclk" },
> + {.fw_name = "sai1_tx_bclk", .name = "sai1_tx_bclk" },
> + {.fw_name = "sai2_rx_bclk", .name = "sai2_rx_bclk" },
> + {.fw_name = "sai3_rx_bclk", .name = "sai3_rx_bclk" },
> + {.fw_name = "sai4_rx_bclk", .name = "sai4_rx_bclk" },
> +};
[...]
> +
> +static const struct clk_parent_data imx8dxl_mclk_out_sels[] = {
> + {.fw_name = "aud_rec_clk0_lpcg_clk", .name = "aud_rec_clk0_lpcg_clk" },
> + {.fw_name = "aud_rec_clk1_lpcg_clk", .name = "aud_rec_clk1_lpcg_clk" },
> + {.name = "dummy" },
> + {.name = "dummy" },
> + {.fw_name = "spdif0_rx", .name = "spdif0_rx" },
> + {.name = "dummy" },
> + {.name = "dummy" },
> + {.name = "dummy" },
Instead of dummy can you use -1 as the index?
next prev parent reply other threads:[~2023-07-19 20:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 8:10 [PATCH v5 0/3] clk: imx: add audio clock mux driver Shengjiu Wang
2023-07-14 8:10 ` [PATCH v5 1/3] dt-bindings: clock: fsl,imx8-acm: Add audio clock mux support Shengjiu Wang
2023-07-14 8:10 ` [PATCH v5 2/3] dt-bindings: clock: imx8-clock: Add audio clock mux related clock Shengjiu Wang
2023-07-14 8:10 ` [PATCH v5 3/3] clk: imx: imx8: add audio clock mux driver Shengjiu Wang
2023-07-18 7:14 ` Peng Fan
2023-07-19 20:17 ` Stephen Boyd [this message]
[not found] ` <CAA+D8APd3n8XvC3m5fAoPxqqLzaU-RKm+e9y_G++D6KdaJJhiQ@mail.gmail.com>
2023-07-20 18:21 ` Stephen Boyd
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=ad757ed215d8f098472be370e3bbd961.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=abelvesa@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=shengjiu.wang@gmail.com \
--cc=shengjiu.wang@nxp.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;
as well as URLs for NNTP newsgroup(s).