From: Hsin-yu Chao <hychao@google.com>
To: Oder Chiou <oder_chiou@realtek.com>
Cc: "Jack Yu" <jack.yu@realtek.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"Albert Chen" <albertchen@realtek.com>,
"Mark Brown" <broonie@kernel.org>,
"Shuming [范書銘]" <shumingf@realtek.com>,
"Bard Liao" <bardliao@realtek.com>,
"Flove(HsinFu)" <flove@realtek.com>
Subject: Re: [PATCH] ASoC: rt5514: Use the local variable to get the data from SPI device
Date: Tue, 25 Jul 2017 22:47:55 +0800 [thread overview]
Message-ID: <CANyK0SmAVH2GBBA_69D-omT_pJuHA_v2oE9ExbPYEe_WbFxi9Q@mail.gmail.com> (raw)
In-Reply-To: <7EB0DE829A537248AF2ED30C97D12694023B5FB9@RTITMBSV02.realtek.com.tw>
The original cause seems to be in spi driver.
I tested setting enable_dma flag to false in spi-pxa2xx driver and that
fixes the problem.
Will investigate in spi driver side. Thanks!
Hsin-yu
On Mon, Jul 24, 2017 at 11:06 AM, Oder Chiou <oder_chiou@realtek.com> wrote:
> > On Fri, Jul 21, 2017 at 04:00:47PM +0800, Oder Chiou wrote:
> > > The patch uses the local variable to get the data from SPI device to
> > > prevent to get all zero data.
> >
> > How do you end up with all zero data from reading directly into rxbuf?
> >
> While the "runtime->dma_area" put into the rxbuf directly on the Intel
> platform, it seemed that had the limitation to let the memory cannot be
> written the data using the driver of the SPI controller. We verified the
> original code on the platforms of Nvidia and Rockchip, and these are
> working fine.
>
next prev parent reply other threads:[~2017-07-25 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 8:00 [PATCH] ASoC: rt5514: Use the local variable to get the data from SPI device Oder Chiou
2017-07-21 10:51 ` Mark Brown
[not found] ` <7EB0DE829A537248AF2ED30C97D12694023B5FB9@RTITMBSV02.realtek.com.tw>
2017-07-25 14:47 ` Hsin-yu Chao [this message]
2017-07-28 13:59 ` Mark Brown
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=CANyK0SmAVH2GBBA_69D-omT_pJuHA_v2oE9ExbPYEe_WbFxi9Q@mail.gmail.com \
--to=hychao@google.com \
--cc=albertchen@realtek.com \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=broonie@kernel.org \
--cc=flove@realtek.com \
--cc=jack.yu@realtek.com \
--cc=lgirdwood@gmail.com \
--cc=oder_chiou@realtek.com \
--cc=shumingf@realtek.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;
as well as URLs for NNTP newsgroup(s).