From: Mark Howell <mhowell@northlink.com>
To: Matthew Percival <matthew@capgo.com>
Cc: Linux OMAP Open Source <linux-omap-open-source@linux.omap.com>
Subject: Re: Using McBSP in kernel...
Date: Wed, 26 Jul 2006 14:16:00 -0700 [thread overview]
Message-ID: <44C7DB90.3050406@northlink.com> (raw)
In-Reply-To: <1153723664.5162.18.camel@localhost.localdomain>
Matthew, I have a working driver that uses McBSP2 to talk to an SPI
slave on my H2 (1611) dev board. It does *not* use the McBSP SPI driver
in the kernel, but rather goes straight to the McBSP registers. If this
would be handy to play with or refer to, I can e it to you off-list.
Cheers,
Mark.
Matthew Percival wrote:
> G'Day,
>
> I am still unsuccessful at using McBSP2 as an SPI Master in a kernel
> driver. I have confirmed that the mux settings are correct, and have
> attempted using a pull up (though have noted no change).
>
> An interesting occurrence I have observed in my testing is that if I
> test that XRDY is set, indicating that I can load DXR2/1, load the
> transmit registers, then check again, XRDY is still set afterwards, and
> both registers still reflect the values I put in them earlier. Clearly
> the module is not attempting to transmit, which would explain why I see
> nothing with the CRO.
>
> Looking over the diagrams in spru762, I came across something
> interesting. I understand that, for an SPI Master, FSXM should be set
> to 1, yet Figure 4 suggests that MCBSP2.FSX will only come out if FSXM
> is set to 0. Am I mistaken in this, is the diagram wrong, or perhaps is
> McBSP2 unsuitable for use as a SPI Master (or at least in the way I have
> configured it)?
>
> Thanks,
>
> Matthew
>
> PS I shall include a current register dump, in case this is of use:
> DRR2: 0x0000
> DRR1: 0x0000
> DXR2: 0x0000
> DXR1: 0x0000
> SPCR2: 0x00C3
> SPCR1: 0x1001
> RCR2: 0x0001
> RCR1: 0x00A0
> XCR2: 0x0001
> XCR1: 0x00A0
> SRGR2: 0x2000
> SRGR1: 0x1F00
> PCR0: 0x0A0B
>
> _______________________________________________
> Linux-omap-open-source mailing list
> Linux-omap-open-source@linux.omap.com
> http://linux.omap.com/mailman/listinfo/linux-omap-open-source
>
>
>
next prev parent reply other threads:[~2006-07-26 21:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-20 12:16 Using McBSP in kernel Khasim, Syed
2006-07-24 6:47 ` Matthew Percival
2006-07-26 21:16 ` Mark Howell [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-19 15:17 Khasim, Syed
2006-07-20 6:53 ` Matthew Percival
2006-07-19 6:56 Matthew Percival
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=44C7DB90.3050406@northlink.com \
--to=mhowell@northlink.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=matthew@capgo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.