From: Patrick Williams <patrick@stwcx.xyz>
To: Eddie James <eajames@linux.ibm.com>
Cc: openbmc@lists.ozlabs.org, andrew@aj.id.au
Subject: Re: [PATCH linux dev-5.7 v2 0/2] clk: Aspeed: Fix eMMC clock speeds
Date: Fri, 10 Jul 2020 08:13:45 -0500 [thread overview]
Message-ID: <20200710131345.GI3922@heinlein> (raw)
In-Reply-To: <20200709194113.12119-1-eajames@linux.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 794 bytes --]
Hi Eddie,
On Thu, Jul 09, 2020 at 02:41:11PM -0500, Eddie James wrote:
> There were two problems affecting clock speeds to the eMMC chip. Firstly, the
> AST2600 clock was not muxed correctly to be derived from the MPLL. Secondly,
> the SDHCI clock control divider was not calculated correctly. This series
> addresses these problems.
Do either of these affect the AST2500? It looks like maybe the sdhci
one would affect both?
>
> Eddie James (2):
> clk: AST2600: Add mux for EMMC clock
> mmc: sdhci-of-aspeed: Fix clock divider calculation
>
> drivers/clk/clk-ast2600.c | 49 +++++++++++++++++++++++++-----
> drivers/mmc/host/sdhci-of-aspeed.c | 2 +-
> 2 files changed, 42 insertions(+), 9 deletions(-)
>
> --
> 2.24.0
>
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-07-10 13:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 19:41 [PATCH linux dev-5.7 v2 0/2] clk: Aspeed: Fix eMMC clock speeds Eddie James
2020-07-09 19:41 ` [PATCH linux dev-5.7 v2 1/2] clk: AST2600: Add mux for EMMC clock Eddie James
2020-07-09 19:41 ` [PATCH linux dev-5.7 v2 2/2] mmc: sdhci-of-aspeed: Fix clock divider calculation Eddie James
2020-07-10 1:14 ` Andrew Jeffery
2020-07-10 13:13 ` Patrick Williams [this message]
2020-07-10 13:33 ` [PATCH linux dev-5.7 v2 0/2] clk: Aspeed: Fix eMMC clock speeds Andrew Jeffery
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=20200710131345.GI3922@heinlein \
--to=patrick@stwcx.xyz \
--cc=andrew@aj.id.au \
--cc=eajames@linux.ibm.com \
--cc=openbmc@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.