From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Frank Wunderlich <frank-w@public-files.de>
Cc: Frank Wunderlich <linux@fw-web.de>,
Chaotian Jing <chaotian.jing@mediatek.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Wenbin Mei <wenbin.mei@mediatek.com>,
linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, daniel@makrotopia.org,
john@phrozen.org, eladwf@gmail.com, ansuelsmth@gmail.com
Subject: Re: Aw: Re: [PATCH v2 2/2] mmc: mtk-sd: add support for mt7988
Date: Mon, 7 Oct 2024 12:14:58 +0200 [thread overview]
Message-ID: <272309da-24ff-49cd-9e4b-287054218cbc@collabora.com> (raw)
In-Reply-To: <trinity-2ac8c3fe-ad19-424b-ab4f-da84c42c4ae1-1728290266613@3c-app-gmx-bap03>
Il 07/10/24 10:37, Frank Wunderlich ha scritto:
> Hi
>
>> Gesendet: Montag, 07. Oktober 2024 um 09:58 Uhr
>> Von: "AngeloGioacchino Del Regno" <angelogioacchino.delregno@collabora.com>
>> Betreff: Re: [PATCH v2 2/2] mmc: mtk-sd: add support for mt7988
>>
>> Il 06/10/24 17:34, Frank Wunderlich ha scritto:
>>> From: Frank Wunderlich <frank-w@public-files.de>
>>>
>>> Add support for mmc on MT7988 SoC.
>>>
>>> Signed-off-by: Frank Wunderlich <frank-w@public-files.de>
>>
>> There's no need to add yet one more duplicate mtk_mmc_compatible platform
>> data, nor one more compatible string to this driver, as this is exactly
>> the same as mt7986.
>>
>> Please reuse the MT7986 compatible; in DT you'll have:
>>
>> compatible = "mediatek,mt7988-mmc", "mediatek,mt7986-mmc";
>
> as explained in binding, the clock config is completely different (except first 2 also required by driver - 3-7 are optional there). mt7988 uses axi and ahb clocks.
>
> but i could of course use the mt7988 compatible with mt7986 compat data...but looked dirty to me so just copied the block (to allow later changes if needed).
>
In case there will be any changes required *later*, you can always add new platform
data for the MT7988 compatible, as it's just only a code change and nothing else.
For now, since they're the same, just reuse mt7986_compat.
Reusing is way better than duplicating - here and everywhere else - especially when
this implies a 100% duplication.
>> Cheers,
>> Angelo
>>
>>> ---
>>> drivers/mmc/host/mtk-sd.c | 14 ++++++++++++++
>>> 1 file changed, 14 insertions(+)
>>>
>>> diff --git a/drivers/mmc/host/mtk-sd.c b/drivers/mmc/host/mtk-sd.c
>>> index 89018b6c97b9..6d5afe51a61d 100644
>>> --- a/drivers/mmc/host/mtk-sd.c
>>> +++ b/drivers/mmc/host/mtk-sd.c
>>> @@ -571,6 +571,19 @@ static const struct mtk_mmc_compatible mt7986_compat = {
>>> .support_64g = true,
>>> };
>>>
>>> +static const struct mtk_mmc_compatible mt7988_compat = {
>>> + .clk_div_bits = 12,
>>> + .recheck_sdio_irq = true,
>>> + .hs400_tune = false,
>>> + .pad_tune_reg = MSDC_PAD_TUNE0,
>>> + .async_fifo = true,
>>> + .data_tune = true,
>>> + .busy_check = true,
>>> + .stop_clk_fix = true,
>>> + .enhance_rx = true,
>>> + .support_64g = true,
>>> +};
>>> +
>>> static const struct mtk_mmc_compatible mt8135_compat = {
>>> .clk_div_bits = 8,
>>> .recheck_sdio_irq = true,
>>> @@ -629,6 +642,7 @@ static const struct of_device_id msdc_of_ids[] = {
>>> { .compatible = "mediatek,mt7620-mmc", .data = &mt7620_compat},
>>> { .compatible = "mediatek,mt7622-mmc", .data = &mt7622_compat},
>>> { .compatible = "mediatek,mt7986-mmc", .data = &mt7986_compat},
>>> + { .compatible = "mediatek,mt7988-mmc", .data = &mt7988_compat},
>>> { .compatible = "mediatek,mt8135-mmc", .data = &mt8135_compat},
>>> { .compatible = "mediatek,mt8173-mmc", .data = &mt8173_compat},
>>> { .compatible = "mediatek,mt8183-mmc", .data = &mt8183_compat},
>>
>>
next prev parent reply other threads:[~2024-10-07 10:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-06 15:34 [PATCH v2 0/2] Add mmc support for mt7988 Frank Wunderlich
2024-10-06 15:34 ` [PATCH v2 1/2] dt-bindings: mmc: mtk-sd: Add mt7988 SoC Frank Wunderlich
2024-10-07 5:55 ` Krzysztof Kozlowski
2024-10-07 6:59 ` Aw: " Frank Wunderlich
2024-10-07 7:04 ` Krzysztof Kozlowski
2024-10-07 7:56 ` Aw: " Frank Wunderlich
2024-10-07 11:13 ` Krzysztof Kozlowski
2024-10-07 8:00 ` AngeloGioacchino Del Regno
2024-10-07 8:33 ` Aw: " Frank Wunderlich
2024-10-07 10:12 ` AngeloGioacchino Del Regno
2024-10-07 11:36 ` Daniel Golle
2024-10-06 15:34 ` [PATCH v2 2/2] mmc: mtk-sd: add support for mt7988 Frank Wunderlich
2024-10-07 7:58 ` AngeloGioacchino Del Regno
2024-10-07 8:37 ` Aw: " Frank Wunderlich
2024-10-07 10:14 ` AngeloGioacchino Del Regno [this message]
2024-10-07 11:30 ` Krzysztof Kozlowski
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=272309da-24ff-49cd-9e4b-287054218cbc@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=ansuelsmth@gmail.com \
--cc=chaotian.jing@mediatek.com \
--cc=conor+dt@kernel.org \
--cc=daniel@makrotopia.org \
--cc=devicetree@vger.kernel.org \
--cc=eladwf@gmail.com \
--cc=frank-w@public-files.de \
--cc=john@phrozen.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux@fw-web.de \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=wenbin.mei@mediatek.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