From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: <mturquette@baylibre.com>, <sboyd@kernel.org>, <robh+dt@kernel.org>
Cc: <nicolas.ferre@microchip.com>, <kavyasree.kotagiri@microchip.com>,
<eugen.hristev@microchip.com>, <linux-clk@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Horatiu Vultur <horatiu.vultur@microchip.com>
Subject: [RFC PATCH 0/3] Extend lan966x clock driver for clock gating support
Date: Tue, 19 Oct 2021 10:44:46 +0200 [thread overview]
Message-ID: <20211019084449.1411060-1-horatiu.vultur@microchip.com> (raw)
This patch series depends on the following series, therefor keep it as RFC.
https://www.spinics.net/lists/linux-clk/msg62237.html
This patch series extend the clock driver to support also clock gating.
Horatiu Vultur (3):
dt-bindings: clock: lan966x: Extend for clock gate support
dt-bindings: clock: lan966x: Extend includes with clock gates
clk: lan966x: Extend lan966x clock driver for clock gating support
.../bindings/clock/microchip,lan966x-gck.yaml | 13 +++-
drivers/clk/clk-lan966x.c | 72 +++++++++++++++++--
include/dt-bindings/clock/microchip,lan966x.h | 8 ++-
3 files changed, 86 insertions(+), 7 deletions(-)
--
2.33.0
next reply other threads:[~2021-10-19 8:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 8:44 Horatiu Vultur [this message]
2021-10-19 8:44 ` [RFC PATCH 1/3] dt-bindings: clock: lan966x: Extend for clock gate support Horatiu Vultur
2021-10-27 3:08 ` Rob Herring
2021-10-29 12:06 ` Horatiu Vultur
2021-10-19 8:44 ` [RFC PATCH 2/3] dt-bindings: clock: lan966x: Extend includes with clock gates Horatiu Vultur
2021-10-27 3:09 ` Rob Herring
2021-10-19 8:44 ` [RFC PATCH 3/3] clk: lan966x: Extend lan966x clock driver for clock gating support Horatiu Vultur
2021-10-29 6:41 ` Stephen Boyd
2021-10-29 9:35 ` Horatiu Vultur
2021-10-29 23:32 ` Stephen Boyd
2021-10-31 9:03 ` Horatiu Vultur
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=20211019084449.1411060-1-horatiu.vultur@microchip.com \
--to=horatiu.vultur@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=eugen.hristev@microchip.com \
--cc=kavyasree.kotagiri@microchip.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@kernel.org \
--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®