public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tretter <m.tretter@pengutronix.de>
To: Amit Sunil Dhamne <amit.sunil.dhamne@xilinx.com>
Cc: mturquette@baylibre.com, sboyd@codeaurora.org, sboyd@kernel.org,
	michal.simek@xilinx.com, mark.rutland@arm.com,
	linux-clk@vger.kernel.org, rajanv@xilinx.com, jollys@xilinx.com,
	tejasp@xilinx.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Rajan Vaja <rajan.vaja@xilinx.com>,
	Tejas Patel <tejas.patel@xilinx.com>
Subject: Re: [PATCH v2 2/3] clk: zynqmp: Use firmware specific divider clock flags
Date: Wed, 22 Jul 2020 15:27:08 +0200	[thread overview]
Message-ID: <20200722132708.GD21264@pengutronix.de> (raw)
In-Reply-To: <1595400932-303612-3-git-send-email-amit.sunil.dhamne@xilinx.com>

On Tue, 21 Jul 2020 23:55:31 -0700, Amit Sunil Dhamne wrote:
> From: Rajan Vaja <rajan.vaja@xilinx.com>
> 
> Use ZynqMP specific divider clock flags instead of using CCF flags.
> 
> Signed-off-by: Rajan Vaja <rajan.vaja@xilinx.com>
> Signed-off-by: Tejas Patel <tejas.patel@xilinx.com>
> Signed-off-by: Amit Sunil Dhamne <amit.sunil.dhamne@xilinx.com>
> ---
>  drivers/clk/zynqmp/clk-zynqmp.h |  9 +++++++++
>  drivers/clk/zynqmp/divider.c    | 16 +++++++++++++++-
>  2 files changed, 24 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/clk/zynqmp/clk-zynqmp.h b/drivers/clk/zynqmp/clk-zynqmp.h
> index 3cb6149..ec33525 100644
> --- a/drivers/clk/zynqmp/clk-zynqmp.h
> +++ b/drivers/clk/zynqmp/clk-zynqmp.h
> @@ -32,6 +32,15 @@
>  /* do not gate, ever */
>  #define ZYNQMP_CLK_IS_CRITICAL         BIT(11)
> 
> +/* Type Flags for divider clock */
> +#define ZYNQMP_CLK_DIVIDER_ONE_BASED           BIT(0)
> +#define ZYNQMP_CLK_DIVIDER_POWER_OF_TWO                BIT(1)
> +#define ZYNQMP_CLK_DIVIDER_ALLOW_ZERO          BIT(2)
> +#define ZYNQMP_CLK_DIVIDER_HIWORD_MASK         BIT(3)
> +#define ZYNQMP_CLK_DIVIDER_ROUND_CLOSEST       BIT(4)
> +#define ZYNQMP_CLK_DIVIDER_READ_ONLY           BIT(5)
> +#define ZYNQMP_CLK_DIVIDER_MAX_AT_ZERO         BIT(6)
> +
>  enum topology_type {
>         TYPE_INVALID,
>         TYPE_MUX,
> diff --git a/drivers/clk/zynqmp/divider.c b/drivers/clk/zynqmp/divider.c
> index 3ab57d9..86cb785 100644
> --- a/drivers/clk/zynqmp/divider.c
> +++ b/drivers/clk/zynqmp/divider.c
> @@ -320,7 +320,21 @@ struct clk_hw *zynqmp_clk_register_divider(const char *name,
>         /* struct clk_divider assignments */
>         div->is_frac = !!((nodes->flag & CLK_FRAC) |
>                           (nodes->custom_type_flag & CUSTOM_FLAG_CLK_FRAC));
> -       div->flags = nodes->type_flag;
> +       div->flags = 0;
> +       div->flags |= (nodes->type_flag & ZYNQMP_CLK_DIVIDER_ONE_BASED) ?
> +                     CLK_DIVIDER_ONE_BASED : 0;
> +       div->flags |= (nodes->type_flag & ZYNQMP_CLK_DIVIDER_POWER_OF_TWO) ?
> +                     CLK_DIVIDER_POWER_OF_TWO : 0;
> +       div->flags |= (nodes->type_flag & ZYNQMP_CLK_DIVIDER_ALLOW_ZERO) ?
> +                     CLK_DIVIDER_ALLOW_ZERO : 0;
> +       div->flags |= (nodes->type_flag & ZYNQMP_CLK_DIVIDER_POWER_OF_TWO) ?
> +                     CLK_DIVIDER_HIWORD_MASK : 0;
> +       div->flags |= (nodes->type_flag & ZYNQMP_CLK_DIVIDER_ROUND_CLOSEST) ?
> +                     CLK_DIVIDER_ROUND_CLOSEST : 0;
> +       div->flags |= (nodes->type_flag & ZYNQMP_CLK_DIVIDER_READ_ONLY) ?
> +                     CLK_DIVIDER_READ_ONLY : 0;
> +       div->flags |= (nodes->type_flag & ZYNQMP_CLK_DIVIDER_MAX_AT_ZERO) ?
> +                     CLK_DIVIDER_MAX_AT_ZERO : 0;

Add a helper function for converting the flags.

Michael

>         div->hw.init = &init;
>         div->clk_id = clk_id;
>         div->div_type = nodes->type;
> --
> 2.7.4
> 
> This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
> 

  reply	other threads:[~2020-07-22 13:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-22  6:55 [PATCH v2 0/3] clk: zynqmp: Add firmware specific clock flags Amit Sunil Dhamne
2020-07-22  6:55 ` [PATCH v2 1/3] clk: zynqmp: Use firmware specific common " Amit Sunil Dhamne
2020-07-22 13:22   ` Michael Tretter
2020-07-23 23:46     ` Amit Sunil Dhamne
2020-07-22  6:55 ` [PATCH v2 2/3] clk: zynqmp: Use firmware specific divider " Amit Sunil Dhamne
2020-07-22 13:27   ` Michael Tretter [this message]
2020-07-23 23:59     ` Amit Sunil Dhamne
2020-07-22  6:55 ` [PATCH v2 3/3] clk: zynqmp: Use firmware specific mux " Amit Sunil Dhamne
2020-07-22 13:28   ` Michael Tretter
2020-07-23 22:35 ` [PATCH v2 0/3] clk: zynqmp: Add firmware specific " 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=20200722132708.GD21264@pengutronix.de \
    --to=m.tretter@pengutronix.de \
    --cc=amit.sunil.dhamne@xilinx.com \
    --cc=jollys@xilinx.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=michal.simek@xilinx.com \
    --cc=mturquette@baylibre.com \
    --cc=rajan.vaja@xilinx.com \
    --cc=rajanv@xilinx.com \
    --cc=sboyd@codeaurora.org \
    --cc=sboyd@kernel.org \
    --cc=tejas.patel@xilinx.com \
    --cc=tejasp@xilinx.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