Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Javier Martinez Canillas <javier@dowhile0.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Santosh Shilimkar <santosh.shilimkar@ti.com>,
	Kevin Hilman <khilman@linaro.org>,
	Peter Ujfalusi <peter.ujfalusi@ti.com>,
	Nishanth Menon <nm@ti.com>,
	linux-omap <linux-omap@vger.kernel.org>,
	Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Subject: Re: regressions in linux-next?
Date: Tue, 22 Apr 2014 16:47:53 -0700	[thread overview]
Message-ID: <20140422234753.GC12204@atomide.com> (raw)
In-Reply-To: <CABxcv==aaBKO0Mos1=RuGhF8X6pVAki748vnzH7ADYraTpBxRQ@mail.gmail.com>

* Javier Martinez Canillas <javier@dowhile0.org> [140422 16:03]:
> Hello Linus,
> 
> On Wed, Apr 23, 2014 at 12:00 AM, Linus Walleij
> <linus.walleij@linaro.org> wrote:
> > On Tue, Apr 22, 2014 at 5:52 PM, Javier Martinez Canillas
> > <javier@dowhile0.org> wrote:
> >
> >> I've revised the patch again and I couldn't find the reason why
> >> certain boards are failing to boot.
> >>
> >> I can't reproduce this issue since I only have a DM3730 IGEPv2 board
> >> which boots fine but I should have access to an AM3354 IGEP Aquila
> >> board which is similar to the am335x-evmsk so I may be able to debug
> >> it.
> >
> > It would really REALLY appreciate if some of the people maintaining
> > and using OMAP1 would help Javier out in this refactoring operation.
> >
> 
> The board that is failing to boot with this patch-set is not an OMAP1
> based board but the Sitara AM335x Starter Kit
> (arch/arm/boot/dts/am335x-evmsk.dts).

This does not happen to have anything to do with the ti,no-reset-on-init
hack for &gpio0 on the am335x-evmsk.dts that's needed to keep DDR
powered? See the am43x thread for more info.
 
> Now, other boards using the same SoC like the Beagle Bone Black are
> booting correctly and also am335x-evm which is very similar to
> am335x-evmsk.dts.

Except for the gpio0 hack..
 
> Nishanth has access to this board and his helping now with the debugging.
> 
> > I'd really *hate* to have to drop his patches because of a lack of
> > boards. This refactoring is necessary to handle the exploding
> > multitude of GPIO drivers moving forward.
> >
> 
> Yeah, I'm doing my best to keep this driver up-to-date with the latest
> changes in gpiolib but it seems that is very hard to change the OMAP
> GPIO driver without breaking one of the gazillion TI platforms out
> there...
> 
> > We even tried to get an Innovator to boot just to be able to refactor
> > OMAP stuff but fell short on some special JTAG reflash snag so
> > we are dependent on maintainers to help out here :-/

I got it to the point where some relatively recent u-boot was loading
fine over JTAG but the first stage did not boot properly from NOR for
some reason.

Regards,

Tony

  reply	other threads:[~2014-04-22 23:47 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-22 13:18 regressions in linux-next? Nishanth Menon
2014-04-22 13:29 ` Peter Ujfalusi
2014-04-22 15:52   ` Javier Martinez Canillas
2014-04-22 19:37     ` Ezequiel Garcia
2014-04-22 22:32       ` Javier Martinez Canillas
2014-04-22 22:00     ` Linus Walleij
2014-04-22 23:03       ` Javier Martinez Canillas
2014-04-22 23:47         ` Tony Lindgren [this message]
2014-04-24 15:16       ` Kevin Hilman
2014-04-24 15:25         ` Nishanth Menon
2014-04-24 15:37           ` Javier Martinez Canillas
2014-04-24 15:42             ` Tony Lindgren
2014-04-24 16:33               ` Javier Martinez Canillas
2014-04-24 16:47                 ` Tony Lindgren
2014-04-24 15:40           ` Tony Lindgren
2014-04-24 15:46             ` Nishanth Menon
2014-04-24 16:17               ` Tony Lindgren
2014-04-24 17:08                 ` Nishanth Menon
2014-04-24 19:59                   ` Aaro Koskinen
2014-04-24 19:22           ` Aaro Koskinen
2014-04-28 22:04         ` Paul Walmsley
2014-04-22 15:13 ` Nishanth Menon
2014-04-22 21:57   ` Nishanth Menon
2014-04-22 22:45     ` Javier Martinez Canillas
2014-04-22 22:52       ` Nishanth Menon
2014-04-22 23:08         ` Javier Martinez Canillas
2014-04-23  1:30           ` Nishanth Menon
2014-04-23  7:24             ` Javier Martinez Canillas
2014-04-23 10:59               ` Peter Ujfalusi
2014-04-23 13:01               ` Linus Walleij
2014-04-23 13:29                 ` Nishanth Menon
2014-04-23 14:38                   ` Linus Walleij
2014-04-23 14:50                     ` Javier Martinez Canillas
2014-04-23 14:52                       ` Linus Walleij

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140422234753.GC12204@atomide.com \
    --to=tony@atomide.com \
    --cc=javier.martinez@collabora.co.uk \
    --cc=javier@dowhile0.org \
    --cc=khilman@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=peter.ujfalusi@ti.com \
    --cc=santosh.shilimkar@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox