From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Sakoman Subject: Re: Overo broken after recent mainline merge Date: Sun, 15 Mar 2009 15:15:02 -0700 Message-ID: <5e088bd90903151515g25ccb614q6537c5c64ee81cbd@mail.gmail.com> References: <5e088bd90903140624u5b5098f4vd9b1afa937325779@mail.gmail.com> <200903141208.30413.david-b@pacbell.net> <5e088bd90903141647s2faee448s6472f6b7bb9e0ba4@mail.gmail.com> <200903141900.08727.david-b@pacbell.net> <5e088bd90903151256v554ee5edwbf36d2ebc29add03@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from wf-out-1314.google.com ([209.85.200.170]:22158 "EHLO wf-out-1314.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752685AbZCOWPE convert rfc822-to-8bit (ORCPT ); Sun, 15 Mar 2009 18:15:04 -0400 Received: by wf-out-1314.google.com with SMTP id 28so1548719wfa.4 for ; Sun, 15 Mar 2009 15:15:02 -0700 (PDT) In-Reply-To: <5e088bd90903151256v554ee5edwbf36d2ebc29add03@mail.gmail.com> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: David Brownell , linux-omap , Tony Lindgren On Sun, Mar 15, 2009 at 12:56 PM, Steve Sakoman wro= te: > On Sat, Mar 14, 2009 at 7:00 PM, David Brownell = wrote: > >> Works for me, and I think you've got all the patches that >> should matter. =A0 This is against today's GIT, yes? >> Does taking #3 away help? > > I'm not sure why it is working for you! =A0Perhaps you have some patc= hes > that aren't included in the current tree? > > I believe the root issue is in your recent Overo patch > (http://marc.info/?l=3Dlinux-omap&m=3D123679791627030&w=3D2) > > In particular, these lines: > > + =A0 =A0 =A0 /* gpio + 0 is "mmc0_cd" (input/IRQ) */ > + =A0 =A0 =A0 mmc[0].gpio_cd =3D gpio + 0; > > Overo, having a microSD slot, doesn't have a card detect switch. The > other part of your patch sets gpio_cd properly: > > +static struct twl4030_hsmmc_info mmc[] =3D { > + =A0 =A0 =A0 { > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 .mmc =A0 =A0 =A0 =A0 =A0 =A0=3D 1, > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 .wires =A0 =A0 =A0 =A0 =A0=3D 4, > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 .gpio_cd =A0 =A0 =A0 =A0=3D -EINVAL, > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 .gpio_wp =A0 =A0 =A0 =A0=3D -EINVAL, > + =A0 =A0 =A0 }, > + =A0 =A0 =A0 { > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 .mmc =A0 =A0 =A0 =A0 =A0 =A0=3D 2, > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 .wires =A0 =A0 =A0 =A0 =A0=3D 4, > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 .gpio_cd =A0 =A0 =A0 =A0=3D -EINVAL, > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 .gpio_wp =A0 =A0 =A0 =A0=3D -EINVAL, > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 .transceiver =A0 =A0=3D true, > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 .ocr_mask =A0 =A0 =A0 =3D 0x00100000, =A0= /* 3.3V */ > + =A0 =A0 =A0 }, > + =A0 =A0 =A0 {} =A0 =A0 =A0/* Terminator */ > +}; > > So all I had to do was remove the above 2 lines to get a successful b= oot. I spoke a little too soon :-) The above fix does get me past the mmc issue, and everything looks fine from the serial console. But I just noticed that DVI is broken -- I suspect that some regulator magic may be required in the video driver too :-( Steve -- To unsubscribe from this list: send the line "unsubscribe linux-omap" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html