From: Kalle Valo <kvalo@codeaurora.org>
To: Pkshih <pkshih@realtek.com>
Cc: "tony0620emma\@gmail.com" <tony0620emma@gmail.com>,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>, DeanKu <ku920601@realtek.com>,
Bernie Huang <phhuang@realtek.com>, Shaofu <shaofu@realtek.com>,
Steven Ting <steventing@realtek.com>,
Kevin Yang <kevin_yang@realtek.com>
Subject: Re: [PATCH 6/7] rtw88: 8822c: add CFO tracking
Date: Mon, 12 Apr 2021 14:47:49 +0300 [thread overview]
Message-ID: <87mtu3lo62.fsf@codeaurora.org> (raw)
In-Reply-To: <6ea1eb17f2a64fd0954b9d4060da12f0@realtek.com> (pkshih@realtek.com's message of "Mon, 12 Apr 2021 08:11:09 +0000")
Pkshih <pkshih@realtek.com> writes:
>> -----Original Message-----
>> From: kvalo=codeaurora.org@mg.codeaurora.org
>> [mailto:kvalo=codeaurora.org@mg.codeaurora.org] On
>> Behalf Of Kalle Valo
>> Sent: Sunday, April 11, 2021 5:20 PM
>> To: Pkshih
>> Cc: tony0620emma@gmail.com; linux-wireless@vger.kernel.org; DeanKu;
>> Bernie Huang; Shaofu; Steven Ting;
>> Kevin Yang
>> Subject: Re: [PATCH 6/7] rtw88: 8822c: add CFO tracking
>>
>> Ping-Ke Shih <pkshih@realtek.com> wrote:
>>
>> > From: Po-Hao Huang <phhuang@realtek.com>
>> >
>> > Add CFO tracking mechanism to mitigate the effect of oscillator
>> > frequency discrepancy.
>> >
>> > Signed-off-by: Po-Hao Huang <phhuang@realtek.com>
>> > Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
>>
>> What's CFO? I need to understand the commit log, so please write it so that any
>> engineer working with wireless understands it.
>>
>
> CFO tracking, which stands for central frequency offset tracking, is used to
> adjust oscillator to align central frequency of connected AP. Then, we can
> have better performance.
>
> Should I resend this patch to explain CFO?
Yes, please send a new version with an updated commit log.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2021-04-12 11:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 5:42 [PATCH 0/7] rtw88: add some fixes and 8822c features Ping-Ke Shih
2021-03-19 5:42 ` [PATCH 1/7] rtw88: add flush hci support Ping-Ke Shih
2021-04-11 9:24 ` Kalle Valo
2021-03-19 5:42 ` [PATCH 2/7] rtw88: follow the AP basic rates for tx mgmt frame Ping-Ke Shih
2021-04-11 9:21 ` Kalle Valo
2021-04-12 8:11 ` Pkshih
2021-04-12 11:46 ` Kalle Valo
2021-04-15 4:05 ` Pkshih
2021-04-22 3:27 ` Pkshih
2021-05-19 5:59 ` Pkshih
2021-03-19 5:42 ` [PATCH 3/7] rtw88: fix DIG min setting Ping-Ke Shih
2021-03-19 5:42 ` [PATCH 4/7] rtw88: 8822c: update tx power limit table to RF v40.1 Ping-Ke Shih
2021-04-11 9:25 ` Kalle Valo
2021-03-19 5:42 ` [PATCH 5/7] rtw88: 8822c: add LC calibration for RTL8822C Ping-Ke Shih
2021-04-11 9:27 ` Kalle Valo
2021-03-19 5:42 ` [PATCH 6/7] rtw88: 8822c: add CFO tracking Ping-Ke Shih
2021-04-11 9:19 ` Kalle Valo
2021-04-12 8:11 ` Pkshih
2021-04-12 11:47 ` Kalle Valo [this message]
2021-04-15 5:02 ` Pkshih
2021-03-19 5:42 ` [PATCH 7/7] rtw88: coex: fix A2DP stutters while WL busy + WL scan Ping-Ke Shih
2021-04-11 9:28 ` 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=87mtu3lo62.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=kevin_yang@realtek.com \
--cc=ku920601@realtek.com \
--cc=linux-wireless@vger.kernel.org \
--cc=phhuang@realtek.com \
--cc=pkshih@realtek.com \
--cc=shaofu@realtek.com \
--cc=steventing@realtek.com \
--cc=tony0620emma@gmail.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;
as well as URLs for NNTP newsgroup(s).