All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Steffen Trumtrar <s.trumtrar@pengutronix.de>,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org
Cc: kernel@pengutronix.de,
	Alexandre Torgue <alexandre.torgue@foss.st.com>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>
Subject: Re: [PATCH v2 2/3] ARM: dts: stm32: add STM32MP1-based Phytec SoM
Date: Mon, 16 May 2022 14:32:59 +0200	[thread overview]
Message-ID: <6fe3aabe-98be-e316-cbd1-1d9705d871d3@pengutronix.de> (raw)
In-Reply-To: <20220516121619.2617401-2-s.trumtrar@pengutronix.de>

Hello Steffen,

On 16.05.22 14:16, Steffen Trumtrar wrote:
> +	reserved-memory {
> +		#address-cells = <1>;
> +		#size-cells = <1>;
> +		ranges;
> +
> +		retram: retram@38000000 {
> +			compatible = "shared-dma-pool";
> +			reg = <0x38000000 0x10000>;
> +			no-map;
> +		};
> +
> +		mcuram: mcuram@30000000 {
> +			compatible = "shared-dma-pool";
> +			reg = <0x30000000 0x40000>;
> +			no-map;
> +		};
> +
> +		mcuram2: mcuram2@10000000 {
> +			compatible = "shared-dma-pool";
> +			reg = <0x10000000 0x40000>;
> +			no-map;

Is this intended? Or do you want to use SRAM fully
from e.g. userspace?

> +&uart4 {
> +	pinctrl-names = "default", "sleep", "idle";
> +	pinctrl-0 = <&uart4_pins_a>;
> +	pinctrl-1 = <&uart4_sleep_pins_a>;
> +	pinctrl-2 = <&uart4_idle_pins_a>;
> +	pinctrl-3 = <&uart4_pins_a>;
> +	status = "okay";
> +};

As you are using uart4 as the Linux console, you'll need to:

  /delete-property/dmas;     
  /delete-property/dma-names;

because the STM32 UART driver doesn't support DMA for the console
and dma properties have been added into the SoC dtsi in
v5.18-rc1, commit:

  0f18f728ba62 ("ARM: dts: stm32: add DMA configuration to UART nodes on stm32mp151")

Cheers,
Ahmad

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-05-16 12:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16 12:16 [PATCH v2 1/3] ARM: dts: stm32: add SRAM binding Steffen Trumtrar
2022-05-16 12:16 ` [PATCH v2 2/3] ARM: dts: stm32: add STM32MP1-based Phytec SoM Steffen Trumtrar
2022-05-16 12:32   ` Ahmad Fatoum [this message]
2022-05-16 15:16   ` Alexandre TORGUE
2022-05-16 12:16 ` [PATCH v2 3/3] ARM: dts: stm32: add STM32MP1-based Phytec board Steffen Trumtrar
2022-05-16 15:11   ` Alexandre TORGUE
2022-05-16 12:24 ` [PATCH v2 1/3] ARM: dts: stm32: add SRAM binding Ahmad Fatoum
2022-05-16 12:35   ` Ahmad Fatoum

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=6fe3aabe-98be-e316-cbd1-1d9705d871d3@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=alexandre.torgue@foss.st.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=s.trumtrar@pengutronix.de \
    /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.