From: "Kaustabh Chakraborty" <kauschluss@disroot.org>
To: "Kaustabh Chakraborty" <kauschluss@disroot.org>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
"Ulf Hansson" <ulfh@kernel.org>, "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Jaehoon Chung" <jh80.chung@samsung.com>,
"Shawn Lin" <shawn.lin@rock-chips.com>
Cc: <linux-mmc@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: mmc: dw-mshc-common: add option for configuring DMA threshold
Date: Sun, 12 Apr 2026 10:16:50 +0530 [thread overview]
Message-ID: <DHQWJJVGWU2A.2JE3O90VZK72Z@disroot.org> (raw)
In-Reply-To: <DHQW60ZTLODV.3C6OG2KUNVSBR@disroot.org>
On 2026-04-12 09:59 +05:30, Kaustabh Chakraborty wrote:
> On 2026-04-11 22:27 +02:00, Krzysztof Kozlowski wrote:
>> On 11/04/2026 21:43, Kaustabh Chakraborty wrote:
>>> Some controllers, such as certain Exynos SDIO ones, are unable to
>>> perform DMA transfers of small amount of bytes properly. Add a property
>>> to configure the DMA transfer threshold.
>>>
>>> Signed-off-by: Kaustabh Chakraborty <kauschluss@disroot.org>
>>> ---
>>> .../devicetree/bindings/mmc/synopsys-dw-mshc-common.yaml | 8 ++++++++
>>> 1 file changed, 8 insertions(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/mmc/synopsys-dw-mshc-common.yaml b/Documentation/devicetree/bindings/mmc/synopsys-dw-mshc-common.yaml
>>> index 6f11b2adf1036..1693277957a91 100644
>>> --- a/Documentation/devicetree/bindings/mmc/synopsys-dw-mshc-common.yaml
>>> +++ b/Documentation/devicetree/bindings/mmc/synopsys-dw-mshc-common.yaml
>>> @@ -57,6 +57,14 @@ properties:
>>> force fifo watermark setting accordingly.
>>> $ref: /schemas/types.yaml#/definitions/flag
>>>
>>> + dma-threshold-bytes:
>>> + description:
>>> + DMA transfer takes place only if the transfer size is equal to or greater
>>> + than the number of bytes defined by the threshold value. Some controllers are
>>> + unable to perform the DMA transfer properly with small amounts of data.
>>
>> Looks like controller specific, thus should be deducible from the
>> compatible.
>
> "samsung,dma-threshold-bytes"? So you also suggest I move it to the
> Samsung's schema? Okay.
Ahh, nevermind I get it. A separate controller compatible which sets a
higher threshold.
>
>>
>> Best regards,
>> Krzysztof
next prev parent reply other threads:[~2026-04-12 4:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-11 19:43 [PATCH 0/2] Configuring DMA threshold value for DW-MMC controllers Kaustabh Chakraborty
2026-04-11 19:43 ` [PATCH 1/2] dt-bindings: mmc: dw-mshc-common: add option for configuring DMA threshold Kaustabh Chakraborty
2026-04-11 20:27 ` Krzysztof Kozlowski
2026-04-12 4:29 ` Kaustabh Chakraborty
2026-04-12 4:46 ` Kaustabh Chakraborty [this message]
2026-04-11 19:43 ` [PATCH 2/2] mmc: dw_mmc: implement " Kaustabh Chakraborty
2026-04-12 11:15 ` Shawn Lin
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=DHQWJJVGWU2A.2JE3O90VZK72Z@disroot.org \
--to=kauschluss@disroot.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jh80.chung@samsung.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=robh@kernel.org \
--cc=shawn.lin@rock-chips.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