linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Niklas Cassel <cassel@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Damien Le Moal <dlemoal@kernel.org>,
	Sebastian Reichel <sebastian.reichel@collabora.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: rockchip: rk3588: add msi-parent for pcie3x4_ep
Date: Fri, 03 Jan 2025 15:26:18 +0100	[thread overview]
Message-ID: <13674524.dW097sEU6C@diego> (raw)
In-Reply-To: <Z2Uk2A7-YwkSfAOh@ryzen>

Hey Niklas,

Am Freitag, 20. Dezember 2024, 09:03:36 CET schrieb Niklas Cassel:
> On Tue, Dec 03, 2024 at 12:29:16AM +0100, Heiko Stuebner wrote:
> > 
> > On Wed, 20 Nov 2024 18:10:49 +0100, Niklas Cassel wrote:
> > > Add msi-parent for the pcie3x4_ep PCI endpoint node.
> > > 
> > > The pcie3x4_ep node should use the same msi-parent as the pcie3x4 node
> > > (which represents the PCIe controller running in Root Complex mode).
> > > 
> > > The GIC ITS can be used to trigger an IRQ on the endpoint when any of
> > > the endpoint's PCI BARs are written to by the host[1].
> > > 
> > > [...]
> > 
> > Applied, thanks!
> > 
> > [1/1] arm64: dts: rockchip: rk3588: add msi-parent for pcie3x4_ep
> >       commit: b6f09f497b07008aa65c31341138cecafa78222c
> > 

> Could you please drop this patch from your v6.14-armsoc/dts64 branch?

happy new year :-) .

I've now dropped the patch from my queue


Heiko




      reply	other threads:[~2025-01-03 14:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-20 17:10 [PATCH] arm64: dts: rockchip: rk3588: add msi-parent for pcie3x4_ep Niklas Cassel
2024-12-02 23:29 ` Heiko Stuebner
2024-12-20  8:03   ` Niklas Cassel
2025-01-03 14:26     ` Heiko Stübner [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=13674524.dW097sEU6C@diego \
    --to=heiko@sntech.de \
    --cc=cassel@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh@kernel.org \
    --cc=sebastian.reichel@collabora.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;
as well as URLs for NNTP newsgroup(s).