public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: Paul Walmsley <paul@pwsan.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Enabling spidev in MCSPI1
Date: Fri, 15 Jan 2010 08:43:52 -0500	[thread overview]
Message-ID: <4B507118.9000809@balister.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1001131329330.20437@utopia.booyaka.com>

On 01/13/2010 03:36 PM, Paul Walmsley wrote:
> Hi Philip,
>
> On Wed, 13 Jan 2010, Philip Balister wrote:
>
>> I'm trying to enable spidev on mcspi1, but when I do, the kernel while booting
>> after the kernel is uncompressed. No useful messages are displayed. This is
>> with a current git.
>>
>> I've attached the diff I use to add the spi driver to the board file. (OVero +
>> Summit).
>
> Maybe try enabling early printk support if you haven't already?
>
> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg21017.html

I think the early printk stuff was stopping me seeing the message ....

Unfortunately, I found the conflicting driver, the 7846 touchscreen 
driver, and disabled it, so the kernel boots again. (Before I could boot 
with debugging messages enabled)

I suspect the kernel should not crash if two drivers try to claim the 
spi device. If someone is interested, I can reanable the bad 
configuration and try to collect better data.

Philip

      reply	other threads:[~2010-01-15 13:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-13 13:00 Enabling spidev in MCSPI1 Philip Balister
2010-01-13 13:33 ` Hemanth V
2010-01-13 20:36 ` Paul Walmsley
2010-01-15 13:43   ` Philip Balister [this message]

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=4B507118.9000809@balister.org \
    --to=philip@balister.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.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