On 25/07/2025 10:22, Suzuki K Poulose wrote:
On Thu, 24 Jul 2025 16:22:30 +0100, Leo Yan wrote:
This series fixes and improves clock usage in the Arm CoreSight drivers.
Based on the DT binding documents, the trace clock (atclk) is defined in some CoreSight modules, but support is absent. In most cases, the issue is hidden because the atclk clock is shared by multiple CoreSight modules and the clock is enabled anyway by other drivers. The first three patches address this issue.
[...]
Applied, thanks!
[01/10] coresight: tmc: Support atclk https://git.kernel.org/coresight/c/e96d605a66ff [02/10] coresight: catu: Support atclk https://git.kernel.org/coresight/c/7eca4399060d [03/10] coresight: etm4x: Support atclk https://git.kernel.org/coresight/c/14fb833b8204 [04/10] coresight: Appropriately disable programming clocks https://git.kernel.org/coresight/c/ce15ee28bddd [05/10] coresight: Appropriately disable trace bus clocks https://git.kernel.org/coresight/c/90b0000bd501 [06/10] coresight: Avoid enable programming clock duplicately https://git.kernel.org/coresight/c/5c0ead76597b [07/10] coresight: Consolidate clock enabling https://git.kernel.org/coresight/c/f47d7f7da638 [08/10] coresight: Refactor driver data allocation https://git.kernel.org/coresight/c/7471c81e60b9 [09/10] coresight: Make clock sequence consistent https://git.kernel.org/coresight/c/d4cf59aa905b [10/10] coresight: Refactor runtime PM https://git.kernel.org/coresight/c/2b52cf338d39
Best regards,
I have dropped this from -next, due to the issues reported by Mark.
Suzuki