devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robin Murphy <robin.murphy@arm.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Heiko Stuebner <heiko@sntech.de>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [RFT PATCH 1/3] arm64: dts: rockchip: correct audio-codec interrupt flag in eaidk-610
Date: Thu, 6 Jul 2023 18:49:33 +0100	[thread overview]
Message-ID: <9d9245fb-463f-c967-46e5-cfc0ac832792@arm.com> (raw)
In-Reply-To: <941ead9e-9e46-b5cb-0a8b-345df6606484@linaro.org>

On 2023-07-06 14:54, Krzysztof Kozlowski wrote:
> On 05/07/2023 08:48, 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: GPIO_ACTIVE_HIGH = 0 = IRQ_TYPE_NONE.
>>
>> Correct the interrupt flags, assuming the author of the code wanted same
>> logical behavior behind the name "ACTIVE_xxx", this is:
>>    ACTIVE_LOW  => IRQ_TYPE_LEVEL_LOW
> 
> This should be HIGH in both cases. I will send a v2.

Also the titles say "audio-codec" but they're all touching SDIO WiFi 
modules ;)

Cheers,
Robin.

>>
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>> ---
>>   arch/arm64/boot/dts/rockchip/rk3399-eaidk-610.dts | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/arm64/boot/dts/rockchip/rk3399-eaidk-610.dts b/arch/arm64/boot/dts/rockchip/rk3399-eaidk-610.dts
>> index d1f343345f67..6464ef4d113d 100644
>> --- a/arch/arm64/boot/dts/rockchip/rk3399-eaidk-610.dts
>> +++ b/arch/arm64/boot/dts/rockchip/rk3399-eaidk-610.dts
>> @@ -773,7 +773,7 @@ brcmf: wifi@1 {
>>   		compatible = "brcm,bcm4329-fmac";
>>   		reg = <1>;
>>   		interrupt-parent = <&gpio0>;
>> -		interrupts = <RK_PA3 GPIO_ACTIVE_HIGH>;
>> +		interrupts = <RK_PA3 IRQ_TYPE_LEVEL_HIGH>;
> 
> Best regards,
> Krzysztof
> 
> 
> _______________________________________________
> Linux-rockchip mailing list
> Linux-rockchip@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip

  reply	other threads:[~2023-07-06 17:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-05  6:48 [RFT PATCH 1/3] arm64: dts: rockchip: correct audio-codec interrupt flag in eaidk-610 Krzysztof Kozlowski
2023-07-05  6:48 ` [RFT PATCH 2/3] arm64: dts: rockchip: correct audio-codec interrupt flag in Rock Pi 4B Krzysztof Kozlowski
2023-07-06 11:31   ` Christopher Obbard
2023-07-05  6:48 ` [RFT PATCH 3/3] arm64: dts: rockchip: correct audio-codec interrupt flag in Box Demo Krzysztof Kozlowski
2023-07-06 13:54 ` [RFT PATCH 1/3] arm64: dts: rockchip: correct audio-codec interrupt flag in eaidk-610 Krzysztof Kozlowski
2023-07-06 17:49   ` Robin Murphy [this message]
2023-07-07  6:26     ` Krzysztof Kozlowski

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=9d9245fb-463f-c967-46e5-cfc0ac832792@arm.com \
    --to=robin.murphy@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --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).