All of lore.kernel.org
 help / color / mirror / Atom feed
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 v3 0/2] mmc: sdhci-brcmstb: Add support for optional sdio_freq clock
Date: Fri, 20 May 2022 14:31:06 -0400	[thread overview]
Message-ID: <20220520183108.47358-1-kdasu.kdev@gmail.com> (raw)

v3 changes:
- PATCH 1/2 v3
 - Based on review comments reverted to using the 'clock-frequency' field
   in sdhci-brcmstb controller node for the sdio_freq clock 
- PATCH 2/2 v3
  - use devm_clk_get_optional() to get sdio_freq clock
  - look for clock-frequency value if set in the sdhci-brcmstb dt node
  - Added pmops to unprepare, prepare sdio_freq clock on suspend/resume
    in addition to the sdhci_pltfm_suspend/resume()  

v2 changes :
- Added Reviewed-by tag to PATCH v2 1/2
- In PATCH v2 2/2 Used host->mmc->f_max instead of parsing the device
  tree again, /s/clock-frequency/max-frequency in commit message 

v1 Changes :
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.


Kamal Dasu (2):
  dt-bindings: mmc: Add Broadcom optional sdio_freq clock
  mmc: sdhci-brcmstb: Add ability to increase max clock rate for 72116b0

 .../bindings/mmc/brcm,sdhci-brcmstb.yaml      | 32 +++++++--
 drivers/mmc/host/sdhci-brcmstb.c              | 69 ++++++++++++++++++-
 2 files changed, 94 insertions(+), 7 deletions(-)

-- 
2.17.1


WARNING: multiple messages have this Message-ID (diff)
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 v3 0/2] mmc: sdhci-brcmstb: Add support for optional sdio_freq clock
Date: Fri, 20 May 2022 14:31:06 -0400	[thread overview]
Message-ID: <20220520183108.47358-1-kdasu.kdev@gmail.com> (raw)

v3 changes:
- PATCH 1/2 v3
 - Based on review comments reverted to using the 'clock-frequency' field
   in sdhci-brcmstb controller node for the sdio_freq clock 
- PATCH 2/2 v3
  - use devm_clk_get_optional() to get sdio_freq clock
  - look for clock-frequency value if set in the sdhci-brcmstb dt node
  - Added pmops to unprepare, prepare sdio_freq clock on suspend/resume
    in addition to the sdhci_pltfm_suspend/resume()  

v2 changes :
- Added Reviewed-by tag to PATCH v2 1/2
- In PATCH v2 2/2 Used host->mmc->f_max instead of parsing the device
  tree again, /s/clock-frequency/max-frequency in commit message 

v1 Changes :
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.


Kamal Dasu (2):
  dt-bindings: mmc: Add Broadcom optional sdio_freq clock
  mmc: sdhci-brcmstb: Add ability to increase max clock rate for 72116b0

 .../bindings/mmc/brcm,sdhci-brcmstb.yaml      | 32 +++++++--
 drivers/mmc/host/sdhci-brcmstb.c              | 69 ++++++++++++++++++-
 2 files changed, 94 insertions(+), 7 deletions(-)

-- 
2.17.1


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2022-05-20 18:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20 18:31 Kamal Dasu [this message]
2022-05-20 18:31 ` [PATCH v3 0/2] mmc: sdhci-brcmstb: Add support for optional sdio_freq clock Kamal Dasu
2022-05-20 18:31 ` [PATCH v3 1/2] dt-bindings: mmc: Add Broadcom " Kamal Dasu
2022-05-20 18:31   ` Kamal Dasu
2022-05-20 18:31 ` [PATCH v3 2/2] mmc: sdhci-brcmstb: Add ability to increase max clock rate for 72116b0 Kamal Dasu
2022-05-20 18:31   ` Kamal Dasu
2022-05-23 23:09   ` Florian Fainelli
2022-05-23 23:09     ` Florian Fainelli
2022-06-01 12:46 ` [PATCH v3 0/2] mmc: sdhci-brcmstb: Add support for optional sdio_freq clock Ulf Hansson
2022-06-01 12:46   ` Ulf Hansson

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=20220520183108.47358-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.