From: Ben Gamari <bgamari.foss@gmail.com>
To: ml@communistcode.co.uk, balbi@ti.com
Cc: linux-omap@vger.kernel.org,
Shubhrajyoti Datta <omaplinuxkernel@gmail.com>
Subject: Re: AM335x BeagleBone SPI Issues
Date: Tue, 11 Dec 2012 10:22:26 -0500 [thread overview]
Message-ID: <87y5h4r4ul.fsf@gmail.com> (raw)
In-Reply-To: <50C70846.7010207@communistcode.co.uk>
Jack Mitchell <ml@communistcode.co.uk> writes:
> Shubhro, Felipe,
>
> Thank you, the reordering dma patch fixed the dma issue I was having!
> However, the bad news, I now get the same results for the dma and
> non-dma spidev test. While the scope shows the SPI clk and data is fine,
> the reading from the program still shows 0x00 for all words.
>
Just to make sure this has been thought of: I've seen this sort of
behavior in the past when the CLK pin wasn't configured as an input.
Cheers,
- Ben
next prev parent reply other threads:[~2012-12-11 15:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 13:23 AM335x BeagleBone SPI Issues Jack Mitchell
2012-12-10 13:53 ` Felipe Balbi
2012-12-10 14:50 ` Jack Mitchell
2012-12-10 14:59 ` Felipe Balbi
2012-12-10 15:19 ` Jack Mitchell
2012-12-10 15:26 ` Shubhrajyoti Datta
2012-12-10 16:18 ` Jack Mitchell
2012-12-10 18:35 ` Felipe Balbi
2012-12-11 6:39 ` Shubhrajyoti Datta
2012-12-11 10:17 ` Jack Mitchell
2012-12-11 10:20 ` Felipe Balbi
2012-12-11 10:38 ` Jack Mitchell
2012-12-11 11:48 ` Felipe Balbi
2012-12-11 14:27 ` Felipe Balbi
2012-12-11 15:23 ` Jack Mitchell
2012-12-11 16:15 ` Felipe Balbi
2012-12-11 15:22 ` Ben Gamari [this message]
2012-12-11 16:24 ` Jack Mitchell
2012-12-11 16:36 ` Jack Mitchell
2012-12-11 17:02 ` Jack Mitchell
2013-01-04 14:46 ` Jan Lübbe
2013-01-04 16:21 ` Jack Mitchell
2013-01-04 16:36 ` Jack Mitchell
2012-12-11 17:03 ` Felipe Balbi
2012-12-11 17:52 ` Felipe Balbi
2012-12-12 8:07 ` Felipe Balbi
-- strict thread matches above, loose matches on Subject: below --
2012-12-10 13:17 Jack Mitchell
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=87y5h4r4ul.fsf@gmail.com \
--to=bgamari.foss@gmail.com \
--cc=balbi@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=ml@communistcode.co.uk \
--cc=omaplinuxkernel@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 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.