From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Yann Sionneau <ysionneau@kalrayinc.com>, barebox@lists.infradead.org
Cc: Jonathan Borne <jborne@kalrayinc.com>,
Julian Vetter <jvetter@kalrayinc.com>,
Jules Maselbas <jmaselbas@zdiv.net>
Subject: Re: [PATCH 4/4] mci: dwcmshc-sdhci: add support for Kalray Coolidge v2 SoC eMMC controller
Date: Thu, 29 Feb 2024 17:19:17 +0100 [thread overview]
Message-ID: <213af923-0b5f-4a49-a982-a7a40ef1c25a@pengutronix.de> (raw)
In-Reply-To: <20240229155700.17443-4-ysionneau@kalrayinc.com>
Hello Yann,
On 29.02.24 16:57, Yann Sionneau wrote:
> Kalray Coolidge v2 SoC eMMC controller needs static tx delay tuning even
> for basic standard or high speed modes.
>
> This patch also adds possibility to do some vendor specific tuning
> in set_ios().
> This will be needed for Coolidge v2 for >50 MHz speeds and HS200/HS400
> modes.
>
> Signed-off-by: Yann Sionneau <ysionneau@kalrayinc.com>
> ---
> drivers/mci/dwcmshc-sdhci.c | 40 +++++++++++++++++++++++++++++++++++++
> 1 file changed, 40 insertions(+)
>
> diff --git a/drivers/mci/dwcmshc-sdhci.c b/drivers/mci/dwcmshc-sdhci.c
> index d9c51752db..5017a1f56e 100644
> --- a/drivers/mci/dwcmshc-sdhci.c
> +++ b/drivers/mci/dwcmshc-sdhci.c
> @@ -9,11 +9,16 @@
> #include <dma.h>
> #include <malloc.h>
> #include <mci.h>
> +#include <of_device.h>
> #include <linux/err.h>
> #include <linux/clk.h>
>
> #include "sdhci.h"
>
> +#define tx_delay_static_cfg(delay) (delay << 5)
> +#define tx_tuning_clk_sel(delay) (delay)
> +
> +#define DWCMSHC_GPIO_OUT 0x34 /* offset from vendor specific area */
> #define CARD_STATUS_MASK (0x1e00)
> #define CARD_STATUS_TRAN (4 << 9)
>
> @@ -22,6 +27,13 @@ static int do_send_cmd(struct mci_host *mci, struct mci_cmd *cmd, struct mci_dat
> struct dwcmshc_host {
> struct mci_host mci;
> struct sdhci sdhci;
> + int vendor_specific_area;
> + const struct dwcmshc_callbacks *cb;
> +};
> +
> +struct dwcmshc_callbacks {
> + void (*init)(struct mci_host *mci, struct device *dev);
Why is dev needed? There's already mci->hw_dev and mci->mci->dev
> + void (*set_ios)(struct mci_host *mci, struct mci_ios *ios);
You don't actually use set_ios. But I assume you intend to add in future?
Maybe add it when it's actually needed?
> +static void dwcmshc_coolidgev2_init(struct mci_host *mci, struct device *dev)
> +{
> + struct dwcmshc_host *host = priv_from_mci_host(mci);
> +
> + // configure TX delay to set correct setup/hold for Coolidge V2
Nite: If you are going to send v2, please change into /* */ comments
for uniformity.
Cheers,
Ahmad
> + sdhci_write32(&host->sdhci,
> + host->vendor_specific_area + DWCMSHC_GPIO_OUT,
> + tx_delay_static_cfg(0xf) | tx_tuning_clk_sel(4));
> +}
> +
> +struct dwcmshc_callbacks kalray_coolidgev2_callbacks = {
> + .init = dwcmshc_coolidgev2_init,
> +};
> +
> static struct of_device_id dwcmshc_dt_ids[] = {
> { .compatible = "snps,dwcmshc-sdhci", },
> + { .compatible = "kalray,coolidge-v2-dwcmshc-sdhci", .data = &kalray_coolidgev2_callbacks },
> { }
> };
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2024-02-29 16:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 15:56 [PATCH 1/4] mci: dwcmshc-sdhci: Remove superfluous call to sdhci_enable_v4_mode Yann Sionneau
2024-02-29 15:56 ` [PATCH 2/4] mci: dwcmshc-sdhci: Fix f_max computation Yann Sionneau
2024-02-29 16:19 ` Ahmad Fatoum
2024-02-29 15:56 ` [PATCH 3/4] mci: sdhci: add register define for P_VENDOR_SPECIFIC_AREA Yann Sionneau
2024-02-29 15:57 ` [PATCH 4/4] mci: dwcmshc-sdhci: add support for Kalray Coolidge v2 SoC eMMC controller Yann Sionneau
2024-02-29 16:19 ` Ahmad Fatoum [this message]
2024-02-29 16:31 ` Yann Sionneau
2024-03-01 7:49 ` Ahmad Fatoum
2024-03-04 9:18 ` (subset) [PATCH 1/4] mci: dwcmshc-sdhci: Remove superfluous call to sdhci_enable_v4_mode Sascha Hauer
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=213af923-0b5f-4a49-a982-a7a40ef1c25a@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=jborne@kalrayinc.com \
--cc=jmaselbas@zdiv.net \
--cc=jvetter@kalrayinc.com \
--cc=ysionneau@kalrayinc.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