mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Amit Sunil Dhamne <amitsuni@xilinx.com>
To: Amit Sunil Dhamne <amitsuni@xilinx.com>,
	"mturquette@baylibre.com" <mturquette@baylibre.com>,
	"m.tretter@pengutronix.de" <m.tretter@pengutronix.de>,
	"sboyd@kernel.org" <sboyd@kernel.org>,
	Michal Simek <michals@xilinx.com>,
	"mark.rutland@arm.com" <mark.rutland@arm.com>,
	"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>
Cc: Rajan Vaja <RAJANV@xilinx.com>, Jolly Shah <JOLLYS@xilinx.com>,
	Tejas Patel <TEJASP@xilinx.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v3 0/3] clk: zynqmp: Add firmware specific clock flags
Date: Mon, 10 Aug 2020 22:06:13 +0000	[thread overview]
Message-ID: <BYAPR02MB562261B10DBF08A58FF066B2A7440@BYAPR02MB5622.namprd02.prod.outlook.com> (raw)
In-Reply-To: <1596523457-40465-1-git-send-email-amit.sunil.dhamne@xilinx.com>

Hi Stephen, Reviewers,
I wanted to gently follow up on the review of this patch.

Thanks,
Amit

> -----Original Message-----
> From: Amit Sunil Dhamne <amit.sunil.dhamne@xilinx.com>
> Sent: Monday, August 3, 2020 11:44 PM
> To: mturquette@baylibre.com; m.tretter@pengutronix.de;
> sboyd@kernel.org; Michal Simek <michals@xilinx.com>;
> mark.rutland@arm.com; linux-clk@vger.kernel.org
> Cc: Rajan Vaja <RAJANV@xilinx.com>; Jolly Shah <JOLLYS@xilinx.com>; Tejas
> Patel <TEJASP@xilinx.com>; linux-arm-kernel@lists.infradead.org; linux-
> kernel@vger.kernel.org; Amit Sunil Dhamne <amitsuni@xilinx.com>
> Subject: [PATCH v3 0/3] clk: zynqmp: Add firmware specific clock flags
> 
> Currently firmware is maintaining CCF specific flags and provides to CCF as it
> is. But CCF flag numbers may change and that shouldn't mean that the
> firmware needs to change. The firmware should have its own 'flag number
> space' that is distinct from the common clk framework's 'flag number space'.
> So use firmware specific clock flags in ZynqMP clock driver instead of CCF
> flags.
> 
> Changes in v3:
>  - Modify helper function signature to map zynqmp (common)flags with CCF
>  - Add helper function to map zynqmp (mux & divider)flags with CCF flags
> 
> Changes in v2:
>  - Add helper function to map zynqmp (common)flags with CCF flags.
>  - Mapped zynqmp clock flags with CCF flags from
>    zynqmp_clk_register_*() functions instead of
>    __zynqmp_clock_get_topology() which is changing the flags to struct
>    clk_init_data instead of the struct clock_topology.
> 
> Rajan Vaja (3):
>   clk: zynqmp: Use firmware specific common clock flags
>   clk: zynqmp: Use firmware specific divider clock flags
>   clk: zynqmp: Use firmware specific mux clock flags
> 
>  drivers/clk/zynqmp/clk-gate-zynqmp.c |  4 +++-  drivers/clk/zynqmp/clk-
> mux-zynqmp.c  | 26 +++++++++++++++++++++--
>  drivers/clk/zynqmp/clk-zynqmp.h      | 41
> ++++++++++++++++++++++++++++++++++++
>  drivers/clk/zynqmp/clkc.c            | 32 +++++++++++++++++++++++++++-
>  drivers/clk/zynqmp/divider.c         | 29 ++++++++++++++++++++++---
>  drivers/clk/zynqmp/pll.c             |  4 +++-
>  6 files changed, 128 insertions(+), 8 deletions(-)
> 
> --
> 2.7.4


      parent reply	other threads:[~2020-08-10 22:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-04  6:44 Amit Sunil Dhamne
2020-08-04  6:44 ` [PATCH v3 1/3] clk: zynqmp: Use firmware specific common " Amit Sunil Dhamne
2020-08-13 20:09   ` Stephen Boyd
2020-08-04  6:44 ` [PATCH v3 2/3] clk: zynqmp: Use firmware specific divider " Amit Sunil Dhamne
2020-08-04  6:44 ` [PATCH v3 3/3] clk: zynqmp: Use firmware specific mux " Amit Sunil Dhamne
2020-08-10 22:06 ` Amit Sunil Dhamne [this message]

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=BYAPR02MB562261B10DBF08A58FF066B2A7440@BYAPR02MB5622.namprd02.prod.outlook.com \
    --to=amitsuni@xilinx.com \
    --cc=JOLLYS@xilinx.com \
    --cc=RAJANV@xilinx.com \
    --cc=TEJASP@xilinx.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.tretter@pengutronix.de \
    --cc=mark.rutland@arm.com \
    --cc=michals@xilinx.com \
    --cc=mturquette@baylibre.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®