From: Fabio Estevam <festevam@gmail.com>
To: Adam Ford <aford173@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, aford@beaconembedded.com,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] arm64: dts: imx8mm-beacon: Fix HS400 USDHC clock speed
Date: Thu, 3 Jul 2025 09:44:36 -0300 [thread overview]
Message-ID: <CAOMZO5B-7LuYs34ACmMD7S3B0Sxihe8A+atdNi_3QfMP3VFYtg@mail.gmail.com> (raw)
In-Reply-To: <20250620213447.56392-1-aford173@gmail.com>
On Fri, Jun 20, 2025 at 6:34 PM Adam Ford <aford173@gmail.com> wrote:
>
> The reference manual for the i.MX8MM states the clock rate in
> MMC mode is 1/2 of the input clock, therefore to properly run
> at HS400 rates, the input clock must be 400MHz to operate at
> 200MHz. Currently the clock is set to 200MHz which is half the
> rate it should be, so the throughput is half of what it should be
> for HS400 operation.
>
> Fixes: 593816fa2f35 ("arm64: dts: imx: Add Beacon i.MX8m-Mini development kit")
> Signed-off-by: Adam Ford <aford173@gmail.com>
Reviewed-by: Fabio Estevam <festevam@gmail.com>
next prev parent reply other threads:[~2025-07-03 12:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 21:34 [PATCH 1/2] arm64: dts: imx8mm-beacon: Fix HS400 USDHC clock speed Adam Ford
2025-06-20 21:34 ` [PATCH 2/2] arm64: dts: imx8mn-beacon: " Adam Ford
2025-07-03 12:45 ` Fabio Estevam
2025-06-27 17:56 ` [PATCH 1/2] arm64: dts: imx8mm-beacon: " Tim Harvey
2025-06-27 18:39 ` Adam Ford
2025-06-27 23:51 ` Tim Harvey
2025-07-02 14:20 ` Adam Ford
2025-07-03 12:44 ` Fabio Estevam [this message]
2025-07-07 7:22 ` Shawn Guo
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=CAOMZO5B-7LuYs34ACmMD7S3B0Sxihe8A+atdNi_3QfMP3VFYtg@mail.gmail.com \
--to=festevam@gmail.com \
--cc=aford173@gmail.com \
--cc=aford@beaconembedded.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
/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).