From owner-freebsd-arm@FreeBSD.ORG Wed May 21 21:38:04 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 96412D25 for ; Wed, 21 May 2014 21:38:04 +0000 (UTC) Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 69439232C for ; Wed, 21 May 2014 21:38:03 +0000 (UTC) Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52] helo=damnhippie.dyndns.org) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1WnED4-000IZd-Rk; Wed, 21 May 2014 21:38:02 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id s4LLc0op045506; Wed, 21 May 2014 15:38:00 -0600 (MDT) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 24.8.230.52 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1+td6BDOaLe1QCbHYiggPba Subject: Re: BBB MMC / SD detection instability with U-Boot 2014.04 (CPU 1GHz) From: Ian Lepore To: SAITOU Toshihide In-Reply-To: <20140520.234245.38709064.toshi@ruby.ocn.ne.jp> References: <20140520.191001.03109216.toshi@ruby.ocn.ne.jp> <20140520.212003.232778263.toshi@ruby.ocn.ne.jp> <537B62D1.4090901@hot.ee> <20140520.234245.38709064.toshi@ruby.ocn.ne.jp> Content-Type: text/plain; charset="us-ascii" Date: Wed, 21 May 2014 15:38:00 -0600 Message-ID: <1400708280.1152.199.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port 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: Wed, 21 May 2014 21:38:04 -0000 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" -- Ian