From: Kamal Dasu <kdasu.kdev@gmail.com>
To: ulf.hansson@linaro.org, robh+dt@kernel.org, krzk+dt@kernel.org,
alcooperx@gmail.com
Cc: f.fainelli@gmail.com, bcm-kernel-feedback-list@broadcom.com,
adrian.hunter@intel.com, linux-mmc@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Kamal Dasu <kdasu.kdev@gmail.com>
Subject: [PATCH 0/2] mmc: sdhci-brcmstb: Add support for optional sdio_freq clock
Date: Fri, 13 May 2022 16:19:05 -0400 [thread overview]
Message-ID: <20220513201907.36470-1-kdasu.kdev@gmail.com> (raw)
Sending the remaining 2 patches separately after implementing review comments
for the patches 3/4 and 4/4 as part of the following:
"mmc: sdhci-brcmstb: host controller clock enhancements"
https://lore.kernel.org/linux-arm-kernel/96fd3054-17b1-db42-9a44-a60485243807@linaro.org/t/
changes are rebased over
git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git refs/heads/next
tested brcm,sdhci-brcmstb.yaml and driver with and without sdio_freq clock.
Al Cooper (1):
mmc: sdhci-brcmstb: Add ability to increase max clock rate for 72116b0
Kamal Dasu (1):
dt-bindings: mmc: Add Broadcom optional sdio_freq clock
.../bindings/mmc/brcm,sdhci-brcmstb.yaml | 25 ++++++++++++----
drivers/mmc/host/sdhci-brcmstb.c | 30 +++++++++++++++++++
2 files changed, 49 insertions(+), 6 deletions(-)
--
2.17.1
next reply other threads:[~2022-05-13 20:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 20:19 Kamal Dasu [this message]
2022-05-13 20:19 ` [PATCH 1/2] dt-bindings: mmc: Add Broadcom optional sdio_freq clock Kamal Dasu
2022-05-17 8:58 ` Krzysztof Kozlowski
2022-05-13 20:19 ` [PATCH 2/2] mmc: sdhci-brcmstb: Add ability to increase max clock rate for 72116b0 Kamal Dasu
2022-05-17 12:49 ` Ulf Hansson
2022-05-20 2:15 ` Alan Cooper
2022-05-20 17:23 ` Kamal Dasu
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=20220513201907.36470-1-kdasu.kdev@gmail.com \
--to=kdasu.kdev@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=alcooperx@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=ulf.hansson@linaro.org \
/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).