From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>,
Guillaume La Roque <glaroque@baylibre.com>,
devicetree@vger.kernel.org
Cc: linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: meson-sm1-sei610: add missing interrupt-names
Date: Fri, 14 Feb 2020 11:18:06 -0800 [thread overview]
Message-ID: <7h8sl5asgh.fsf@baylibre.com> (raw)
In-Reply-To: <42e82841-067d-245b-6196-183503da389b@baylibre.com>
Neil Armstrong <narmstrong@baylibre.com> writes:
> On 17/01/2020 14:34, Guillaume La Roque wrote:
>> add missing "host-wakeup interrupt names
>>
>> Fixes: 30388cc07572 ("arm64: dts: meson-sm1-sei610: add gpio bluetooth interrupt")
>>
>> Signed-off-by: Guillaume La Roque <glaroque@baylibre.com>
>> ---
>> arch/arm64/boot/dts/amlogic/meson-sm1-sei610.dts | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/arch/arm64/boot/dts/amlogic/meson-sm1-sei610.dts b/arch/arm64/boot/dts/amlogic/meson-sm1-sei610.dts
>> index a8bb3fa9fec9..cb1b48f5b8b1 100644
>> --- a/arch/arm64/boot/dts/amlogic/meson-sm1-sei610.dts
>> +++ b/arch/arm64/boot/dts/amlogic/meson-sm1-sei610.dts
>> @@ -593,6 +593,7 @@
>> compatible = "brcm,bcm43438-bt";
>> interrupt-parent = <&gpio_intc>;
>> interrupts = <95 IRQ_TYPE_LEVEL_HIGH>;
>> + interrupt-names = "host-wakeup";
>> shutdown-gpios = <&gpio GPIOX_17 GPIO_ACTIVE_HIGH>;
>> max-speed = <2000000>;
>> clocks = <&wifi32k>;
>>
>
> Acked-by: Neil Armstrong <narmstrong@baylibre.com>
Queued as a fix for v5.6-rc1.
Thanks,
Kevin
prev parent reply other threads:[~2020-02-14 19:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 13:34 [PATCH] arm64: dts: meson-sm1-sei610: add missing interrupt-names Guillaume La Roque
2020-01-23 9:48 ` Neil Armstrong
2020-02-14 19:18 ` Kevin Hilman [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=7h8sl5asgh.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=glaroque@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.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).