mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Xi Ruoyao <xry111@xry111.site>
Cc: Jiaxun Yang <jiaxun.yang@flygoat.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Yanteng Si <si.yanteng@linux.dev>,
	devicetree@vger.kernel.org, linux-mips@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: Loongson64: DTS: Really fix PCIe port nodes for ls7a
Date: Sat, 23 Nov 2024 12:02:28 +0100	[thread overview]
Message-ID: <Z0G2RBj2k+ZKU+ld@alpha.franken.de> (raw)
In-Reply-To: <20241123035737.24722-1-xry111@xry111.site>

On Sat, Nov 23, 2024 at 11:57:37AM +0800, Xi Ruoyao wrote:
> Fix the dtc warnings:
> 
>     arch/mips/boot/dts/loongson/ls7a-pch.dtsi:68.16-416.5: Warning (interrupt_provider): /bus@10000000/pci@1a000000: '#interrupt-cells' found, but node is not an interrupt provider
>     arch/mips/boot/dts/loongson/ls7a-pch.dtsi:68.16-416.5: Warning (interrupt_provider): /bus@10000000/pci@1a000000: '#interrupt-cells' found, but node is not an interrupt provider
>     arch/mips/boot/dts/loongson/loongson64g_4core_ls7a.dtb: Warning (interrupt_map): Failed prerequisite 'interrupt_provider'
> 
> And a runtime warning introduced in commit 045b14ca5c36 ("of: WARN on
> deprecated #address-cells/#size-cells handling"):
> 
>     WARNING: CPU: 0 PID: 1 at drivers/of/base.c:106 of_bus_n_addr_cells+0x9c/0xe0
>     Missing '#address-cells' in /bus@10000000/pci@1a000000/pci_bridge@9,0
> 
> The fix is similar to commit d89a415ff8d5 ("MIPS: Loongson64: DTS: Fix PCIe
> port nodes for ls7a"), which has fixed the issue for ls2k (despite its
> subject mentions ls7a).
> 
> Signed-off-by: Xi Ruoyao <xry111@xry111.site>
> ---
>  arch/mips/boot/dts/loongson/ls7a-pch.dtsi | 73 +++++++++++++++++++----
>  1 file changed, 60 insertions(+), 13 deletions(-)

applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      reply	other threads:[~2024-11-23 11:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-23  3:57 Xi Ruoyao
2024-11-23 11:02 ` Thomas Bogendoerfer [this message]

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=Z0G2RBj2k+ZKU+ld@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jiaxun.yang@flygoat.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=si.yanteng@linux.dev \
    --cc=xry111@xry111.site \
    /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

all inboxes | Powered by JetHome®