From: Peter Korsgaard Date: Mon, 04 Mar 2013 15:04:29 +0100 Subject: [U-Boot] [PATCH v2 7/9] am33xx: support ti814x mmc reference clock In-Reply-To: <20130304135731.GD6209@beef> (Matt Porter's message of "Mon, 4 Mar 2013 08:57:31 -0500") References: <1362101393-5131-1-git-send-email-mporter@ti.com> <1362101393-5131-8-git-send-email-mporter@ti.com> <80ea5e8e05d24152a4572f154a7124f0@DFLE72.ent.ti.com> <20130304135731.GD6209@beef> Message-ID: <87r4jvb6s2.fsf@dell.be.48ers.dk> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de >>>>> "Matt" == Matt Porter writes: Hi, >> Did you figure out why it was working for you with 96 MHz ref? Matt> Unfortunately not at a root cause level. Unless I'm missing Matt> something I would have expected the calculations from the Matt> supplied 96 MHz ref clock to result in 2x the clock the SD card Matt> can handle due to the incorrect divider. However, with the LA Matt> attached, I found that a 2-3 MHz SDCLK was being generated after Matt> the capability probe occurs. Odd and incorrect, but Matt> functional. After switching to 192MHz I was able to sample a Matt> nominal 25MHz SDCLK as expected on a regular SD card advertising Matt> that as its capability. I don't like it but I'm going to mark Matt> this down as "something undocumented" as I only have PG1.0 Matt> silicon but can't find an errata sheet for that version right Matt> now. Ok, thanks for the info. -- Bye, Peter Korsgaard