| Message ID | 877geohh6r.fsf@linaro.org (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
On Tue, Sep 10, 2013 at 07:42:04AM -0700, Kevin Hilman wrote: > Fabio Estevam <festevam@gmail.com> writes: > > > On Mon, Sep 9, 2013 at 1:19 PM, Robert Nelson <robertcnelson@gmail.com> wrote: > > > >>> Ok, I made this test and it booted fine. > >>> > >>> So I will change U-boot so that it searches for imx6dl-wandboard.dtb > >>> instead of imx6s-wandboard.dtb. > >> > >> Since there is no WiFi/Bluetooth on the "solo" vs the wandboard dual > >> lite, we should really still have a separate solo dtb file.. > > > > I think we could still represent the im6solo-wandboard using the > > imx6dl-wandboard.dts. > > > > In the case of lack of bcm4329 populated on a mx6solo board, the SDHC3 > > port will just not probe bcm4329 without any negative effect, right? > > I've noticed in my auto build/boot[1] that booting a wandboard solo with > imx6dl-wandboard.dtb actually faults[2]. Just disabling usdhc2[3] makes > it boot fine. > > This only happens on current linus/HEAD. v3.11 boots fine as does > linux-next (as of next-20130910.) It may be because commit 2af502c (mmc: sdhci: request irq after sdhci_init() is called) which is on linux-next right now hasn't landed on mainline yet. Shawn
On Tue, Sep 10, 2013 at 8:05 AM, Shawn Guo <shawn.guo@linaro.org> wrote: > On Tue, Sep 10, 2013 at 07:42:04AM -0700, Kevin Hilman wrote: >> Fabio Estevam <festevam@gmail.com> writes: >> >> > On Mon, Sep 9, 2013 at 1:19 PM, Robert Nelson <robertcnelson@gmail.com> wrote: >> > >> >>> Ok, I made this test and it booted fine. >> >>> >> >>> So I will change U-boot so that it searches for imx6dl-wandboard.dtb >> >>> instead of imx6s-wandboard.dtb. >> >> >> >> Since there is no WiFi/Bluetooth on the "solo" vs the wandboard dual >> >> lite, we should really still have a separate solo dtb file.. >> > >> > I think we could still represent the im6solo-wandboard using the >> > imx6dl-wandboard.dts. >> > >> > In the case of lack of bcm4329 populated on a mx6solo board, the SDHC3 >> > port will just not probe bcm4329 without any negative effect, right? >> >> I've noticed in my auto build/boot[1] that booting a wandboard solo with >> imx6dl-wandboard.dtb actually faults[2]. Just disabling usdhc2[3] makes >> it boot fine. >> >> This only happens on current linus/HEAD. v3.11 boots fine as does >> linux-next (as of next-20130910.) > > It may be because commit 2af502c (mmc: sdhci: request irq after > sdhci_init() is called) which is on linux-next right now hasn't landed > on mainline yet. Yup, linus/HEAD + that commit makes things work again. Thanks. Kevin
diff --git a/arch/arm/boot/dts/imx6qdl-wandboard.dtsi b/arch/arm/boot/dts/imx6qdl-wandboard.dtsi index a55113e..8d80181 100644 --- a/arch/arm/boot/dts/imx6qdl-wandboard.dtsi +++ b/arch/arm/boot/dts/imx6qdl-wandboard.dtsi @@ -126,7 +126,7 @@ pinctrl-names = "default"; pinctrl-0 = <&pinctrl_usdhc2_2>; non-removable; - status = "okay"; + status = "disabled"; }; &usdhc3 {