Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@nxp.com>
To: Alexander Stein <alexander.stein@ew.tq-group.com>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	devicetree@vger.kernel.org, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux@ew.tq-group.com
Subject: Re: [PATCH 1/5] arm64: dts: imx8-ss-hsio: Wire up DMA IRQ for PCIe
Date: Tue, 7 Jan 2025 10:39:25 -0500	[thread overview]
Message-ID: <Z31KrdxPULx8K5ao@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20250107140110.982215-2-alexander.stein@ew.tq-group.com>

On Tue, Jan 07, 2025 at 03:01:06PM +0100, Alexander Stein wrote:
> IRQ mapping is already present. Add the missing DMA interrupt.

PCI host side have not use bridge's DMA yet although hardware support it.

Frank

>
> Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
> ---
>  arch/arm64/boot/dts/freescale/imx8-ss-hsio.dtsi | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/freescale/imx8-ss-hsio.dtsi b/arch/arm64/boot/dts/freescale/imx8-ss-hsio.dtsi
> index 70a8aa1a67911..4bdfc15487cbc 100644
> --- a/arch/arm64/boot/dts/freescale/imx8-ss-hsio.dtsi
> +++ b/arch/arm64/boot/dts/freescale/imx8-ss-hsio.dtsi
> @@ -57,8 +57,9 @@ pcieb: pcie@5f010000 {
>  		ranges = <0x81000000 0 0x00000000 0x8ff80000 0 0x00010000>,
>  			 <0x82000000 0 0x80000000 0x80000000 0 0x0ff00000>;
>  		#interrupt-cells = <1>;
> -		interrupts = <GIC_SPI 102 IRQ_TYPE_LEVEL_HIGH>;
> -		interrupt-names = "msi";
> +		interrupts = <GIC_SPI 102 IRQ_TYPE_LEVEL_HIGH>,
> +			     <GIC_SPI 104 IRQ_TYPE_LEVEL_HIGH>;
> +		interrupt-names = "msi", "dma";
>  		#address-cells = <3>;
>  		#size-cells = <2>;
>  		clocks = <&pcieb_lpcg IMX_LPCG_CLK_6>,
> --
> 2.34.1
>


  reply	other threads:[~2025-01-07 15:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-07 14:01 [PATCH 0/5] TQMa8Xx update Alexander Stein
2025-01-07 14:01 ` [PATCH 1/5] arm64: dts: imx8-ss-hsio: Wire up DMA IRQ for PCIe Alexander Stein
2025-01-07 15:39   ` Frank Li [this message]
2025-01-08  9:58     ` Alexander Stein
2025-01-08 16:33       ` Frank Li
2025-02-24 17:49         ` Frank Li
2025-02-25 10:20           ` Alexander Stein
2025-01-07 14:01 ` [PATCH 2/5] arm64: dts: tqma8xx: Add vcc-supply for spi-nor Alexander Stein
2025-01-07 14:01 ` [PATCH 3/5] arm64: dts: tqma8xx: enable jpeg encode and decode Alexander Stein
2025-01-07 14:01 ` [PATCH 4/5] arm64: dts: tqma8xx: Remove GPU TODO Alexander Stein
2025-01-07 14:01 ` [PATCH 5/5] arm64: dts: mba8xx: Add PCIe support Alexander Stein
2025-02-24 19:04   ` Frank Li
2025-02-25 10:19     ` Alexander Stein
2025-02-18  5:26 ` [PATCH 0/5] TQMa8Xx update Shawn Guo

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=Z31KrdxPULx8K5ao@lizhi-Precision-Tower-5810 \
    --to=frank.li@nxp.com \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@ew.tq-group.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    /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