From: Marc Gonzalez <marc.w.gonzalez@free.fr>
To: linux-amlogic@lists.infradead.org,
linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com
Cc: Arend van Spriel <aspriel@gmail.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Pierre-Hugues Husson <phh@phh.me>, Arnaud Vrac <avrac@freebox.fr>
Subject: Re: Throughput & CPU usage of WiFi download
Date: Tue, 4 Apr 2023 17:42:19 +0200 [thread overview]
Message-ID: <620b5ce8-8c87-5b45-2389-3eb99e15b8cd@free.fr> (raw)
In-Reply-To: <f2344e2e-2b53-9f57-d15a-25e5b03b3029@free.fr>
On 04/04/2023 14:54, Marc Gonzalez wrote:
> 2) SDIO is clocked higher on vendor system, but could
> lead to instabilities on some boards?
Apparently, I remembered wrong.
For mainline, arch/arm64/boot/dts/amlogic/meson-g12a-sei510.dts
bus-width = <4>;
cap-sd-highspeed;
sd-uhs-sdr50;
max-frequency = <100000000>;
For vendor, common/arch/arm64/boot/dts/amlogic/mesong12a_sei.dtsi
bus-width = <4>;
cap-sd-highspeed;
cap-mmc-highspeed;
max-frequency = <100000000>;
The vendor DTS has the following child node:
sdio {
pinname = "sdio";
ocr_avail = <0x200080>; /**VDD voltage 3.3 ~ 3.4 */
/* max_req_size = <0x20000>; */ /**128KB*/
max_req_size = <0x400>;
card_type = <3>;
/* 3:sdio device(ie:sdio-wifi),
* 4:SD combo (IO+mem) card
*/
dmode = "pio";
};
Thus, it seems that the performance delta comes from driver architecture
and different HW setup, rather than clock difference.
Regards
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2023-04-04 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 12:12 Marc Gonzalez
2023-04-04 12:54 ` [RESEND] " Marc Gonzalez
2023-04-04 13:36 ` Neil Armstrong
2023-04-04 15:42 ` Marc Gonzalez [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=620b5ce8-8c87-5b45-2389-3eb99e15b8cd@free.fr \
--to=marc.w.gonzalez@free.fr \
--cc=aspriel@gmail.com \
--cc=avrac@freebox.fr \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=phh@phh.me \
/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
all inboxes | Powered by JetHome®