From: Harry Austen <hpausten@protonmail.com>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Michal Simek <michal.simek@amd.com>
Cc: Shubhrajyoti Datta <shubhrajyoti.datta@amd.com>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Harry Austen <hpausten@protonmail.com>
Subject: [PATCH v2 0/6] clk: clocking-wizard: modernize probe
Date: Fri, 13 Sep 2024 19:11:08 +0000 [thread overview]
Message-ID: <20240913191037.2690-1-hpausten@protonmail.com> (raw)
Improve utilised clk/notifier APIs, making use of device managed versions
of functions and make dynamic reconfiguration support optional (because it is
in hardware).
This is currently untested on hardware, so any help testing this would be
much appreciated!
This patchset is based on a previous one [1] ([PATCH v3 0/9] clk:
clocking-wizard: add user clock monitor support), whereby I was attempting to
add support for the user clock monitor functionality. Those three patches (DT
binding, clk driver and UIO driver) have now been removed, with the intention of
getting these simpler tidyup changes merged first, while reworking the design of
the user clock monitor support.
Changes from v1 [2]:
- Invert DT property (patch 5/6)
- Update driver with inverted DT property (patch 6/6)
[1] https://lore.kernel.org/20240826123602.1872-1-hpausten@protonmail.com
[2] https://lore.kernel.org/20240831111056.3864-1-hpausten@protonmail.com
Harry Austen (6):
clk: clocking-wizard: simplify probe/remove with devres helpers
clk: clocking-wizard: use newer clk_hw API
clk: clocking-wizard: use devres versions of clk_hw API
clk: clocking-wizard: move clock registration to separate function
dt-bindings: clock: xilinx: describe whether dynamic reconfig is
enabled
clk: clocking-wizard: move dynamic reconfig setup behind flag
.../bindings/clock/xlnx,clocking-wizard.yaml | 6 +
drivers/clk/xilinx/clk-xlnx-clock-wizard.c | 281 ++++++++----------
2 files changed, 127 insertions(+), 160 deletions(-)
--
2.46.0
next reply other threads:[~2024-09-13 19:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 19:11 Harry Austen [this message]
2024-09-13 19:11 ` [PATCH v2 1/6] clk: clocking-wizard: simplify probe/remove with devres helpers Harry Austen
2024-10-10 0:51 ` Stephen Boyd
2024-09-13 19:11 ` [PATCH v2 2/6] clk: clocking-wizard: use newer clk_hw API Harry Austen
2024-10-10 0:51 ` Stephen Boyd
2024-09-13 19:11 ` [PATCH v2 3/6] clk: clocking-wizard: use devres versions of " Harry Austen
2024-10-10 0:51 ` Stephen Boyd
2024-09-13 19:11 ` [PATCH v2 4/6] clk: clocking-wizard: move clock registration to separate function Harry Austen
2024-10-10 0:51 ` Stephen Boyd
2024-09-13 19:11 ` [PATCH v2 5/6] dt-bindings: clock: xilinx: describe whether dynamic reconfig is enabled Harry Austen
2024-09-16 14:47 ` Rob Herring (Arm)
2024-10-10 0:51 ` Stephen Boyd
2024-09-13 19:11 ` [PATCH v2 6/6] clk: clocking-wizard: move dynamic reconfig setup behind flag Harry Austen
2024-10-10 1:19 ` 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=20240913191037.2690-1-hpausten@protonmail.com \
--to=hpausten@protonmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=shubhrajyoti.datta@amd.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;
as well as URLs for NNTP newsgroup(s).