From: Dragan Simic <dsimic@manjaro.org>
To: Detlev Casanova <detlev.casanova@collabora.com>
Cc: linux-kernel@vger.kernel.org,
Ulf Hansson <ulf.hansson@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Jaehoon Chung <jh80.chung@samsung.com>,
linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, kernel@collabora.com
Subject: Re: [PATCH v4 4/4] mmc: dw_mmc-rockchip: Add support for rk3576 SoCs
Date: Fri, 23 Aug 2024 09:00:57 +0200 [thread overview]
Message-ID: <26fe259f390a8015c3f08c6dc027711c@manjaro.org> (raw)
In-Reply-To: <20240822212418.982927-5-detlev.casanova@collabora.com>
Hello Detlev,
Please see a comment below.
On 2024-08-22 23:15, Detlev Casanova wrote:
> On rk3576 the tunable clocks are inside the controller itself, removing
> the need for the "ciu-drive" and "ciu-sample" clocks.
>
> That makes it a new type of controller that has its own dt_parse
> function.
>
> Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com>
> ---
> drivers/mmc/host/dw_mmc-rockchip.c | 48 ++++++++++++++++++++++++++----
> 1 file changed, 43 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/mmc/host/dw_mmc-rockchip.c
> b/drivers/mmc/host/dw_mmc-rockchip.c
> index 1458cb5fd5c7..7c8ccf5e71bc 100644
> --- a/drivers/mmc/host/dw_mmc-rockchip.c
> +++ b/drivers/mmc/host/dw_mmc-rockchip.c
> @@ -410,7 +410,7 @@ static int dw_mci_rk3288_execute_tuning(struct
> dw_mci_slot *slot, u32 opcode)
> return ret;
> }
>
> -static int dw_mci_rk3288_parse_dt(struct dw_mci *host)
> +static int dw_mci_common_parse_dt(struct dw_mci *host)
> {
> struct device_node *np = host->dev->of_node;
> struct dw_mci_rockchip_priv_data *priv;
> @@ -420,13 +420,29 @@ static int dw_mci_rk3288_parse_dt(struct dw_mci
> *host)
> return -ENOMEM;
>
> if (of_property_read_u32(np, "rockchip,desired-num-phases",
> - &priv->num_phases))
> + &priv->num_phases))
> priv->num_phases = 360;
>
> if (of_property_read_u32(np, "rockchip,default-sample-phase",
> - &priv->default_sample_phase))
> + &priv->default_sample_phase))
> priv->default_sample_phase = 0;
>
> + host->priv = priv;
> +
> + return 0;
> +}
> +
> +static int dw_mci_rk3288_parse_dt(struct dw_mci *host)
> +{
> + struct dw_mci_rockchip_priv_data *priv;
> + int err;
> +
> + err = dw_mci_common_parse_dt(host);
> + if (err)
> + return err;
> +
> + priv = host->priv;
> +
> priv->drv_clk = devm_clk_get(host->dev, "ciu-drive");
> if (IS_ERR(priv->drv_clk))
> dev_dbg(host->dev, "ciu-drive not available\n");
> @@ -435,13 +451,25 @@ static int dw_mci_rk3288_parse_dt(struct dw_mci
> *host)
> if (IS_ERR(priv->sample_clk))
> dev_dbg(host->dev, "ciu-sample not available\n");
>
> - host->priv = priv;
> -
> priv->internal_phase = false;
>
> return 0;
> }
>
> +static int dw_mci_rk3576_parse_dt(struct dw_mci *host)
> +{
> + struct dw_mci_rockchip_priv_data *priv;
> + int err = dw_mci_common_parse_dt(host);
> + if (err)
> + return err;
> +
> + priv = host->priv;
> +
> + priv->internal_phase = true;
Defining priv, assigning it and using it seems rather redundant,
when all that's needed is simple "host->priv->internal_phase = true"
assignment instead.
> +
> + return 0;
> +}
> +
> static int dw_mci_rockchip_init(struct dw_mci *host)
> {
> int ret, i;
> @@ -483,11 +511,21 @@ static const struct dw_mci_drv_data
> rk3288_drv_data = {
> .init = dw_mci_rockchip_init,
> };
>
> +static const struct dw_mci_drv_data rk3576_drv_data = {
> + .common_caps = MMC_CAP_CMD23,
> + .set_ios = dw_mci_rk3288_set_ios,
> + .execute_tuning = dw_mci_rk3288_execute_tuning,
> + .parse_dt = dw_mci_rk3576_parse_dt,
> + .init = dw_mci_rockchip_init,
> +};
> +
> static const struct of_device_id dw_mci_rockchip_match[] = {
> { .compatible = "rockchip,rk2928-dw-mshc",
> .data = &rk2928_drv_data },
> { .compatible = "rockchip,rk3288-dw-mshc",
> .data = &rk3288_drv_data },
> + { .compatible = "rockchip,rk3576-dw-mshc",
> + .data = &rk3576_drv_data },
> {},
> };
> MODULE_DEVICE_TABLE(of, dw_mci_rockchip_match);
next prev parent reply other threads:[~2024-08-23 7:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 21:15 [PATCH v4 0/4] Add dw_mmc support for rk3576 Detlev Casanova
2024-08-22 21:15 ` [PATCH v4 1/4] dt-bindings: mmc: Add support for rk3576 dw-mshc Detlev Casanova
2024-08-23 7:36 ` Krzysztof Kozlowski
2024-08-22 21:15 ` [PATCH v4 2/4] mmc: dw_mmc-rockchip: Add internal phase support Detlev Casanova
2024-08-23 5:41 ` Dragan Simic
2024-08-23 13:34 ` Detlev Casanova
2024-08-26 14:39 ` Dragan Simic
2024-08-26 18:44 ` Detlev Casanova
2024-08-22 21:15 ` [PATCH v4 3/4] mmc: dw_mmc-rockchip: Skip all phases bigger than 270 degrees Detlev Casanova
2024-08-23 5:45 ` Dragan Simic
2024-08-23 13:59 ` Detlev Casanova
2024-08-26 14:52 ` Dragan Simic
2024-08-22 21:15 ` [PATCH v4 4/4] mmc: dw_mmc-rockchip: Add support for rk3576 SoCs Detlev Casanova
2024-08-23 7:00 ` Dragan Simic [this message]
2024-08-23 13:20 ` Detlev Casanova
2024-08-26 14:07 ` Dragan Simic
2024-08-26 15:45 ` Detlev Casanova
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=26fe259f390a8015c3f08c6dc027711c@manjaro.org \
--to=dsimic@manjaro.org \
--cc=conor+dt@kernel.org \
--cc=detlev.casanova@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jh80.chung@samsung.com \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@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