public inbox for linux-mediatek@lists.infradead.org
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
To: Rui Salvaterra <rsalvaterra@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: ryder.lee@mediatek.com, daniel@makrotopia.org
Subject: Re: [PATCH] arm64: dts: mt7622: specify the number of DMA requests
Date: Fri, 29 Apr 2022 13:57:20 +0200	[thread overview]
Message-ID: <91d8eb87-adf0-da62-0c7b-dbf94442f535@gmail.com> (raw)
In-Reply-To: <20220429084225.298213-1-rsalvaterra@gmail.com>



On 29/04/2022 10:42, Rui Salvaterra wrote:
> The MT7622 device tree never bothered to specify the number of virtual DMA
> channels for the HSDMA controller, always falling back to the default value of
> 3. Make this value explicit, in order to avoid the following dmesg notification:
> 
> mtk_hsdma 1b007000.dma-controller: Using 3 as missing dma-requests property
> 
> Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>

Applied, thanks!

> ---
>   arch/arm64/boot/dts/mediatek/mt7622.dtsi | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/arch/arm64/boot/dts/mediatek/mt7622.dtsi b/arch/arm64/boot/dts/mediatek/mt7622.dtsi
> index 3d6eaf6dd078..5551f004945b 100644
> --- a/arch/arm64/boot/dts/mediatek/mt7622.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt7622.dtsi
> @@ -924,6 +924,7 @@ hsdma: dma-controller@1b007000 {
>   		clock-names = "hsdma";
>   		power-domains = <&scpsys MT7622_POWER_DOMAIN_ETHSYS>;
>   		#dma-cells = <1>;
> +		dma-requests = <3>;
>   	};
>   
>   	eth: ethernet@1b100000 {

_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

  reply	other threads:[~2022-04-29 11:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-29  8:42 [PATCH] arm64: dts: mt7622: specify the number of DMA requests Rui Salvaterra
2022-04-29 11:57 ` Matthias Brugger [this message]
2022-04-29 13:05   ` Rui Salvaterra
2022-04-29 14:14     ` Matthias Brugger

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=91d8eb87-adf0-da62-0c7b-dbf94442f535@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=daniel@makrotopia.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=rsalvaterra@gmail.com \
    --cc=ryder.lee@mediatek.com \
    /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