All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Percival <matthew@capgo.com>
To: Linux OMAP Open Source <linux-omap-open-source@linux.omap.com>
Subject: RE: Using McBSP in kernel...
Date: Mon, 24 Jul 2006 16:47:44 +1000	[thread overview]
Message-ID: <1153723664.5162.18.camel@localhost.localdomain> (raw)
In-Reply-To: <77C7F7CB1230A74A9D19C0C111E6EDBEB21CD9@DLEE09.ent.ti.com>

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

  reply	other threads:[~2006-07-24  6:47 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 [this message]
2006-07-26 21:16   ` Mark Howell
  -- 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=1153723664.5162.18.camel@localhost.localdomain \
    --to=matthew@capgo.com \
    --cc=linux-omap-open-source@linux.omap.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.