From: b32955@freescale.com (Huang Shijie)
To: linux-arm-kernel@lists.infradead.org
Subject: GPMI-NAND Status?
Date: Tue, 9 Aug 2011 14:36:19 +0800 [thread overview]
Message-ID: <4E40D563.2090202@freescale.com> (raw)
In-Reply-To: <CAHMSPgMdBmmNG41_QgGivSb+M1rG5nqJjtveyZueKHHJrA8vzA@mail.gmail.com>
Hi Koen:
> Hi,
>
> On Mon, Aug 8, 2011 at 12:37 PM, Huang Shijie<b32955@freescale.com> wrote:
>> Hi,
>>> On my target, the mxs-dma is working for sdio until the gpmi-nand
>>> gives a timeout. After that the dma for sdio is *not fully* working
>>> anymore.
>>>
>> We need more log in following aspects:
>> [1] apbh-dma registers
>> [2] clk registers
>> [3] gpmi registers
>>
>> Please git-apply the patch in the attachment.
>> It will print out more DMA information WHEN dma-timeout occur.
> Don't get it. What exactly are you trying to dump?
> This patch dumps CTRL0, CTRL1, CTRL2, DEVSEL but also some registers
> of APBH channel0 which is reserved....
sorry, I intended to print out the channel 4(NAND_DEVICE0).
I want to know that:
When the dma timeout occurs, whether it caused by the GPMI or by the
DMA itself.
Please try the new patch.
Best Regards
Huang Shijie
> Then it prints some debug info on channel 1 (ssp1) and then alle
> channel 2 register except the debug register (ssp2 = not used here).
>
> What info do you need?
>
> Br,
> Koen
>
>> Best Regards
>> Huang Shijie
>>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
next prev parent reply other threads:[~2011-08-09 6:36 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 13:51 GPMI-NAND Status? Wolfram Sang
2011-08-08 6:21 ` Huang Shijie
2011-08-08 9:19 ` Koen Beel
2011-08-08 10:37 ` Huang Shijie
2011-08-08 12:42 ` Koen Beel
2011-08-09 6:36 ` Huang Shijie [this message]
2011-08-09 7:58 ` Koen Beel
2011-08-09 8:18 ` Huang Shijie
2011-08-09 8:25 ` Koen Beel
2011-08-09 5:11 ` Huang Shijie
2011-08-09 6:25 ` Koen Beel
2011-08-09 6:40 ` Huang Shijie
2011-08-09 9:45 ` Wolfram Sang
2011-08-09 9:35 ` Wolfram Sang
2011-08-09 10:54 ` Huang Shijie
2011-08-09 20:42 ` Wolfram Sang
2011-08-08 9:12 ` Huang Shijie
2011-08-09 9:19 ` Wolfram Sang
2011-08-09 10:41 ` Huang Shijie
2011-08-09 11:36 ` Lothar Waßmann
2011-08-14 8:11 ` Ivan Djelic
2011-08-14 18:31 ` Wolfram Sang
2011-08-15 5:41 ` Lothar Waßmann
2011-08-15 6:30 ` Lin Tony-B19295
2011-08-15 8:41 ` Ivan Djelic
2011-08-15 8:29 ` Ivan Djelic
2011-08-15 9:31 ` Lothar Waßmann
2011-08-15 12:54 ` Ivan Djelic
2011-08-15 13:37 ` Lothar Waßmann
2011-08-15 16:34 ` Artem Bityutskiy
2011-08-15 16:18 ` Artem Bityutskiy
2011-08-15 16:22 ` Artem Bityutskiy
2011-08-15 16:57 ` Ivan Djelic
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=4E40D563.2090202@freescale.com \
--to=b32955@freescale.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).