From: Frieder Schrempf <frieder.schrempf@kontron.de>
To: Lucas Stach <l.stach@pengutronix.de>, Shawn Guo <shawnguo@kernel.org>
Cc: NXP Linux Team <linux-imx@nxp.com>,
linux-arm-kernel@lists.infradead.org,
Fabio Estevam <festevam@gmail.com>,
kernel@pengutronix.de, patchwork-lst@pengutronix.de
Subject: Re: [PATCH 2/2] arm64: dts: imx8mn: specify dma-ranges
Date: Tue, 4 May 2021 11:06:03 +0200 [thread overview]
Message-ID: <b4bfa4de-4ca9-ddf8-7691-f73691ab5f76@kontron.de> (raw)
In-Reply-To: <20210504082052.2084706-2-l.stach@pengutronix.de>
On 04.05.21 10:20, Lucas Stach wrote:
> DMA addressing capabilities on i.MX8MN are limited by the interconnect,
> same as on i.MX8MQ. Add dma-ranges to the the peripheral bus to let
> the kernel know about this.
>
> Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Reviewed-by: Frieder Schrempf <frieder.schrempf@kontron.de>
> ---
> arch/arm64/boot/dts/freescale/imx8mn.dtsi | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm64/boot/dts/freescale/imx8mn.dtsi b/arch/arm64/boot/dts/freescale/imx8mn.dtsi
> index 16ea50089567..256e1dfb5db3 100644
> --- a/arch/arm64/boot/dts/freescale/imx8mn.dtsi
> +++ b/arch/arm64/boot/dts/freescale/imx8mn.dtsi
> @@ -245,6 +245,7 @@ soc@0 {
> #address-cells = <1>;
> #size-cells = <1>;
> ranges = <0x0 0x0 0x0 0x3e000000>;
> + dma-ranges = <0x40000000 0x0 0x40000000 0xc0000000>;
> nvmem-cells = <&imx8mn_uid>;
> nvmem-cell-names = "soc_unique_id";
>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-05-04 9:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 8:20 [PATCH 1/2] arm64: dts: imx8mm: specify dma-ranges Lucas Stach
2021-05-04 8:20 ` [PATCH 2/2] arm64: dts: imx8mn: " Lucas Stach
2021-05-04 9:06 ` Frieder Schrempf [this message]
2021-05-04 9:05 ` [PATCH 1/2] arm64: dts: imx8mm: " Frieder Schrempf
2021-05-05 11:36 ` Adam Ford
2021-05-05 11:54 ` Lucas Stach
2021-05-05 12:08 ` Adam Ford
2021-05-23 2:32 ` Shawn Guo
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=b4bfa4de-4ca9-ddf8-7691-f73691ab5f76@kontron.de \
--to=frieder.schrempf@kontron.de \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=patchwork-lst@pengutronix.de \
--cc=shawnguo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.