From: "Girish" <girishsg@ti.com>
To: 'Meng Hu' <meng.hu@gmail.com>
Cc: Linux-omap-open-source@linux.omap.com
Subject: RE: McSPI interfaces in newer kernel
Date: Thu, 13 Dec 2007 11:28:07 +0530 [thread overview]
Message-ID: <006201c83d4d$22a53e50$988818ac@ent.ti.com> (raw)
In-Reply-To: <94d6903b0712121554o5097604cxecaeac2b36832e33@mail.gmail.com>
>-----Original Message-----
>From: Meng Hu [mailto:meng.hu@gmail.com]
>Sent: Thursday, December 13, 2007 5:24 AM
>To: Girish
>Cc: Linux-omap-open-source@linux.omap.com
>Hi, Girish
>I am working on an OMAP2430 board, not the SDP though.
>The wierd thing is, the new upstream SPI driver fails on my board.
>Here are the kernel messages:
>---omap2_mcspi_init---
>omap2_mcspi_probe 1
>omap2_mcspi: probe of omap2_mcspi.1 failed with error -2
>omap2_mcspi_probe 2
>omap2_mcspi: probe of omap2_mcspi.2 failed with error -2
>
>Any idea about this?
Omap2_mcspi should be working fine on 2430, check with your clock enabling, if it's causing the break.
>
>On the other hand, I ported the old TI SPI drivers to the new
>kernel and they seem to work.
>And my 2046 touchscreen driver works fine with the old TI SPI drivers.
>There might be potential problems. I don't know.
You might want to use ads7846 touchscreen driver which is in upstream, 2046 is a newer ads7846 silicon.
-Girish
>> _______________________________________________
>> >Linux-omap-open-source mailing list
>> >Linux-omap-open-source@linux.omap.com
>> >http://linux.omap.com/mailman/listinfo/linux-omap-open-source
>> >
>>
>>
>
prev parent reply other threads:[~2007-12-13 5:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 19:15 McSPI interfaces in newer kernel Meng Hu
2007-12-11 19:59 ` Kevin Hilman
2007-12-12 23:34 ` Meng Hu
2007-12-12 15:10 ` Girish
2007-12-12 23:54 ` Meng Hu
2007-12-13 5:58 ` Girish [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='006201c83d4d$22a53e50$988818ac@ent.ti.com' \
--to=girishsg@ti.com \
--cc=Linux-omap-open-source@linux.omap.com \
--cc=meng.hu@gmail.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