From: Jolly Shah <jolly.shah@xilinx.com>
To: olof@lixom.net, mturquette@baylibre.com, sboyd@kernel.org,
michal.simek@xilinx.com, arm@kernel.org,
linux-clk@vger.kernel.org
Cc: Jolly Shah <jolly.shah@xilinx.com>,
rajanv@xilinx.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] drivers: clk: zynqmp: Update fraction clock check from custom type flags
Date: Thu, 12 Mar 2020 14:31:37 -0700 [thread overview]
Message-ID: <1584048699-24186-1-git-send-email-jolly.shah@xilinx.com> (raw)
This patch series adds support for custom type flags passed from
firmware. It also update fraction clock check from custom type
flags since new firmware pass CLK_FRAC flag as a part of custom flags
instead of clkflags as CLK_FRAC is not common clock framework flag.
This patch series maintains backward compatibility with older version
of firmware.
v2:
-PATCH[2/2] Correct BIT index of CLK_FRAC in custom_type_flag
Rajan Vaja (1):
drivers: clk: zynqmp: Add support for custom type flags
Tejas Patel (1):
drivers: clk: zynqmp: Update fraction clock check from custom type
flags
drivers/clk/zynqmp/clk-zynqmp.h | 1 +
drivers/clk/zynqmp/clkc.c | 4 ++++
drivers/clk/zynqmp/divider.c | 6 ++++--
3 files changed, 9 insertions(+), 2 deletions(-)
--
2.7.4
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-03-12 21:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 21:31 Jolly Shah [this message]
2020-03-12 21:31 ` [PATCH v2 1/2] drivers: clk: zynqmp: Add support for custom type flags Jolly Shah
2020-05-27 1:01 ` Stephen Boyd
2020-03-12 21:31 ` [PATCH v2 2/2] drivers: clk: zynqmp: Update fraction clock check from " Jolly Shah
2020-05-27 1:01 ` Stephen Boyd
2020-05-27 1:08 ` Stephen Boyd
2020-05-28 17:44 ` Jolly Shah
2020-05-28 23:12 ` Stephen Boyd
2020-05-29 21:20 ` Jolly Shah
2020-03-23 21:15 ` [PATCH v2 0/2] " Jolly Shah
2020-04-09 20:48 ` Jolly Shah
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=1584048699-24186-1-git-send-email-jolly.shah@xilinx.com \
--to=jolly.shah@xilinx.com \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=mturquette@baylibre.com \
--cc=olof@lixom.net \
--cc=rajanv@xilinx.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