From: Heiko Stuebner <heiko@sntech.de>
To: Anand Moon <linux.amoon@gmail.com>,
Kever Yang <kever.yang@rock-chips.com>,
devicetree@vger.kernel.org,
Jagan Teki <jagan@amarulasolutions.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Vivek Unune <npcomplete13@gmail.com>,
Alexis Ballier <aballier@gentoo.org>,
Johan Jonker <jbx6244@gmail.com>
Cc: Heiko Stuebner <heiko@sntech.de>
Subject: Re: [PATCH v2 1/2] ARM: dts: rk3188: correct interrupt flags
Date: Mon, 4 Apr 2022 10:59:58 +0200 [thread overview]
Message-ID: <164906273049.1398682.13221310139844668938.b4-ty@sntech.de> (raw)
In-Reply-To: <20200917185211.5483-1-krzk@kernel.org>
On Thu, 17 Sep 2020 20:52:10 +0200, Krzysztof Kozlowski wrote:
> GPIO_ACTIVE_x flags are not correct in the context of interrupt flags.
> These are simple defines so they could be used in DTS but they will not
> have the same meaning:
> 1. GPIO_ACTIVE_HIGH = 0 = IRQ_TYPE_NONE
> 2. GPIO_ACTIVE_LOW = 1 = IRQ_TYPE_EDGE_RISING
>
> Correct the interrupt flags without affecting the code:
> ACTIVE_HIGH => IRQ_TYPE_NONE
Applied, thanks!
[1/2] ARM: dts: rk3188: correct interrupt flags
commit: 7e5a7e39d767b60d8631792bd3d7820a6f4a43f8
[2/2] arm64: dts: rk3399: correct interrupt flags
commit: 57f3b0bf5c346f73a848c3d74270b21ed110e530
Best regards,
--
Heiko Stuebner <heiko@sntech.de>
prev parent reply other threads:[~2022-04-04 9:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 18:52 [PATCH v2 1/2] ARM: dts: rk3188: correct interrupt flags Krzysztof Kozlowski
2020-09-17 18:52 ` [PATCH v2 2/2] arm64: dts: rk3399: " Krzysztof Kozlowski
2020-10-02 16:11 ` [PATCH v2 1/2] ARM: dts: rk3188: " Krzysztof Kozlowski
2020-10-17 12:08 ` Heiko Stübner
2022-04-02 16:49 ` Krzysztof Kozlowski
2022-04-04 8:59 ` Heiko Stuebner [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=164906273049.1398682.13221310139844668938.b4-ty@sntech.de \
--to=heiko@sntech.de \
--cc=aballier@gentoo.org \
--cc=devicetree@vger.kernel.org \
--cc=jagan@amarulasolutions.com \
--cc=jbx6244@gmail.com \
--cc=kever.yang@rock-chips.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux.amoon@gmail.com \
--cc=npcomplete13@gmail.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).