[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a046159f5feb2ad777a35f109a19edeb294c7027.camel@suse.de>
Date: Fri, 09 Apr 2021 11:28:48 +0200
From: Nicolas Saenz Julienne <nsaenzjulienne@...e.de>
To: Alan Cooper <alcooperx@...il.com>
Cc: Stefan Wahren <stefan.wahren@...e.com>,
Nicolas Saenz Julienne <nsaenz@...nel.org>,
"moderated list:BROADCOM BCM7XXX ARM ARCHITECTURE"
<linux-arm-kernel@...ts.infradead.org>,
linux-mmc <linux-mmc@...r.kernel.org>,
DTML <devicetree@...r.kernel.org>,
BCM Kernel Feedback <bcm-kernel-feedback-list@...adcom.com>,
linux-rpi-kernel@...ts.infradead.org,
Florian Fainelli <f.fainelli@...il.com>, phil@...pberrypi.com,
Tim Gover <tim.gover@...pberrypi.com>,
Scott Branden <sbranden@...adcom.com>,
Adrian Hunter <adrian.hunter@...el.com>,
": Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
Ulf Hansson <ulf.hansson@...aro.org>,
Rob Herring <robh+dt@...nel.org>
Subject: Re: [PATCH 4/4] ARM: dts: Fix-up EMMC2 controller's frequency
Hi Al,
On Wed, 2021-04-07 at 16:37 -0400, Alan Cooper wrote:
> Nicolas,
>
> I got a better description of the failure and it looks like the bus
> clock needs to be limited to 300KHz for a 500MHz core clock.
> What's happening is that an internal reset sequence is needed after a
> command timeout and the reset signal needs to be asserted for at least
> 2 ticks of the bus clock. This is done using a 12 bit counter clocked
> by the core clock. That means a 500MHz core clock produces a 122KHz
> reset signal which is too fast for 2 ticks of the 200KHz bus clock
> (100KHz) but is okay for the 300KHz (150Khz) bus clock.
Thanks for the info. I'll work something out.
Regards,
Nicolas
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists