From: "Romli, Khairul Anuar" <khairul.anuar.romli@altera.com>
To: Rob Herring <robh@kernel.org>
Cc: Dinh Nguyen <dinguyen@kernel.org>, Vinod Koul <vkoul@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: dma: snps,dw-axi-dmac: Add compatible string for Agilex5
Date: Wed, 26 Nov 2025 07:43:42 +0000 [thread overview]
Message-ID: <e049a03a-49e3-4b00-a3e8-7560f63fa61a@altera.com> (raw)
In-Reply-To: <20251120173608.GA1582568-robh@kernel.org>
On 21/11/2025 1:36 am, Rob Herring wrote:
> On Thu, Nov 20, 2025 at 07:31:10PM +0800, Khairul Anuar Romli wrote:
>> The address bus on Agilex5 is limited to 40 bits. When SMMU is enable this
>> will cause address truncation and translation faults. Hence introducing
>> "altr,agilex5-axi-dma" to enable platform specific configuration to
>> configure the dma addressable bit mask.
>
> That's likely a bus limitation, not an IP limitation. So that should be
> handled with dma-ranges.
>
> However, adding a specific compatible is perfectly fine.
>
Would it be okay if I rephrase and send the next version with a
correction in the commit message body as your comment in this version?
Thanks.
Regards,
Khairul
>>
>> Add a fallback capability for the compatible property to allow driver to
>> probe and initialize with a newly added compatible string without requiring
>> additional entry in the driver.
>>
>> Signed-off-by: Khairul Anuar Romli <khairul.anuar.romli@altera.com>
>> ---
>> .../devicetree/bindings/dma/snps,dw-axi-dmac.yaml | 14 +++++++++-----
>> 1 file changed, 9 insertions(+), 5 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/dma/snps,dw-axi-dmac.yaml b/Documentation/devicetree/bindings/dma/snps,dw-axi-dmac.yaml
>> index a393a33c8908..db89ebf2b006 100644
>> --- a/Documentation/devicetree/bindings/dma/snps,dw-axi-dmac.yaml
>> +++ b/Documentation/devicetree/bindings/dma/snps,dw-axi-dmac.yaml
>> @@ -17,11 +17,15 @@ allOf:
>>
>> properties:
>> compatible:
>> - enum:
>> - - snps,axi-dma-1.01a
>> - - intel,kmb-axi-dma
>> - - starfive,jh7110-axi-dma
>> - - starfive,jh8100-axi-dma
>> + oneOf:
>> + - enum:
>> + - snps,axi-dma-1.01a
>> + - intel,kmb-axi-dma
>> + - starfive,jh7110-axi-dma
>> + - starfive,jh8100-axi-dma
>> + - items:
>> + - const: altr,agilex5-axi-dma
>> + - const: snps,axi-dma-1.01a
>>
>> reg:
>> minItems: 1
>> --
>> 2.43.7
>>
next prev parent reply other threads:[~2025-11-26 7:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 11:31 [PATCH 0/2] Add Agilex5 AXI DMA support Khairul Anuar Romli
2025-11-20 11:31 ` [PATCH 1/2] dt-bindings: dma: snps,dw-axi-dmac: Add compatible string for Agilex5 Khairul Anuar Romli
2025-11-20 17:36 ` Rob Herring
2025-11-26 7:43 ` Romli, Khairul Anuar [this message]
2025-11-26 9:41 ` Krzysztof Kozlowski
2025-11-20 11:31 ` [PATCH 2/2] arm64: dts: agilex5: Use platform-specific compatible for AXI DMA Khairul Anuar Romli
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=e049a03a-49e3-4b00-a3e8-7560f63fa61a@altera.com \
--to=khairul.anuar.romli@altera.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=vkoul@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