public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Harry Austen <hpausten@protonmail.com>,
	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>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Shubhrajyoti Datta <shubhrajyoti.datta@amd.com>,
	Dave Ertman <david.m.ertman@intel.com>,
	Ira Weiny <ira.weiny@intel.com>,
	linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/9] clk: clocking-wizard: add user clock monitor support
Date: Sun, 4 Aug 2024 15:58:05 +0200	[thread overview]
Message-ID: <1f60e4d1-ee8a-47fc-8fad-a75ec6485a28@kernel.org> (raw)
In-Reply-To: <D374LM180ETW.M8ESN44FLCVX@protonmail.com>

On 04/08/2024 14:28, Harry Austen wrote:
> On Sun Aug 4, 2024 at 10:01 AM BST, Krzysztof Kozlowski wrote:
>> On 03/08/2024 12:57, Harry Austen wrote:
>>> Improve utilised clk/notifier APIs, making use of device managed versions
>>> of functions, make dynamic reconfiguration support optional (because it is
>>> in hardware) and add support for the clock monitor functionailty added in
>>> version 6.0 of the Xilinx clocking wizard IP core, through use of the
>>> auxiliary bus and UIO frameworks.
>>>
>>> The combined addition of all of these patches allows, for example, to use
>>> the clocking wizard solely for its user clock monitoring logic, keeping
>>> dynamic reconfiguration support disabled.
>>>
>>> This is currently untested on hardware, so any help testing this would be
>>> much appreciated!
>>>
>>> v1 -> v2:
>>> - Split and improve clk_hw+devres transition patch (2+3)
>>> - Fix/improve DT binding patches (5+8)
>>
>> Be specific, what did you change? Anything can be a fix or improvement.
> 
> This was intended as more of a summary, referencing the patches which have
> their own more detailed changelogs. But I will be more descriptive in the
> cover letter too in future.

No, if more descriptive changelog is in each patch, then it is fine.

Best regards,
Krzysztof


      reply	other threads:[~2024-08-04 13:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-03 10:57 [PATCH v2 0/9] clk: clocking-wizard: add user clock monitor support Harry Austen
2024-08-03 10:57 ` [PATCH v2 1/9] clk: clocking-wizard: simplify probe/remove with devres helpers Harry Austen
2024-08-03 10:57 ` [PATCH v2 2/9] clk: clocking-wizard: use newer clk_hw API Harry Austen
2024-08-04 12:27   ` Harry Austen
2024-08-03 10:58 ` [PATCH v2 3/9] clk: clocking-wizard: use devres versions of " Harry Austen
2024-08-03 10:58 ` [PATCH v2 4/9] clk: clocking-wizard: move clock registration to separate function Harry Austen
2024-08-03 10:58 ` [PATCH v2 5/9] dt-bindings: clock: xilinx: add description of user monitor interrupt Harry Austen
2024-08-04  9:04   ` Krzysztof Kozlowski
2024-08-04 12:30     ` Harry Austen
2024-08-03 10:58 ` [PATCH v2 6/9] clk: clocking-wizard: add user clock monitor support Harry Austen
2024-08-19 12:39   ` Datta, Shubhrajyoti
2024-08-20 18:30     ` Harry Austen
2024-08-03 10:58 ` [PATCH v2 7/9] uio: add Xilinx " Harry Austen
2024-08-03 10:58 ` [PATCH v2 8/9] dt-bindings: clock: xilinx: describe whether dynamic reconfig is enabled Harry Austen
2024-08-04  9:04   ` Krzysztof Kozlowski
2024-08-03 10:58 ` [PATCH v2 9/9] clk: clocking-wizard: move dynamic reconfig setup behind flag Harry Austen
2024-08-04  9:01 ` [PATCH v2 0/9] clk: clocking-wizard: add user clock monitor support Krzysztof Kozlowski
2024-08-04 12:28   ` Harry Austen
2024-08-04 13:58     ` Krzysztof Kozlowski [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=1f60e4d1-ee8a-47fc-8fad-a75ec6485a28@kernel.org \
    --to=krzk@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=david.m.ertman@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpausten@protonmail.com \
    --cc=ira.weiny@intel.com \
    --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