From: Kalle Valo <kvalo@kernel.org>
To: <andrea.marcer@external.marelli.com>
Cc: <quic_rajkbhag@quicinc.com>, <ath11k@lists.infradead.org>,
<linux-wireless@vger.kernel.org>, <quic_gsaminat@quicinc.com>,
<Dennis.Damore@marelli.com>,
<danilo.sabato@external.marelli.com>,
<giovanni.ciaramitaro@external.marelli.com>
Subject: Re: [PATCH v4 0/4] ath11k: factory test mode support
Date: Wed, 12 Jun 2024 15:06:37 +0300 [thread overview]
Message-ID: <87r0d2nz5e.fsf@kernel.org> (raw)
In-Reply-To: <TYZPR02MB7247209AEA8B450DB501972ACDC02@TYZPR02MB7247.apcprd02.prod.outlook.com> (andrea marcer's message of "Wed, 12 Jun 2024 11:46:55 +0000")
<andrea.marcer@external.marelli.com> writes:
>> Device is booted in factory test mode to calibrate the board.
>> The commands are sent from a userspace application, which is
>> sent to firmware using wmi commands. Firmware will send the
>> response back to the application which stores the calibration
>> data in caldata.bin file. This file will be loaded when the
>> device boots up normally next time.
>
> I would like to calibrate and generate test signals on a QCN9074
> chip using the factory test mode. Which userspace application
> am I supposed to use to perform the calibration and tests?
>
> QCN9074 PCI WLAN.HK.2.5.0.1-03982-QCAHKSWPL_SILICONZ-3
> Linux Kernel 6.1
To my knowledge there are no calibration tools publically available,
unfortunately.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-06-12 12:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 11:46 [PATCH v4 0/4] ath11k: factory test mode support andrea.marcer
2024-06-12 12:06 ` Kalle Valo [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-17 13:59 Raj Kumar Bhagat
2023-05-17 13:59 ` Raj Kumar Bhagat
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=87r0d2nz5e.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=Dennis.Damore@marelli.com \
--cc=andrea.marcer@external.marelli.com \
--cc=ath11k@lists.infradead.org \
--cc=danilo.sabato@external.marelli.com \
--cc=giovanni.ciaramitaro@external.marelli.com \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_gsaminat@quicinc.com \
--cc=quic_rajkbhag@quicinc.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.