public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Larry Finger <Larry.Finger@lwfinger.net>,
	Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: RE: EFUSE in RTW8723DS
Date: Tue, 14 Nov 2023 00:52:23 +0000	[thread overview]
Message-ID: <748b045e7aaa43eb9a7fb83ad924614f@realtek.com> (raw)
In-Reply-To: <f3505110-b76b-4152-8375-37fa3184d3c1@lwfinger.net>



> -----Original Message-----
> From: Larry Finger <larry.finger@gmail.com> On Behalf Of Larry Finger
> Sent: Saturday, November 11, 2023 4:26 AM
> To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> Cc: linux-wireless <linux-wireless@vger.kernel.org>
> Subject: EFUSE in RTW8723DS
> 
> Martin,
> 
> The commit 9be20a822327 ("wifi: rtw88: rtw8723d: Implement RTL8723DS (SDIO)
> efuse parsing") indicates that no additional information is extracted from the
> EFUSE? Is that true, or did I misread the code?

I think the commit is only to read MAC address that is programmed in different
location from PCI interface, and no more information. 

> 
> One problem we are having is that some devices come with zero programming in the
> EFUSE, and even with supplying a valid MAC address, the performance is poor.

One or two years ago, people reported efuse of RTL8192DE (IIRC) isn't programmed
in OpenWRT platform originally. That kind of product, calibration values are stored
in external files instead, and chip is soldered on main board instead of a
separated hardware module such M.2.

Maybe, we can read calibration values programmed in efuse as _default_ values
from another module. This can't yield the best performance, but at least better
than nothing. 

Ping-Ke



  reply	other threads:[~2023-11-14  0:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-10 20:25 EFUSE in RTW8723DS Larry Finger
2023-11-14  0:52 ` Ping-Ke Shih [this message]
2023-11-20 19:55   ` Martin Blumenstingl
2023-11-21 22:47     ` Larry Finger
2023-12-23 10:40       ` Martin Blumenstingl
2023-12-25  3:46         ` Ping-Ke Shih

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=748b045e7aaa43eb9a7fb83ad924614f@realtek.com \
    --to=pkshih@realtek.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.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