From: Philip Balister <philip@balister.org>
To: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: McSPI3 on the BeagleBoard
Date: Fri, 20 Feb 2009 14:19:01 -0500 [thread overview]
Message-ID: <499F0225.5020402@balister.org> (raw)
In-Reply-To: <1235118800.6894.18.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 2853 bytes --]
Gregoire Gentil wrote:
> Philip,
>
> I found the patch. Thanks. SPI3 is working for me too but I think that
> there are a couple of errors:
>
> - first, in the patch you posted on the beagleboard mailing list, you
> don't setup CS0 and CS1 pins in u-boot. I think that you should do it.
Yeah. I wanted to get the info out quickly since there are a couple of
longish threads on the Beagle list over the problem.
> - secondly, you have added more mux configuration in the kernel for SPI3
> that should not be SPI3 but those new ones are wrong as they are
> competing with some USB pins. It's the same error as David pointed you
> for MMC2. Nevertheless, it's still working. Why? Because I have now a
> strong feeling that mux configuration is not working in the kernel (at
> least for the beagleboard). Here are a few facts that would confirm this
> statement:
I thought I #if 0 ... #endif the kernel mux code? I'll double check. I
should try it with un patched u-boot and only the specific pins set in
the kernel.
I'm juggling too many different things atm :(
I also changed the PIN MUX config option in the flag per another question.
Philip
>
> - MUX setup for USB ehci has never worked in the kernel. It's why the
> beagleaboard rev-C ehci patch has been transfered to u-boot.
>
> - the difference between your patch before and after it was working, is
> really the u-boot configuration. You haven't really changed anything in
> the kernel (especially in the spi driver) and as mentioned above, you
> have even introduced some competing muxes that should have created more
> trouble if the kernel mux config were working correctly.
>
> - I had two other areas where I configured the pins in kernel and it was
> not working. Only when I eventually did it in u-boot, it started to
> work.
>
> I don't know what's wrong with the pin configuration in the kernel,
>
> Grégoire
>
>
> On Thu, 2009-02-19 at 09:14 -0500, Philip Balister wrote:
>> Gregoire Gentil wrote:
>>> Philip,
>>>
>>> Can you please post here or on the Beagleboard mailing list the u-boot
>>> patch? This muxpin is very tricky and I have experienced many problems
>>> when set up in the kernel while it seems to work better from u-boot -
>>> don't know why,
>> I posted it to the Beagle group. Let me know if you are having trouble
>> finding it.
>>
>> If we come up with a better config for the expansion port, we'll clean
>> it up and submit here. My gut feeling is having SPI interfaces on the
>> expansion connector will be more useful then the MMC interface.
>>
>> Philip
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
prev parent reply other threads:[~2009-02-20 19:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 23:42 McSPI3 on the BeagleBoard Philip Balister
2009-02-18 0:09 ` Tony Lindgren
2009-02-18 3:18 ` David Brownell
2009-02-19 0:39 ` Philip Balister
2009-02-19 0:53 ` Tony Lindgren
2009-02-19 8:22 ` Gregoire Gentil
2009-02-19 14:14 ` Philip Balister
2009-02-20 8:33 ` Gregoire Gentil
2009-02-20 11:44 ` Grazvydas Ignotas
2009-02-20 19:19 ` 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=499F0225.5020402@balister.org \
--to=philip@balister.org \
--cc=linux-omap@vger.kernel.org \
/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