Re: [PATCH v3 0/2] Add Clocks for ICSSG

From: MD Danish Anwar
Date: Mon Dec 16 2024 - 05:23:44 EST


Hi Vignesh / Nishant

On 13/11/24 4:39 pm, MD Danish Anwar wrote:
> This series adds clocks for ICSSG for AM64x.
>
> PATCH 1/2 Adds the dt binding necessary to add clocks to the device tree.
> It adds the `clocks` in the dt binding of ICSSG node. Each ICSSG instance
> has 7 clocks available to them as per AM64x TRM [1] Section 6.4.3 Table
> 6-398. They are not added in the dt bindings yet. This patch adds all
> available clocks to ICSSG bindings.
>
> PATCH 2/2 Adds the required clock to the ICSSG nodes. It also changes the
> clock used from clock 20 (ICSSG_ICLK) to clock 0 (ICSSG_CORE). This patch
> adds the clock-names, assigned-clocks and assigned-clock-parents to icssg
> nodes.
>
> More details on clocks can be found at [2]
> There is no additional driver changes needed for this binding change.
>
> Changes from v2 to v3:
> *) Modified commit message of PATCH 1/2 to state why clocks are being added
> to the binding.
> *) Added all available clocks to ICSSG bindings. Earlier only two clocks
> were added.
> *) Added all available clocks to AM64x DTS. Earlier only two clocks were
> added.
>
> Changes from v1 to v2:
> *) Dropped assigned-clocks and assigned-clock-parents from DT binding as
> suggested by Krzysztof Kozlowski
>
> [1] https://www.ti.com/lit/pdf/spruim2
> [2] https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/am64x/clocks.html#clocks-for-pru-icssg0-device
> v1 https://lore.kernel.org/all/20241107104557.1442800-1-danishanwar@xxxxxx/
> v2 https://lore.kernel.org/all/20241108142946.2286098-1-danishanwar@xxxxxx/
>
> MD Danish Anwar (2):
> dt-bindings: soc: ti: pruss: Add clocks for ICSSG
> arm64: dts: ti: k3-am64-main: Switch ICSSG clock to core clock
>
> .../devicetree/bindings/soc/ti/ti,pruss.yaml | 10 +++++++++
> arch/arm64/boot/dts/ti/k3-am64-main.dtsi | 22 +++++++++++++++++--
> 2 files changed, 30 insertions(+), 2 deletions(-)
>
>
> base-commit: bd05b9a700c10473c2f52bf12c5c5938c30e80b0

This series still applies cleanly on latest linux-next (next-20241216)
and doesn't need a re-base.

Can you please pick this.


--
Thanks and Regards,
Danish