BBB MMC / SD detection instability with U-Boot 2014.04 (CPU 1GHz)
SAITOU Toshihide
toshi at ruby.ocn.ne.jp
Sat May 24 11:02:12 UTC 2014
In message: <20140522.231404.174358702.toshi at ruby.ocn.ne.jp>
SAITOU Toshihide <toshi at ruby.ocn.ne.jp> writes:
> In message: <1400764684.1152.218.camel at revolution.hippie.lan>
> Ian Lepore <ian at FreeBSD.org> writes:
>> On Thu, 2014-05-22 at 20:39 +0900, SAITOU Toshihide wrote:
>>> In message: <1400708280.1152.199.camel at revolution.hippie.lan>
>>> Ian Lepore <ian at FreeBSD.org> writes:
>>> > On Tue, 2014-05-20 at 23:42 +0900, SAITOU Toshihide wrote:
>>> >> In message: <537B62D1.4090901 at hot.ee>
>>> >> "Sulev-Madis Silber (ketas)" <madis555 at hot.ee> writes:
>>> >> > On 2014-05-20 15:20, SAITOU Toshihide wrote:
>>> >> >> In message: <20140520.191001.03109216.toshi at ruby.ocn.ne.jp>
>>> >> >> SAITOU Toshihide <toshi at ruby.ocn.ne.jp> writes:
>>> >> >>> In message: <537ACDB2.9080808 at hot.ee>
>>> >> >>> "Sulev-Madis Silber (ketas)" <madis555 at hot.ee> 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 at 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.
Without changing dts, SD/eMMC is fairly working.
It seems that my feeling was caused by source contamination.
--
SAITOU Toshihide
More information about the freebsd-arm
mailing list