From: jbrunet@baylibre.com (Jerome Brunet)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] clk: meson-axg: add clocks required by pcie driver
Date: Tue, 03 Jul 2018 11:24:22 +0200 [thread overview]
Message-ID: <1530609862.2900.187.camel@baylibre.com> (raw)
In-Reply-To: <20180702213118.19222-3-yixun.lan@amlogic.com>
On Mon, 2018-07-02 at 21:31 +0000, Yixun Lan wrote:
> Adding clocks for the pcie driver. Due to the ASIC design,
> the pcie controller re-use part of the mipi clock logic,
> so the mipi clock is also added.
>
> Tested-by: Jianxin Qin <jianxin.qin@amlogic.com>
> Signed-off-by: Yixun Lan <yixun.lan@amlogic.com>
> ---
> drivers/clk/meson/axg.c | 148 ++++++++++++++++++++++++++++++++++++++++
> drivers/clk/meson/axg.h | 6 +-
> 2 files changed, 153 insertions(+), 1 deletion(-)
>
>
[...]
> +
> +/* skip the partent 0, it's for debug only */
> +static u32 mux_table_pcie_ref[] = { 1 };
> +static const char * const pcie_ref_parent_names[] = { "pcie_mux" };
Dropped these symbols.
> +
> +static struct clk_regmap axg_pcie_ref = {
> + .data = &(struct clk_regmap_mux_data){
> + .offset = HHI_PCIE_PLL_CNTL6,
> + .mask = 0x1,
> + .shift = 1,
> + .table = mux_table_pcie_ref,
Replaced with the table itself
> + },
> + .hw.init = &(struct clk_init_data){
> + .name = "pcie_ref",
> + .ops = &clk_regmap_mux_ops,
> + .parent_names = pcie_ref_parent_names,
> + .num_parents = ARRAY_SIZE(pcie_ref_parent_names),
Replaced with the table itself and applied. Thx
> + .flags = CLK_SET_RATE_PARENT,
> + },
> +};
> +
>
next prev parent reply other threads:[~2018-07-03 9:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 21:31 [PATCH v2 0/2] clk: meson-axg: add pcie related clocks Yixun Lan
2018-07-02 21:31 ` [PATCH v2 1/2] clk: meson-axg: add pcie and mipi clock bindings Yixun Lan
2018-07-03 9:20 ` Jerome Brunet
2018-07-02 21:31 ` [PATCH v2 2/2] clk: meson-axg: add clocks required by pcie driver Yixun Lan
2018-07-03 9:24 ` Jerome Brunet [this message]
2018-07-03 10:17 ` Yixun Lan
2018-07-03 11:01 ` Jerome Brunet
2018-07-03 14:05 ` Yixun Lan
2018-07-03 14:42 ` Jerome Brunet
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=1530609862.2900.187.camel@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.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).