All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Valentin <avalentin@marcant.net>
To: Helmut Schaa <helmut.schaa@googlemail.com>,
	Kalle Valo <kvalo@qca.qualcomm.com>
Cc: ath10k@lists.infradead.org
Subject: Re: ath10k OTP loading issues
Date: Sun, 20 Jul 2014 01:46:24 +0200	[thread overview]
Message-ID: <53CB0350.2060506@marcant.net> (raw)
In-Reply-To: <63dce1c7-0142-4592-b8a1-2b09dce63af3@email.android.com>

Hi!

I noticed that OTP loading works on some ZyXEL NBG6716 devices and some not. I made a diff between both
boot (working non-working) logs. Please take a look at the cpu intr cause:

8c8
< ath10k: boot target cpu intr cause: 0x00000000
---
> ath10k: boot target cpu intr cause: 0x00000008
10c10
< ath10k: boot target cpu intr cause: 0x00000000
---
> ath10k: boot target cpu intr cause: 0x00000008
13,19c13,19
< ath10k: boot init ce src ring id 0 entries 16 base_addr ae4dd000
< ath10k: boot ce dest ring id 1 entries 512 base_addr aef52000
< ath10k: boot ce dest ring id 2 entries 32 base_addr ae4d8000
< ath10k: boot init ce src ring id 3 entries 32 base_addr ae28a000
< ath10k: boot init ce src ring id 4 entries 4096 base_addr ae4e0000
< ath10k: boot init ce src ring id 7 entries 2 base_addr ae4d9000
< ath10k: boot ce dest ring id 7 entries 2 base_addr ae4dc000
---
> ath10k: boot init ce src ring id 0 entries 16 base_addr aef3e000
> ath10k: boot ce dest ring id 1 entries 512 base_addr aeedc000
> ath10k: boot ce dest ring id 2 entries 32 base_addr ae0d1000
> ath10k: boot init ce src ring id 3 entries 32 base_addr aed7d000
> ath10k: boot init ce src ring id 4 entries 4096 base_addr ae7a0000
> ath10k: boot init ce src ring id 7 entries 2 base_addr ae0c2000
> ath10k: boot ce dest ring id 7 entries 2 base_addr ae730000
45c45,48
< ath10k: boot otp execute result 0
---
> ath10k: boot otp execute result 2
> ath10k: otp calibration failed: 2
> ath10k: failed to run otp: -22
> ath10k: Ignoring otp execution failure: -22
66c69
< ath10k: boot target cpu intr cause: 0x00001000
---
> ath10k: boot target cpu intr cause: 0x00001008
68c71
< ath10k: boot target cpu intr cause: 0x00000000
---
> ath10k: boot target cpu intr cause: 0x00000008
74c77
< ath10k: boot target cpu intr cause: 0x00000000
---
> ath10k: boot target cpu intr cause: 0x00000008
76c79
< ath10k: boot target cpu intr cause: 0x00000000
---
> ath10k: boot target cpu intr cause: 0x00000008


And with a cold reset (hacked the code) instead:

6,19c4,12
< ath10k: boot warm reset
< ath10k: boot host cpu intr cause: 0x00000000
< ath10k: boot target cpu intr cause: 0x00000000
< ath10k: boot host cpu intr cause: 0x00000000
< ath10k: boot target cpu intr cause: 0x00000000
< ath10k: boot target reset state: 0x00000800
< ath10k: boot warm reset complete
< ath10k: boot init ce src ring id 0 entries 16 base_addr ae4dd000
< ath10k: boot ce dest ring id 1 entries 512 base_addr aef52000
< ath10k: boot ce dest ring id 2 entries 32 base_addr ae4d8000
< ath10k: boot init ce src ring id 3 entries 32 base_addr ae28a000
< ath10k: boot init ce src ring id 4 entries 4096 base_addr ae4e0000
< ath10k: boot init ce src ring id 7 entries 2 base_addr ae4d9000
< ath10k: boot ce dest ring id 7 entries 2 base_addr ae4dc000
---
> ath10k: boot cold reset
> ath10k: boot cold reset complete
> ath10k: boot init ce src ring id 0 entries 16 base_addr aeed5000
> ath10k: boot ce dest ring id 1 entries 512 base_addr ae112000
> ath10k: boot ce dest ring id 2 entries 32 base_addr aeedf000
> ath10k: boot init ce src ring id 3 entries 32 base_addr ae453000
> ath10k: boot init ce src ring id 4 entries 4096 base_addr ad0c0000
> ath10k: boot init ce src ring id 7 entries 2 base_addr ae49f000
> ath10k: boot ce dest ring id 7 entries 2 base_addr ae258000
25,27d17
< ath10k: boot target indicator 0
< ath10k: boot target indicator 0
< ath10k: boot target indicator 0
45c35,36
< ath10k: boot otp execute result 0
---
> ath10k: boot otp execute result 2
> ath10k: otp stream is empty, using board.bin contents

Do you have an idea?

André

On 17.07.2014 23:44, Helmut Schaa wrote:
>
> On 17. Juli 2014 17:50:36 MESZ, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>> Helmut Schaa <helmut.schaa@googlemail.com> writes:
>>
>>>> But in method 2) otp.bin will fail as there's no data in the OTP
>> area.
>>>> This is expected and that's why we should not run otp.bin at all
>> with
>>>> method 2).
>>> Thanks for clarification Kalle! So, method 2 requires only a
>>> board.bin?
>> Yes. You need to extract the board file from the MTD partition and
>> provide it to ath10k.
> Understood. Will give it a try soon ...
> Helmut


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2014-07-19 23:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-27  8:44 ath10k OTP loading issues André Valentin
2014-06-27 11:01 ` André Valentin
2014-07-02  8:13   ` Kalle Valo
2014-07-02  8:13     ` Kalle Valo
2014-07-02  8:34     ` André Valentin
2014-07-02  8:34       ` André Valentin
2014-07-02  8:56       ` Kalle Valo
2014-07-02  8:56         ` Kalle Valo
2014-07-07 14:51         ` André Valentin
2014-07-02  8:10 ` Kalle Valo
2014-07-02  8:10   ` Kalle Valo
2014-07-07 15:40   ` Helmut Schaa
2014-07-15 21:16     ` Andre Valentin
2014-07-17 14:12       ` Helmut Schaa
2014-07-17 15:03         ` Kalle Valo
2014-07-17 15:45           ` Helmut Schaa
2014-07-17 15:50             ` Kalle Valo
2014-07-17 15:54               ` Andre Valentin
2014-07-17 15:59                 ` Kalle Valo
2014-07-17 21:44               ` Helmut Schaa
2014-07-19 23:46                 ` Andre Valentin [this message]
2014-07-19 23:57                   ` Andre Valentin

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=53CB0350.2060506@marcant.net \
    --to=avalentin@marcant.net \
    --cc=ath10k@lists.infradead.org \
    --cc=helmut.schaa@googlemail.com \
    --cc=kvalo@qca.qualcomm.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.