ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven.eckelmann@openmesh.com>
To: ath10k@lists.infradead.org
Cc: Kalle Valo <kvalo@codeaurora.org>, shashidhar.lakkavalli@openmesh.com
Subject: Re: QCA4019 firmware: wrong numChain setting for bmi-board 16+17
Date: Fri, 03 Mar 2017 10:05:32 +0100	[thread overview]
Message-ID: <3324801.qozNz1vNlM@bentobox> (raw)
In-Reply-To: <3636841.TTvBqzp5DH@bentobox>


[-- Attachment #1.1: Type: text/plain, Size: 743 bytes --]

On Mittwoch, 8. Februar 2017 11:40:07 CET Sven Eckelmann wrote:
> Hi,
> 
> I've just noticed that the numChain in (ath10k/)QCA4019/hw1.0/board-2.bin is
> wrong in the bus=ahb,bmi-chip-id=0,bmi-board-id=16 and
> bus=ahb,bmi-chip-id=0,bmi-board-id=17 from the linux-firmware and
> ath10k-firmware repository. It is 0x4 for a 2x2 device. This was fixed in
> the QSDK by commit 171b9607fb8cc694ed469a4e29c91af9d92f2971 [1]. It is not
> known to me whether this has an effect when the pre-cal data says that the
> device should use numChain 2.

I was informed that the numChain information is part of the pre-calibration
data. So it is most likely only relevant when you calibrate your board or
don't have pre-calibration data.

Kind regards,
	Sven

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 146 bytes --]

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

      reply	other threads:[~2017-03-03  9:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-08 10:40 QCA4019 firmware: wrong numChain setting for bmi-board 16+17 Sven Eckelmann
2017-03-03  9:05 ` Sven Eckelmann [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=3324801.qozNz1vNlM@bentobox \
    --to=sven.eckelmann@openmesh.com \
    --cc=ath10k@lists.infradead.org \
    --cc=kvalo@codeaurora.org \
    --cc=shashidhar.lakkavalli@openmesh.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