Devicetree
 help / color / mirror / Atom feed
From: Inochi Amaoto <inochiama@gmail.com>
To: Anirudh Srinivasan <asrinivasan@oss.tenstorrent.com>,
	 Inochi Amaoto <inochiama@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	 Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	 Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>, Yixun Lan <dlan@kernel.org>,
	 devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
	spacemit@lists.linux.dev,  linux-kernel@vger.kernel.org,
	Yixun Lan <dlan@gentoo.org>, Longbin Li <looong.bin@gmail.com>
Subject: Re: [PATCH 2/2] riscv: dts: spacemit: k3: Add PCIe device node
Date: Fri, 17 Jul 2026 06:24:52 +0800	[thread overview]
Message-ID: <allaAnK4nfRSkacc@inochi.infowork> (raw)
In-Reply-To: <CAEev2e8ZyM+b9qLxS6NZjkBZy5GFz37vjgtEfH0ax24nfPozow@mail.gmail.com>

On Mon, Jul 13, 2026 at 10:04:09AM -0500, Anirudh Srinivasan wrote:
> Hi Inochi,
> 
> On Sun, Jul 12, 2026 at 11:19 PM Inochi Amaoto <inochiama@gmail.com> wrote:
> >
> > On Sun, Jul 12, 2026 at 11:13:07PM -0500, Anirudh Srinivasan wrote:
> > > Hi Inochi,
> > >
> > > On Thu, Jul 09, 2026 at 12:04:14PM +0800, Inochi Amaoto wrote:
> > > > Add all PCIe device node for Spacemit K3.
> > > >
> > > > Signed-off-by: Inochi Amaoto <inochiama@gmail.com>
> > > > ---
> > > >  arch/riscv/boot/dts/spacemit/k3-pico-itx.dts |  38 ++++
> > > >  arch/riscv/boot/dts/spacemit/k3-pinctrl.dtsi |  33 ++++
> > > >  arch/riscv/boot/dts/spacemit/k3.dtsi         | 195 +++++++++++++++++++
> > > >  3 files changed, 266 insertions(+)
> > > >
> > >
> > > I see some warnings printed during probe
> > >
> > > [   10.842955] r8169 0002:01:00.0: of_irq_parse_pci: failed with rc=-22
> > >
> > > [   10.937754] rtw89_8852be 0004:01:00.0: of_irq_parse_pci: failed with rc=-22
> > >
> >
> > This is an expected error because the driver does not support INTx
> > but the hardware claims it supports. Since the vendor does not want
> > to support it, so there is no way for the upstreamer to add this.
> 
> Are you saying that the hardware advertises support for INTx, but
> spacemit hasn't provided a driver that uses it?
> 
> Is there a way to let the driver know to not try setting up legacy
> interrupts then? It seems like it's trying to do that now, and failing
> to find interrupts node in the DT.
> 

IIRC it is hard to do this, this is more like a quirk for the spacemit
PCIe controllers.

Regards,
Inochi

> >
> > > I see that all the 3 rc nodes are missing an interrupts node and an
> > > interrupt parent (saplic). The vendor DT seems to have this. Not sure if
> > > this is related.
> > >
> > > The 10G ethernet probes fine, but the wifi card fails to probe. Seems
> > > like the card is trying to request 32 bit DMA addresses and we're
> > > failing cause we have 64 bit memory only.
> > > The vendor kernel seems to have a patch to enable 36 bit DMA in
> > > the rtw89 driver. That'll probably fix this.
> > >
> >
> > This warning is also found on my test, it is not related to
> > the PCIe driver, but a lack of the RTL phy driver. :(
> >
> > You may also noticed a bad performance on this 10G ethernet,
> > it is caused by the single queue used by the RTL driver.
> > IIRC, even 9800 X3D can not achieve the max speed.
> 
> I don't have the ability to test the 10G NIC unfortunately :(
> 
> Regards
> Anirudh Srinivasan
> 
> >
> > Regards,
> > Inochi
> >

      reply	other threads:[~2026-07-16 22:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09  4:04 [PATCH 0/2] riscv: dts: spacemit: k3: Add USB/PCIe devices Inochi Amaoto
2026-07-09  4:04 ` [PATCH 1/2] riscv: dts: spacemit: k3: add USB controller and USB phy support Inochi Amaoto
2026-07-09  4:23   ` sashiko-bot
2026-07-16 21:31   ` Aurelien Jarno
2026-07-09  4:04 ` [PATCH 2/2] riscv: dts: spacemit: k3: Add PCIe device node Inochi Amaoto
2026-07-09  4:17   ` sashiko-bot
2026-07-13  4:13   ` Anirudh Srinivasan
2026-07-13  4:18     ` Inochi Amaoto
2026-07-13 15:04       ` Anirudh Srinivasan
2026-07-16 22:24         ` Inochi Amaoto [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=allaAnK4nfRSkacc@inochi.infowork \
    --to=inochiama@gmail.com \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=asrinivasan@oss.tenstorrent.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlan@gentoo.org \
    --cc=dlan@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=looong.bin@gmail.com \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=robh@kernel.org \
    --cc=spacemit@lists.linux.dev \
    /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