From: Bryan Brattlof <bb@ti.com>
To: Judith Mendez <jm@ti.com>
Cc: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Moteen Shah <m-shah@ti.com>, Udit Kumar <u-kumar1@ti.com>
Subject: Re: [PATCH v2 0/3] Set eMMC clock parent to default
Date: Tue, 29 Apr 2025 13:22:44 -0500 [thread overview]
Message-ID: <20250429182244.vm2atpuvmdfhtmlc@bryanbrattlof.com> (raw)
In-Reply-To: <20250429163337.15634-1-jm@ti.com>
On April 29, 2025 thus sayeth Judith Mendez:
> This series was split-off from "Misc MMC updates" patch series [0] and the
> original patch further divided into three to help with backporting as per
> review comments [1].
>
> This series sets clock parent for eMMC to the default clock parent
> MAIN_PLL0_HSDIV5_CLKOUT for am62, am62a, & am62p/j722s SoCs. Software (DM)
> does not switch MMC clock parent correctly as per the Arasan IP requirement
> to hold the IP in reset while clock source is switched. Since muxes to
> switch clock parent are not glitch-free and the default parent is tested
> and working fine, switch to the default as a preventative action.
>
> Changes since v1:
> - split original patch into three
> - add cover-letter
> - reword patch descriptions
> - add review tags
>
Acked-by: Bryan Brattlof <bb@ti.com>
~Bryan
> [0] https://lore.kernel.org/linux-devicetree/20250417233040.3658761-1-jm@ti.com/
> [1] https://lore.kernel.org/linux-devicetree/20250429142825.bvrbpoc5iz32wh35@garment/
>
> Link to v1:
> https://lore.kernel.org/linux-devicetree/20250429142333.4140010-1-jm@ti.com/
>
> Judith Mendez (3):
> arm64: dts: ti: k3-am62-main: Set eMMC clock parents to default
> arm64: dts: ti: k3-am62a-main: Set eMMC clock parents to default
> arm64: dts: ti: k3-am62p-j722s-common-main: Set eMMC clock parents to
> default
>
> arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 2 --
> arch/arm64/boot/dts/ti/k3-am62a-main.dtsi | 2 --
> arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi | 2 --
> 3 files changed, 6 deletions(-)
>
>
> base-commit: d864bb528a6725e775d564fd4430762acbb9dd0d
> --
> 2.49.0
>
next prev parent reply other threads:[~2025-04-29 18:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 16:33 [PATCH v2 0/3] Set eMMC clock parent to default Judith Mendez
2025-04-29 16:33 ` [PATCH v2 1/3] arm64: dts: ti: k3-am62-main: " Judith Mendez
2025-04-29 16:33 ` [PATCH v2 2/3] arm64: dts: ti: k3-am62a-main: " Judith Mendez
2025-04-29 16:33 ` [PATCH v2 3/3] arm64: dts: ti: k3-am62p-j722s-common-main: " Judith Mendez
2025-04-29 18:22 ` Bryan Brattlof [this message]
2025-05-02 16:01 ` [PATCH v2 0/3] " Nishanth Menon
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=20250429182244.vm2atpuvmdfhtmlc@bryanbrattlof.com \
--to=bb@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jm@ti.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-shah@ti.com \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.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).