From: Yann Gautier <yann.gautier@foss.st.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
<linux-mmc@vger.kernel.org>, <devicetree@vger.kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Philipp Zabel <p.zabel@pengutronix.de>,
Christophe Kerello <christophe.kerello@foss.st.com>,
<linux-kernel@vger.kernel.org>, Marek Vasut <marex@denx.de>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Yang Yingliang <yangyingliang@huawei.com>,
Xiang wangx <wangxiang@cdjrlc.com>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/6] dt-bindings: mmc: mmci: Add st,stm32mp25-sdmmc2 compatible
Date: Thu, 15 Jun 2023 17:16:29 +0200 [thread overview]
Message-ID: <3b6781cb-8f59-e70a-bcf8-9fb48fa47cbf@foss.st.com> (raw)
In-Reply-To: <CAPDyKFqJsqmNzeRg8hj55yUEMSycOWsmKVKsMWk4Qu7Y8_dNzg@mail.gmail.com>
On 6/15/23 15:20, Ulf Hansson wrote:
> On Thu, 15 Jun 2023 at 11:20, Yann Gautier <yann.gautier@foss.st.com> wrote:
>>
>> For STM32MP25, we'll need to distinguish how is managed the delay block.
>> This is done through a new comptible dedicated for this SoC, as the
>> delay block registers are located in SYSCFG peripheral.
>>
>> Signed-off-by: Yann Gautier <yann.gautier@foss.st.com>
>> ---
>> Documentation/devicetree/bindings/mmc/arm,pl18x.yaml | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/mmc/arm,pl18x.yaml b/Documentation/devicetree/bindings/mmc/arm,pl18x.yaml
>> index 1c96da04f0e53..e47b3418b6c77 100644
>> --- a/Documentation/devicetree/bindings/mmc/arm,pl18x.yaml
>> +++ b/Documentation/devicetree/bindings/mmc/arm,pl18x.yaml
>> @@ -59,6 +59,12 @@ properties:
>> - const: st,stm32-sdmmc2
>> - const: arm,pl18x
>> - const: arm,primecell
>> + - description: Entry for STMicroelectronics variant of PL18x for
>> + STM32MP25. This dedicated compatible is used by bootloaders.
>
> What does this last sentence mean? Can we drop it?
Hi Ulf,
I just copied (and added "for STM32MP25") what was done for STM32MP1x:
- description: Entry for STMicroelectronics variant of PL18x.
This dedicated compatible is used by bootloaders.
items:
- const: st,stm32-sdmmc2
- const: arm,pl18x
- const: arm,primecell
- description: Entry for STMicroelectronics variant of PL18x for
STM32MP25. This dedicated compatible is used by bootloaders.
items:
- const: st,stm32mp25-sdmmc2
- const: arm,pl18x
- const: arm,primecell
Should I remove (or adapt) both descriptions?
Best regards,
Yann
>
>> + items:
>> + - const: st,stm32mp25-sdmmc2
>> + - const: arm,pl18x
>> + - const: arm,primecell
>>
>> clocks:
>> description: One or two clocks, the "apb_pclk" and the "MCLK"
>> --
>> 2.25.1
>>
>
> Kind regards
> Uffe
next prev parent reply other threads:[~2023-06-15 15:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 9:19 [PATCH 0/6] Update MMCI driver for STM32MP25 Yann Gautier
2023-06-15 9:19 ` [PATCH 1/6] dt-bindings: mmc: mmci: Add st,stm32mp25-sdmmc2 compatible Yann Gautier
2023-06-15 13:20 ` Ulf Hansson
2023-06-15 15:16 ` Yann Gautier [this message]
2023-06-15 15:19 ` Yann Gautier
2023-06-15 18:51 ` Linus Walleij
2023-06-19 7:29 ` Yann Gautier
2023-06-19 11:01 ` Ulf Hansson
2023-06-17 8:04 ` Krzysztof Kozlowski
2023-06-15 9:19 ` [PATCH 2/6] mmc: mmci: add stm32_idmabsize_align parameter Yann Gautier
2023-06-15 9:19 ` [PATCH 3/6] mmc: mmci: Add support for sdmmc variant revision v3.0 Yann Gautier
2023-06-15 9:19 ` [PATCH 4/6] mmc: mmci: stm32: manage block gap hardware flow control Yann Gautier
2023-06-15 9:20 ` [PATCH 5/6] mmc: mmci: stm32: prepare other delay block support Yann Gautier
2023-06-15 9:20 ` [PATCH 6/6] mmc: mmci: stm32: add delay block support for STM32MP25 Yann Gautier
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=3b6781cb-8f59-e70a-bcf8-9fb48fa47cbf@foss.st.com \
--to=yann.gautier@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=christophe.kerello@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=marex@denx.de \
--cc=mcoquelin.stm32@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=wangxiang@cdjrlc.com \
--cc=yangyingliang@huawei.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