From: Neil Armstrong <neil.armstrong@linaro.org>
To: Lucas Tanure <tanure@linux.com>, Ulf Hansson <ulfh@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jerome Brunet <jbrunet@baylibre.com>,
Kevin Hilman <khilman@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: Brian Masney <bmasney+clk@redhat.com>,
Chuan Liu <chuan.liu@amlogic.com>, Jian Hu <jian.hu@amlogic.com>,
Ronald Claveau <linux-kernel-dev@aliel.fr>,
linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/4] mmc: meson-gx: enable the bus pipeline clock on T7
Date: Thu, 10 Sep 2026 09:13:06 +0200 [thread overview]
Message-ID: <cc06ba9b-c866-4c43-a7d4-e25188b84f22@linaro.org> (raw)
In-Reply-To: <20260905153234.133217-3-tanure@linux.com>
On 9/5/26 17:32, Lucas Tanure wrote:
> On the T7 SoC, the bus path between the SD/eMMC controllers and the
> NIC_MATRIX fabric goes through a pipeline stage inserted by the hardware
> design to help timing closure. The stage has its own gate clock and,
> when that clock is disabled, a controller that starts a DMA transfer can
> never complete it, hanging the storage devices and, from there, the
> whole system.
>
> Add a dedicated match data for the amlogic,t7-mmc compatible that makes
> the driver claim and enable the "pipeline" clock for as long as the
> device is bound.
>
> The clock is deliberately not optional: the hardware cannot do DMA
> without it, and failing the probe with a clear error is preferable to
> booting and hitting an undiagnosable DMA hang later.
>
> Assisted-by: Claude:claude-fable-5
> Signed-off-by: Lucas Tanure <tanure@linux.com>
> ---
> drivers/mmc/host/meson-gx-mmc.c | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
> diff --git a/drivers/mmc/host/meson-gx-mmc.c b/drivers/mmc/host/meson-gx-mmc.c
> index 694bb443d5f3..c0f1e929fc13 100644
> --- a/drivers/mmc/host/meson-gx-mmc.c
> +++ b/drivers/mmc/host/meson-gx-mmc.c
> @@ -139,6 +139,7 @@ struct meson_mmc_data {
> unsigned int always_on;
> unsigned int adjust;
> unsigned int irq_sdio_sleep;
> + bool has_pipeline_clk;
> };
>
> struct sd_emmc_desc {
> @@ -1204,6 +1205,15 @@ static int meson_mmc_probe(struct platform_device *pdev)
> if (IS_ERR(core_clk))
> return PTR_ERR(core_clk);
>
> + if (host->data->has_pipeline_clk) {
> + struct clk *pipe_clk;
> +
> + pipe_clk = devm_clk_get_enabled(&pdev->dev, "pipeline");
> + if (IS_ERR(pipe_clk))
> + return dev_err_probe(&pdev->dev, PTR_ERR(pipe_clk),
> + "missing pipeline clock\n");
> + }
> +
> ret = meson_mmc_clk_init(host);
> if (ret)
> return ret;
> @@ -1322,12 +1332,22 @@ static const struct meson_mmc_data meson_axg_data = {
> .irq_sdio_sleep = CLK_V3_IRQ_SDIO_SLEEP,
> };
>
> +static const struct meson_mmc_data meson_t7_data = {
> + .tx_delay_mask = CLK_V3_TX_DELAY_MASK,
> + .rx_delay_mask = CLK_V3_RX_DELAY_MASK,
> + .always_on = CLK_V3_ALWAYS_ON,
> + .adjust = SD_EMMC_V3_ADJUST,
> + .irq_sdio_sleep = CLK_V3_IRQ_SDIO_SLEEP,
> + .has_pipeline_clk = true,
> +};
> +
> static const struct of_device_id meson_mmc_of_match[] = {
> { .compatible = "amlogic,meson-gx-mmc", .data = &meson_gx_data },
> { .compatible = "amlogic,meson-gxbb-mmc", .data = &meson_gx_data },
> { .compatible = "amlogic,meson-gxl-mmc", .data = &meson_gx_data },
> { .compatible = "amlogic,meson-gxm-mmc", .data = &meson_gx_data },
> { .compatible = "amlogic,meson-axg-mmc", .data = &meson_axg_data },
> + { .compatible = "amlogic,t7-mmc", .data = &meson_t7_data },
> {}
> };
> MODULE_DEVICE_TABLE(of, meson_mmc_of_match);
Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
Thanks,
Neil
next prev parent reply other threads:[~2026-09-10 7:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 15:32 [PATCH v2 0/4] amlogic: t7: give the MMC bus pipeline clock real consumers Lucas Tanure
2026-09-05 15:32 ` [PATCH v2 1/4] dt-bindings: mmc: amlogic,meson-gx-mmc: document the T7 pipeline clock Lucas Tanure
2026-09-07 17:34 ` Conor Dooley
2026-09-05 15:32 ` [PATCH v2 2/4] mmc: meson-gx: enable the bus pipeline clock on T7 Lucas Tanure
2026-09-10 7:13 ` Neil Armstrong [this message]
2026-09-05 15:32 ` [PATCH v2 3/4] arm64: dts: amlogic: t7: add the pipeline clock to the MMC controllers Lucas Tanure
2026-09-10 7:13 ` Neil Armstrong
2026-09-05 15:32 ` [PATCH v2 4/4] clk: meson: t7: don't mark sys_ampipe_nand as critical Lucas Tanure
2026-09-10 7:13 ` Neil Armstrong
2026-09-12 0:08 ` Brian Masney
2026-09-12 7:50 ` Lucas Tanure
2026-09-12 15:50 ` Jerome Brunet
2026-09-11 15:40 ` [PATCH v2 0/4] amlogic: t7: give the MMC bus pipeline clock real consumers 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=cc06ba9b-c866-4c43-a7d4-e25188b84f22@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=bmasney+clk@redhat.com \
--cc=chuan.liu@amlogic.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=jian.hu@amlogic.com \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel-dev@aliel.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=tanure@linux.com \
--cc=ulfh@kernel.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