ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: ath10k@lists.infradead.org
Subject: ath10k-firmware: QCA4019 hw1.0: Update OpenMesh A62 specific BDFs
Date: Mon, 01 Jul 2019 11:42:59 +0200	[thread overview]
Message-ID: <2312547.eMb23psXx6@bentobox> (raw)


[-- Attachment #1.1.1: Type: text/plain, Size: 1924 bytes --]

[resent of mail from 2019-06-11; seems like @datto.com mail server ate the
 outgoing mails]

Hi,

The OpenMesh A62 AP requires three special BDFs to get the Wi-Fi PHYs working 
(correctly). The  bmi-board-id='s would clash with one of the the IPQ401X 
AP-DK boards because QCA doesn't provide special IDs for customers and seems 
to use the AP-DK board-ids in the wifi firmware to change its behavior. This 
request contains the two files for QCA4019. The QCA9888 one will be submitted 
in a different request.

This update contains:

* add of the antenna gain
* adjustments of the antenna sensitivity (see minCCA power threshold and
  configAddr)
* CTLs for DFS channels

It supersedes https://lkml.kernel.org/r/2795259.fejyDvFH3e@bentobox


Now to the questions from the wiki page [1]:

* description for what hardware this is:

  - it is a QCA4018 based module (based on qcom-ipq4019-ap.dk04.1)
  - one QCA4018 radio is used as 2.4GHz radio
  - one QCA4018 radio is used as 5GHz radio
  - an additional QCA9888 5GHz radio is attached via PCI

* origin of the board file (did you create it yourself or where you
  downloaded)

  - it was created by the ODM and QCA for the OpenMesh A62
  - was provided by the ODM to OpenMesh for this product (this includes
    distribution)
  - it is the latest release from 2018-11-28 (with fix to have
    antennagain at correct position)

* ids to be used with the board file (ATH10K_BD_IE_BOARD_NAME in ath10k)

  - QCA4019 hw1.0

    + bus=ahb,bmi-chip-id=0,bmi-board-id=20,variant=OM-A62
      md5sum: 7642733bfd0c53927209a25440a484e3
    + bus=ahb,bmi-chip-id=0,bmi-board-id=21,variant=OM-A62
      md5sum: ef250f4c8ac057e9995b08e28c482423

* attach the actual board file (board.bin)

  - The name of the files are equal to the id string in the board-2.bin
    (minus the ".bin")

Kind regards,
        Sven

[1] https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles

[-- Attachment #1.1.2: bus=ahb,bmi-chip-id=0,bmi-board-id=20,variant=OM-A62.bin --]
[-- Type: application/x-saturn-rom, Size: 12064 bytes --]

[-- Attachment #1.1.3: bus=ahb,bmi-chip-id=0,bmi-board-id=21,variant=OM-A62.bin --]
[-- Type: application/x-saturn-rom, Size: 12064 bytes --]

[-- 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:[~2019-07-01  9:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-01  9:42 Sven Eckelmann [this message]
2022-01-21 13:12 ` ath10k-firmware: QCA4019 hw1.0: Update OpenMesh A62 specific BDFs Kalle Valo
  -- strict thread matches above, loose matches on Subject: below --
2019-01-10 12:59 Sven Eckelmann
2019-06-28 13:38 ` Kalle Valo

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=2312547.eMb23psXx6@bentobox \
    --to=sven@narfation.org \
    --cc=ath10k@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