From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>
Cc: Wright Feng <Wright.Feng@cypress.com>, linux-tegra@vger.kernel.org
Subject: [PATCH v1 0/4] WiFi SDIO fixes and improvements for Acer A500 and Nexus 7
Date: Sun, 23 Aug 2020 17:47:21 +0300 [thread overview]
Message-ID: <20200823144725.28299-1-digetx@gmail.com> (raw)
Hello!
I was debugging WiFi performance problems that I started to notice on
Acer A500 and found couple problems. One discovered problem lays in a
wrong SDIO PINCTRL configuration of A500 device-tree, others are found
in MMC core and brcmfmac driver.
This series fixes the PINCTRL configuration and improves MMC clock setup
of Acer A500 and Nexus 7 WiFi.
Big thanks to Wright Feng of Cypress who indirectly helped me to notice the
PINCTRL bug by showing MMC IOS info of the BCM4329 setup that Wright uses,
it lead me to re-check to the PINCTRL configuration!
Dmitry Osipenko (4):
ARM: tegra: acer-a500: Correct PINCTRL configuration
ARM: tegra: acer-a500: Set WiFi MMC clock rate to 50MHz
ARM: tegra: acer-a500: Use PLLC for WiFi MMC clk parent
ARM: tegra: nexus7: Use PLLC for WiFi MMC clk parent
.../arm/boot/dts/tegra20-acer-a500-picasso.dts | 18 +++++++++++++++---
.../tegra30-asus-nexus7-grouper-common.dtsi | 5 +++++
2 files changed, 20 insertions(+), 3 deletions(-)
--
2.27.0
next reply other threads:[~2020-08-23 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-23 14:47 Dmitry Osipenko [this message]
2020-08-23 14:47 ` [PATCH v1 1/4] ARM: tegra: acer-a500: Correct PINCTRL configuration Dmitry Osipenko
2020-08-23 14:47 ` [PATCH v1 2/4] ARM: tegra: acer-a500: Set WiFi MMC clock rate to 50MHz Dmitry Osipenko
2020-08-23 14:47 ` [PATCH v1 3/4] ARM: tegra: acer-a500: Use PLLC for WiFi MMC clk parent Dmitry Osipenko
2020-08-23 14:47 ` [PATCH v1 4/4] ARM: tegra: nexus7: " Dmitry Osipenko
2020-09-17 10:21 ` [PATCH v1 0/4] WiFi SDIO fixes and improvements for Acer A500 and Nexus 7 Thierry Reding
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=20200823144725.28299-1-digetx@gmail.com \
--to=digetx@gmail.com \
--cc=Wright.Feng@cypress.com \
--cc=jonathanh@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@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).