dmaengine.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peng Ma <peng.ma@nxp.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Vinod Koul <vkoul@kernel.org>,
	"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Fabio Estevam <fabio.estevam@nxp.com>,
	Leo Li <leoyang.li@nxp.com>, Andy Tang <andy.tang@nxp.com>
Subject: RE: [EXT] [BUG BISECT] Net boot fails on VF50 after "dmaengine: fsl-edma: support little endian for edma driver"
Date: Fri, 5 Jul 2019 02:04:20 +0000	[thread overview]
Message-ID: <VI1PR04MB4431E18760FCB6CE32E5717DEDF50@VI1PR04MB4431.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <CAJKOXPdYJKe019CKT=hPRXLejMdZ1KNzxpFh60ruToKOqnAorQ@mail.gmail.com>

Hi Krzysztof,

Got it. Thanks for your help

Best Regards,
Peng
>-----Original Message-----
>From: Krzysztof Kozlowski <krzk@kernel.org>
>Sent: 2019年7月4日 20:57
>To: Peng Ma <peng.ma@nxp.com>
>Cc: Vinod Koul <vkoul@kernel.org>; dmaengine@vger.kernel.org;
>linux-kernel@vger.kernel.org; Fabio Estevam <fabio.estevam@nxp.com>; Leo
>Li <leoyang.li@nxp.com>; Andy Tang <andy.tang@nxp.com>
>Subject: Re: [EXT] [BUG BISECT] Net boot fails on VF50 after "dmaengine:
>fsl-edma: support little endian for edma driver"
>
>Caution: EXT Email
>
>On Thu, 4 Jul 2019 at 04:10, Peng Ma <peng.ma@nxp.com> wrote:
>>
>> Hi Krzysztof,
>>
>> I am sorry, It is my mistake to forget about VF50 used EDMA IP with little
>endian.
>> The Register(CHCFG0 - CHCFG15) of our platform designed as follows:
>> *---------------------------------------------------------------------
>> ----------*
>> |     Offset   | Big endian Register| Little endian Register|
>> |---------------------|--------------------------|-----------------------------|
>> |     0x0     |     CHCFG0    |     CHCFG3      |
>> |---------------------|--------------------------|-----------------------------|
>> |     0x1     |     CHCFG1    |     CHCFG2      |
>> |---------------------|--------------------------|-----------------------------|
>> |     0x2     |     CHCFG2    |     CHCFG1      |
>> |---------------------|--------------------------|-----------------------------|
>> |     0x3     |     CHCFG3    |     CHCFG0      |
>> |---------------------|--------------------------|-----------------------------|
>> |     ...      |        ......     |         ......      |
>> |---------------------|--------------------------|-----------------------------|
>> |     0xC     |     CHCFG12   |     CHCFG15     |
>> |---------------------|--------------------------|-----------------------------|
>> |     0xD     |     CHCFG13   |     CHCFG14     |
>> |---------------------|--------------------------|-----------------------------|
>> |     0xE     |     CHCFG14   |     CHCFG13     |
>> |---------------------|--------------------------|-----------------------------|
>> |     0xF     |     CHCFG15   |     CHCFG12     |
>> *---------------------------------------------------------------------
>> ----------*
>>
>> So we need this patch, I make some changes,Please help me to test
>> attatchment on VF50 board, Thanks.
>
>With the patch VF50 boots fine.
>
>BTW, Colibri VF50 nicely boots from network almost out of the box so it is easy
>to add it to automated tests for simple boot tests. This way you do not have to
>manually test it on such platform...
>
>Best regards,
>Krzysztof

      reply	other threads:[~2019-07-05  2:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-02 12:12 [BUG BISECT] Net boot fails on VF50 after "dmaengine: fsl-edma: support little endian for edma driver" Krzysztof Kozłowski
2019-07-02 12:16 ` Krzysztof Kozlowski
2019-07-02 13:04 ` Fabio Estevam
2019-07-02 13:10   ` Krzysztof Kozlowski
2019-07-02 14:18     ` Fabio Estevam
2019-07-04  2:10 ` [EXT] " Peng Ma
2019-07-04 12:06   ` Fabio Estevam
2019-07-05  2:02     ` Peng Ma
2019-07-04 12:57   ` Krzysztof Kozlowski
2019-07-05  2:04     ` Peng Ma [this message]

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=VI1PR04MB4431E18760FCB6CE32E5717DEDF50@VI1PR04MB4431.eurprd04.prod.outlook.com \
    --to=peng.ma@nxp.com \
    --cc=andy.tang@nxp.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=fabio.estevam@nxp.com \
    --cc=krzk@kernel.org \
    --cc=leoyang.li@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vkoul@kernel.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).