ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: ath10k@lists.infradead.org,
	 "open list:DRM DRIVER FOR MSM ADRENO GPU"
	<linux-arm-msm@vger.kernel.org>
Subject: Re: ath10k-firmware: WCN3990: Add board file for the Qualcomm Robotics RB1 platform
Date: Thu, 07 Dec 2023 16:52:58 +0200	[thread overview]
Message-ID: <87o7f2njxx.fsf@kernel.org> (raw)
In-Reply-To: <CAA8EJpoMoLTLz9UOFt4gwHcnyLVzBoUhAeRSs_Tkz=d3zzq_HA@mail.gmail.com> (Dmitry Baryshkov's message of "Fri, 25 Aug 2023 00:50:03 +0300")

Dmitry Baryshkov <dmitry.baryshkov@linaro.org> writes:

> Hello Kalle,
>
> We'd like to ask for inclusion of the board file for the Qualcomm
> Robotics RB1 platform. It is
> an IOT platform manufactured by Thundercomm, using the Snapdragon QRB2210 SoC.
>
> Following the questions from the ath10k wiki page:
>
> * description for what hardware this is
> - It is an QRB2210-based platform (QRB2210)
> - It uses wcn3990 chip as a WiFi and BT radio
> - For the reference:
>
> ath10k_snoc c800000.wifi: qmi chip_id 0x120 chip_family 0x4007
> board_id 0xff soc_id 0x40670000
> ath10k_snoc c800000.wifi: qmi fw_version 0x337302d3 fw_build_timestamp
> 2023-01-06 01:50 fw_build_id
> QC_IMAGE_VERSION_STRING=WLAN.HL.3.3.7.c2-00723-QCAHLSWMTPLZ-1
> ath10k_snoc c800000.wifi: wcn3990 hw1.0 target 0x00000008 chip_id
> 0x00000000 sub 0000:0000
> ath10k_snoc c800000.wifi: kconfig debug 0 debugfs 0 tracing 0 dfs 0 testmode 0
> ath10k_snoc c800000.wifi: firmware ver  api 5 features
> wowlan,mgmt-tx-by-reference,non-bmi crc32 b3d4b790
> ath10k_snoc c800000.wifi: htt-ver 3.114 wmi-op 4 htt-op 3 cal file
> max-sta 32 raw 0 hwcrypto 1
>
> * origin of the board file
>   - It comes from the firmware package provided by Thundercomm for
> redistribution.
>
> * ids to be used with the board file
>
> bus=snoc,qmi-board-id=ff,qmi-chip-id=120,variant=Thundercomm_RB1
>
> Note, the device comes with the board_id not changed from 0xff.
> Following the example of existing boards we are adding the
> calibration variant.
>
> * md5sum of each new board file to add
>
> $ md5sum *
> 5003239259d8cb68097a941dde86dcc7
> bus=snoc,qmi-board-id=ff,qmi-chip-id=120,variant=Thundercomm_RB1.bin
>
> $ sha256sum *
> 0eeffb43040b216b0f3210b8db69e4558844dd9df52caf9c25f56a79401f442c
> bus=snoc,qmi-board-id=ff,qmi-chip-id=120,variant=Thundercomm_RB1.bin

Thanks, added to WCN3990/hw1.0/board-2.bin:

New:
bus=snoc,qmi-board-id=ff,qmi-chip-id=120,variant=Thundercomm_RB1

Changed:


Deleted:

1 board image(s) added, 0 changed, 0 deleted, 22 in total

https://github.com/kvalo/ath10k-firmware/commit/7d5e852d125d4ca3feba6a3fff9d04a0e488e584

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches


      reply	other threads:[~2023-12-07 14:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-24 21:50 ath10k-firmware: WCN3990: Add board file for the Qualcomm Robotics RB1 platform Dmitry Baryshkov
2023-12-07 14:52 ` Kalle Valo [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=87o7f2njxx.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath10k@lists.infradead.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=linux-arm-msm@vger.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