From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Florian Fainelli" <f.fainelli@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
linux-mips@vger.kernel.org, devicetree@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH] mips: dts: brcm: bcm7435: add "interrupt-names" for NAND controller
Date: Mon, 21 Nov 2022 18:05:05 +0100 [thread overview]
Message-ID: <20221121170505.GD3200@alpha.franken.de> (raw)
In-Reply-To: <20221108085032.4609-1-zajec5@gmail.com>
On Tue, Nov 08, 2022 at 09:50:32AM +0100, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> Second interrupt can be DMA or EDU one. Specify it explicitly using
> interrupt-names property. This matches documented binding.
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
> arch/mips/boot/dts/brcm/bcm7435.dtsi | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/mips/boot/dts/brcm/bcm7435.dtsi b/arch/mips/boot/dts/brcm/bcm7435.dtsi
> index 8c001b944c8b..cfdf9804e126 100644
> --- a/arch/mips/boot/dts/brcm/bcm7435.dtsi
> +++ b/arch/mips/boot/dts/brcm/bcm7435.dtsi
> @@ -422,6 +422,7 @@ nand: nand@41c800 {
> reg = <0x41c800 0x600>, <0x41d000 0x100>;
> interrupt-parent = <&hif_l2_intc>;
> interrupts = <24>, <4>;
> + interrupt-names = "nand_ctlrdy", "flash_dma_done";
> status = "disabled";
> };
>
> --
> 2.34.1
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 ]
prev parent reply other threads:[~2022-11-21 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 8:50 [PATCH] mips: dts: brcm: bcm7435: add "interrupt-names" for NAND controller Rafał Miłecki
2022-11-08 18:20 ` Florian Fainelli
2022-11-21 17:05 ` 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=20221121170505.GD3200@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-mips@vger.kernel.org \
--cc=rafal@milecki.pl \
--cc=robh+dt@kernel.org \
--cc=zajec5@gmail.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).