On 08/30, Ritesh Harjani wrote: > On 8/26/2016 3:57 AM, Stephen Boyd wrote: > >On 08/24, Ritesh Harjani wrote: > >>This adds support for sdhc-msm controllers to get supported > >>clk-rates from DT. sdhci-msm would need it's own set_clock > >>ops to be implemented. For this, supported clk-rates needs > >>to be populated in sdhci_msm_pltfm_data. > >> > >>Signed-off-by: Ritesh Harjani <riteshh@xxxxxxxxxxxxxx> > >>--- > > > >Please include the DT binding review list in binding updates. > > > >> .../devicetree/bindings/mmc/sdhci-msm.txt | 1 + > >> drivers/mmc/host/sdhci-msm.c | 60 ++++++++++++++++++++++ > >> 2 files changed, 61 insertions(+) > >> > >>diff --git a/Documentation/devicetree/bindings/mmc/sdhci-msm.txt b/Documentation/devicetree/bindings/mmc/sdhci-msm.txt > >>index 485483a..6a83b38 100644 > >>--- a/Documentation/devicetree/bindings/mmc/sdhci-msm.txt > >>+++ b/Documentation/devicetree/bindings/mmc/sdhci-msm.txt > >>@@ -17,6 +17,7 @@ Required properties: > >> "iface" - Main peripheral bus clock (PCLK/HCLK - AHB Bus clock) (required) > >> "core" - SDC MMC clock (MCLK) (required) > >> "bus" - SDCC bus voter clock (optional) > >>+- clk-rates: Array of supported GCC clock frequencies for sdhc, Units - Hz. > >> > > > >Why not use OPPv2 binding for this? We already have a way to > >express frequencies for devices with that binding, and we'll need > >to attach voltages to those frequencies at some point in the > >future if we want to handle DVFS on these devices. > > > OPPv2 may not work out in this case. This was also discussed at [1]. > These clk-rates are not as per voltage points(or any OPP) but as per > bus speed mode request from higher layer. > That post you link to had a response from Andy that echoed the same sentiment and then no reply. Are they a set of frequencies the device can operate at? Yes. Do they have associated voltages that aren't expressed in this patch? Yes. Perhaps I've missed something though and the index of the array of rates corresponds to some bus speed mode? That isn't clearly expressed in the binding. Do the frequencies come from some spec for those bus speed modes? Either way, I'd like to understand why we need to put frequency tables into DT (hint: the commit text should explain that). -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
