From owner-freebsd-arm@FreeBSD.ORG Thu May 22 14:14:09 2014 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BFDDA5F7; Thu, 22 May 2014 14:14:09 +0000 (UTC) Received: from msgw001-05.ocn.ad.jp (msgw001-05.ocn.ad.jp [180.37.203.74]) by mx1.freebsd.org (Postfix) with ESMTP id 72AA9264A; Thu, 22 May 2014 14:14:09 +0000 (UTC) Received: from localhost (p12095-ipngn100104sizuokaden.shizuoka.ocn.ne.jp [153.185.230.95]) by msgw001-05.ocn.ad.jp (Postfix) with ESMTP id D81E4A82C2B; Thu, 22 May 2014 23:14:07 +0900 (JST) Date: Thu, 22 May 2014 23:14:04 +0900 (JST) Message-Id: <20140522.231404.174358702.toshi@ruby.ocn.ne.jp> To: ian@FreeBSD.org Subject: Re: BBB MMC / SD detection instability with U-Boot 2014.04 (CPU 1GHz) From: SAITOU Toshihide In-Reply-To: <1400764684.1152.218.camel@revolution.hippie.lan> References: <1400708280.1152.199.camel@revolution.hippie.lan> <20140522.203923.240655619.toshi@ruby.ocn.ne.jp> <1400764684.1152.218.camel@revolution.hippie.lan> X-GPG-fingerprint: 34B3 0B6A 8520 F5B0 EBC7 69F6 C055 9F8A 0D49 F8FC X-Mailer: Mew version 6.2.51 on Emacs 22.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-arm@FreeBSD.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 May 2014 14:14:09 -0000 In message: <1400764684.1152.218.camel@revolution.hippie.lan> Ian Lepore writes: > On Thu, 2014-05-22 at 20:39 +0900, SAITOU Toshihide wrote: >> In message: <1400708280.1152.199.camel@revolution.hippie.lan> >> Ian Lepore writes: >> > On Tue, 2014-05-20 at 23:42 +0900, SAITOU Toshihide wrote: >> >> In message: <537B62D1.4090901@hot.ee> >> >> "Sulev-Madis Silber (ketas)" writes: >> >> > On 2014-05-20 15:20, SAITOU Toshihide wrote: >> >> >> In message: <20140520.191001.03109216.toshi@ruby.ocn.ne.jp> >> >> >> SAITOU Toshihide writes: >> >> >>> In message: <537ACDB2.9080808@hot.ee> >> >> >>> "Sulev-Madis Silber (ketas)" writes: >> >> >>>> >> >> >>>> Actually I guess many people might think like me... "HELL, optimizing >> >> >>>> boot time of 1min?! I have more important tasks to do than this". >> >> >>> >> >> >>> If you have ``device sdhci'' line in conf/BEAGLEBONE, is there any >> >> >>> differences by changing mmchs to sdhci in am335x.dtsi and >> >> >>> beaglebone-black.dts? And also remove ``status = "disabled"'' >> >> > >> >> > Don't edit am335x.dtsi >> >> > >> >> > And beaglebone-black.dts already has proper config. >> >> >> >> In this case, how does ``device sdhci'' driver know the register address? >> >> I thought that there is an inconsistency in BEAGLEBONE config and >> >> dts file for the SD/MMC driver. >> > >> > The name@address tag in the dts[i] files doesn't have to match the >> > driver name in the kernel config. What matters for matching the driver >> > to the right entry in the dts is the "compatible=" property. The >> > ti_sdhci driver looks for an entry with any one of these compatible >> > strings: >> > >> > "ti,omap3-hsmmc", "ti,omap4-hsmmc", "ti,mmchs" >> >> Ah! I see ti_sdhci.c has ofw_bus_is_compatible(dev, "ti,mmchs"). >> (Why I felt difference of eMMC detection... Hmm...) > > What version of source code are you using to see that? You should be > seeing a ofw_bus_search_compatible() call using a table of compatible > strings that has those entries I listed. FreeBSD 11.0-CURRENT #41 r265876:266494M: Thu May 22 08:18:49 JST 2014 but ti_sdhci.c is 254559 I am suprised. I will try at the weekend. -- SAITOU Toshihide