dt-bindings: mmc: brcm,sdhci-brcmstb: Add support for 74165b0
Subsystems (5)
Kamal Dasu
maintainerPATCH 1/2 dt-bindings: mmc: brcm,sdhci-brcmstb: Add support for 74165b0
From: Kamal Dasu <[email protected]>
With newer sdio controller core used for 74165b0 we need to update the compatibility with "brcm,bcm74165b0-sdhci".
--- .../devicetree/bindings/mmc/brcm,sdhci-brcmstb.yaml | 5 +++++ 1 file changed, 5 insertions(+)
Documentation/devicetree/bindings/mmc/brcm,sdhci-brcmstb.yaml +5 -0
@@ -13,6 +13,11 @@ maintainers: properties: compatible: oneOf: + - items: + - enum: + - brcm,bcm74165b0-sdhci + - const: brcm,bcm74165-sdhci + - const: brcm,sdhci-brcmstb - items: - enum: - brcm,bcm7216-sdhci
Signature · 1 line
2.17.1
Kamal Dasu
maintainerPATCH 2/2 mmc: add new sdhci reset sequence for brcm 74165b0
From: Kamal Dasu <[email protected]>
74165b0 shall use a new sdio controller core version which requires a different reset sequence. For core reset we use sdhci_reset. For CMD and/or DATA reset added a new function to also enable SDCHI clocks SDHCI_CLOCK_CARD_EN SDHCI_CLOCK_INT_EN along with the SDHCI_RESET_CMD and/or SDHCI_RESET_DATA fields.
--- drivers/mmc/host/sdhci-brcmstb.c | 69 +++++++++++++++++++++++++++++--- 1 file changed, 64 insertions(+), 5 deletions(-)
drivers/mmc/host/sdhci-brcmstb.c +64 -5
@@ -44,8 +44,13 @@ struct brcmstb_match_priv {static inline void enable_clock_gating (struct sdhci_host *host) { +struct sdhci_pltfm_host *pltfm_host =sdhci_priv (host); +struct sdhci_brcmstb_priv *priv =sdhci_pltfm_priv (pltfm_host);u32 reg; +if (!(priv->flags &BRCMSTB_PRIV_FLAGS_GATE_CLOCK )) +return ; + reg =sdhci_readl (host,SDHCI_VENDOR ); reg |=SDHCI_VENDOR_GATE_SDCLK_EN ;sdhci_writel (host, reg,SDHCI_VENDOR );
@@ -53,14 +58,54 @@ static inline void enable_clock_gating(struct sdhci_host *host)static void brcmstb_reset (struct sdhci_host *host,u8 mask) { -struct sdhci_pltfm_host *pltfm_host =sdhci_priv (host); -struct sdhci_brcmstb_priv *priv =sdhci_pltfm_priv (pltfm_host); -sdhci_and_cqhci_reset (host, mask);/* Reset will clear this, so re-enable it */ -if (priv->flags &BRCMSTB_PRIV_FLAGS_GATE_CLOCK ) -enable_clock_gating (host); +enable_clock_gating (host); +} + +static void brcmstb_sdhci_reset_cmd_data (struct sdhci_host *host,u8 mask) +{ +ktime_t timeout; +u32 reg; +u32 new_mask = (mask & (SDHCI_RESET_CMD |SDHCI_RESET_DATA )) <<24 ; + + new_mask |=SDHCI_CLOCK_CARD_EN |SDHCI_CLOCK_INT_EN ; + reg =sdhci_readl (host,SDHCI_CLOCK_CONTROL ); +sdhci_writel (host, reg | new_mask,SDHCI_CLOCK_CONTROL ); + +/* Wait max 10 ms */ + timeout =ktime_add_ms (ktime_get (),10 ); + +/* hw clears the bit when it's done */ +while (1 ) { +bool timedout =ktime_after (ktime_get (), timeout); + +if (!(sdhci_readb (host,SDHCI_SOFTWARE_RESET ) & mask)) +break ; +if (timedout) { +pr_err ("%s: Reset 0x%x never completed.\n" , +mmc_hostname (host->mmc), (int )mask); +sdhci_err_stats_inc (host,CTRL_TIMEOUT ); +sdhci_dumpregs (host); +return ; + } +udelay (10 ); + } +} + +static void brcmstb_reset_74165b0 (struct sdhci_host *host,u8 mask) +{ +/* take care of RESET_ALL as usual */ +if (mask &SDHCI_RESET_ALL ) +sdhci_and_cqhci_reset (host,SDHCI_RESET_ALL ); + +/* cmd and/or data treated differently on this core */ +if (mask & (SDHCI_RESET_CMD |SDHCI_RESET_DATA )) +brcmstb_sdhci_reset_cmd_data (host, mask); + +/* Reset will clear this, so re-enable it */ +enable_clock_gating (host); }static void sdhci_brcmstb_hs400es (struct mmc_host *mmc,struct mmc_ios *ios)
@@ -162,6 +207,13 @@ static struct sdhci_ops sdhci_brcmstb_ops_7216 = { .set_uhs_signaling = sdhci_brcmstb_set_uhs_signaling, }; +static const struct sdhci_ops sdhci_brcmstb_ops_74165b0 = { + .set_clock = sdhci_brcmstb_set_clock, + .set_bus_width = sdhci_set_bus_width, + .reset = brcmstb_reset_74165b0, + .set_uhs_signaling = sdhci_brcmstb_set_uhs_signaling, +}; +static struct brcmstb_match_priv match_priv_7425 = { .flags =BRCMSTB_MATCH_FLAGS_NO_64BIT |BRCMSTB_MATCH_FLAGS_BROKEN_TIMEOUT ,
@@ -179,10 +231,17 @@ static const struct brcmstb_match_priv match_priv_7216 = { .ops = &sdhci_brcmstb_ops_7216, }; +static const struct brcmstb_match_priv match_priv_74165b0 = { + .flags =BRCMSTB_MATCH_FLAGS_HAS_CLOCK_GATE , + .hs400es = sdhci_brcmstb_hs400es, + .ops = &sdhci_brcmstb_ops_74165b0, +}; +static const struct of_device_id __maybe_unused sdhci_brcm_of_match[] = { { .compatible ="brcm,bcm7425-sdhci" , .data = &match_priv_7425 }, { .compatible ="brcm,bcm7445-sdhci" , .data = &match_priv_7445 }, { .compatible ="brcm,bcm7216-sdhci" , .data = &match_priv_7216 }, + { .compatible ="brcm,bcm74165b0-sdhci" , .data = &match_priv_74165b0 }, {}, };
Signature · 1 line
2.17.1
kernel test robot
build botRe: [PATCH 2/2] mmc: add new sdhci reset sequence for brcm 74165b0
kernel test robot noticed the following build warnings:
Hi Kamal,
kernel test robot noticed the following build warnings:
[auto build test WARNING on robh/for-next]
[also build test WARNING on soc/for-next linus/master v6.7-rc4 next-20231208] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Kamal-Dasu/mmc-add-new-sdhci-reset-sequence-for-brcm-74165b0/20231209-042222 base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next patch link: https://lore.kernel.org/r/20231208202108.7468-2-kamal.dasu%40broadcom.com patch subject: [PATCH 2/2] mmc: add new sdhci reset sequence for brcm 74165b0 config: arc-randconfig-001-20231209 (https://download.01.org/0day-ci/archive/20231209/[email protected]/config) compiler: arceb-elf-gcc (GCC) 13.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231209/[email protected]/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <[email protected]>
| Closes: https://lore.kernel.org/oe-kbuild-all/[email protected]/
All warnings (new ones prefixed by >>):
>> drivers/mmc/host/sdhci-brcmstb.c:237:16: warning: initialization discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
237 | .ops = &sdhci_brcmstb_ops_74165b0,
| ^vim +/const +237 drivers/mmc/host/sdhci-brcmstb.c
233
234 static const struct brcmstb_match_priv match_priv_74165b0 = {
235 .flags = BRCMSTB_MATCH_FLAGS_HAS_CLOCK_GATE,
236 .hs400es = sdhci_brcmstb_hs400es,
> 237 .ops = &sdhci_brcmstb_ops_74165b0,
238 };
239
Signature · 2 lines
0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
kernel test robot
build botRe: [PATCH 2/2] mmc: add new sdhci reset sequence for brcm 74165b0
In reply to Kamal Dasukernel test robot noticed the following build errors:
Hi Kamal,
kernel test robot noticed the following build errors:
[auto build test ERROR on robh/for-next]
[also build test ERROR on soc/for-next linus/master v6.7-rc4 next-20231208] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Kamal-Dasu/mmc-add-new-sdhci-reset-sequence-for-brcm-74165b0/20231209-042222 base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next patch link: https://lore.kernel.org/r/20231208202108.7468-2-kamal.dasu%40broadcom.com patch subject: [PATCH 2/2] mmc: add new sdhci reset sequence for brcm 74165b0 config: arm-defconfig (https://download.01.org/0day-ci/archive/20231209/[email protected]/config) compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project.git f28c006a5895fc0e329fe15fead81e37457cb1d1) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231209/[email protected]/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <[email protected]>
| Closes: https://lore.kernel.org/oe-kbuild-all/[email protected]/
All errors (new ones prefixed by >>):
>> drivers/mmc/host/sdhci-brcmstb.c:237:9: error: initializing 'struct sdhci_ops *' with an expression of type 'const struct sdhci_ops *' discards qualifiers [-Werror,-Wincompatible-pointer-types-discards-qualifiers]
.ops = &sdhci_brcmstb_ops_74165b0,
^~~~~~~~~~~~~~~~~~~~~~~~~~1 error generated.
vim +237 drivers/mmc/host/sdhci-brcmstb.c
233
234 static const struct brcmstb_match_priv match_priv_74165b0 = {
235 .flags = BRCMSTB_MATCH_FLAGS_HAS_CLOCK_GATE,
236 .hs400es = sdhci_brcmstb_hs400es,
> 237 .ops = &sdhci_brcmstb_ops_74165b0,
238 };
239
Signature · 2 lines
0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
kernel test robot
build botRe: [PATCH 2/2] mmc: add new sdhci reset sequence for brcm 74165b0
In reply to Kamal Dasukernel test robot noticed the following build warnings:
Hi Kamal,
kernel test robot noticed the following build warnings:
[auto build test WARNING on robh/for-next]
[also build test WARNING on soc/for-next linus/master v6.7-rc4 next-20231208] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Kamal-Dasu/mmc-add-new-sdhci-reset-sequence-for-brcm-74165b0/20231209-042222 base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next patch link: https://lore.kernel.org/r/20231208202108.7468-2-kamal.dasu%40broadcom.com patch subject: [PATCH 2/2] mmc: add new sdhci reset sequence for brcm 74165b0 config: nios2-randconfig-r133-20231209 (https://download.01.org/0day-ci/archive/20231209/[email protected]/config) compiler: nios2-linux-gcc (GCC) 13.2.0 reproduce: (https://download.01.org/0day-ci/archive/20231209/[email protected]/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <[email protected]>
| Closes: https://lore.kernel.org/oe-kbuild-all/[email protected]/
sparse warnings: (new ones prefixed by >>)
>> drivers/mmc/host/sdhci-brcmstb.c:237:17: sparse: sparse: incorrect type in initializer (different modifiers) @@ expected struct sdhci_ops *ops @@ got struct sdhci_ops const * @@
drivers/mmc/host/sdhci-brcmstb.c:237:17: sparse: expected struct sdhci_ops *ops
drivers/mmc/host/sdhci-brcmstb.c:237:17: sparse: got struct sdhci_ops const *
vim +237 drivers/mmc/host/sdhci-brcmstb.c
233
234 static const struct brcmstb_match_priv match_priv_74165b0 = {
235 .flags = BRCMSTB_MATCH_FLAGS_HAS_CLOCK_GATE,
236 .hs400es = sdhci_brcmstb_hs400es,
> 237 .ops = &sdhci_brcmstb_ops_74165b0,
238 };
239
Signature · 2 lines
0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Quoted 15 lines · Kamal Dasu
From: Kamal Dasu <[email protected]>
With newer sdio controller core used for 74165b0 we need to update the compatibility with "brcm,bcm74165b0-sdhci".
Signed-off-by Kamal Dasu <[email protected]>--- .../devicetree/bindings/mmc/brcm,sdhci-brcmstb.yaml | 5 +++++ 1 file changed, 5 insertions(+)Documentation/devicetree/bindings/mmc/brcm,sdhci-brcmstb.yaml +0
-0
Documentation/devicetree/bindings/mmc/brcm,sdhci-brcmstb.yaml maintainers: · line 19
Quoted 7 lines
Documentation/devicetree/bindings/mmc/brcm,sdhci-brcmstb.yaml +4
-0@@ -13,6 +13,11 @@ maintainers: properties: compatible: oneOf: + - items: + - enum: + - brcm,bcm74165b0-sdhci + - const: brcm,bcm74165-sdhci
What is exactly the difference between bcm74165b0 and bcm74165? Your driver does not use bcm74165, so I wonder what its purpose is.
Few days ago, for different patchset, I was asking "why", because the motivation was not clear from the code. Here you said "we need to", but I would argue: no you do not need to add bcm74165 if it means nothing, thus this commit msg has similar problem. Does not answer why it is done like this.
Best regards,
Krzysztof
Kamal Dasu
maintainerQuoted 29 lines · Krzysztof Kozlowski
Quoted 11 lines · Kamal Dasu
From: Kamal Dasu <[email protected]>
With newer sdio controller core used for 74165b0 we need to update the compatibility with "brcm,bcm74165b0-sdhci".
Signed-off-by Kamal Dasu <[email protected]>--- .../devicetree/bindings/mmc/brcm,sdhci-brcmstb.yaml | 5 +++++ 1 file changed, 5 insertions(+)diff --git
a/Documentation/devicetree/bindings/mmc/brcm,sdhci-brcmstb.yamlb/Documentation/devicetree/bindings/mmc/brcm,sdhci-brcmstb.yamlDocumentation/devicetree/bindings/mmc/brcm,sdhci-brcmstb.yaml maintainers: · line 19
Quoted 11 lines
index
c028039bc477..cec9ff063794100644Documentation/devicetree/bindings/mmc/brcm,sdhci-brcmstb.yaml +4
-0@@ -13,6 +13,11 @@ maintainers: properties: compatible: oneOf: + - items: + - enum: + - brcm,bcm74165b0-sdhci + - const: brcm,bcm74165-sdhciWhat is exactly the difference between bcm74165b0 and bcm74165? Your driver does not use bcm74165, so I wonder what its purpose is.
Quoted 7 lines
Few days ago, for different patchset, I was asking "why", because the motivation was not clear from the code. Here you said "we need to", but I would argue: no you do not need to add bcm74165 if it means nothing, thus this commit msg has similar problem. Does not answer why it is done like this.
I agree it can be removed in this case, it is just a convention that we
have the base chip id without the a0, b0 postfix in general. However since this compatibility is just used by the sdhci core it's not necessary. let me send a v2 version with the change.
Quoted 4 lines
Best regards,
Krzysztof