Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1611681

Re: [PATCH 1/2] dt-bindings: Document the STM32 MDMA bindings

From "M'boumba Cedric Madianga" <cedric.madianga@gmail.com>
Newsgroups linux.kernel
Subject Re: [PATCH 1/2] dt-bindings: Document the STM32 MDMA bindings
Date 2017-03-29 10:20 +0200
Message-ID <tqgZI-49O-13@gated-at.bofh.it> (permalink)
References <tkzLI-2ig-17@gated-at.bofh.it> <tkzLI-2ig-35@gated-at.bofh.it> <tndvk-2mG-7@gated-at.bofh.it> <tpzL4-6pP-19@gated-at.bofh.it> <tq2an-1Rr-35@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Hi Rob,

> stm32 is not a specific SoC. Compatible strings should be specific to
> an SoC (with fallback strings to whatever they are compatible with) so
> you can handle SoC specific differences or errata.

Ok I see. I will add a more specific SoC description in my compatible.
Thanks.


> I still don't understand. Is the difference in DMA addresses vs. CPU
> addresses? If so, you should dma-ranges to translate these.

Not really.
In fact, the MDMA controller provides a master AXI interface for
memories like DDR/SRAM and peripheral registers access (system access
port).
It also provides a master AHB interface only for Cortex-M7 TCM memory
access (TCM access port).
So the goal of this st,ahb-addr-masks property is to list all TCM
addresses avalaible in the SoC, in order to correctly configure the
MDMA as an AHB master in that particular case.
For all other cases (other memories or peripheral registers access),
the MDMA will act as AXI master.

Hope it helps to understand.

BR,
Cedric

Back to linux.kernel | Previous | NextPrevious in thread | Find similar | Unroll thread


Thread

Re: [PATCH 1/2] dt-bindings: Document the STM32 MDMA bindings Rob Herring <robh@kernel.org> - 2017-03-28 18:30 +0200
  Re: [PATCH 1/2] dt-bindings: Document the STM32 MDMA bindings "M'boumba Cedric Madianga" <cedric.madianga@gmail.com> - 2017-03-29 10:20 +0200

csiph-web