linux-kernel - Re: Exynos850 and ExynosAuto v9 pinctrl wakeup muxed interrupt

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <07cd9a2a-9491-0eb0-1f00-7319f58a508a@canonical.com>
Date:   Tue, 11 Jan 2022 14:17:04 +0100
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
To:     Chanho Park <chanho61.park@...sung.com>,
        'Sam Protsenko' <semen.protsenko@...aro.org>
Cc:     linux-samsung-soc@...r.kernel.org,
        'Linux Kernel Mailing List' <linux-kernel@...r.kernel.org>,
        'Sylwester Nawrocki' <s.nawrocki@...sung.com>,
        'Tomasz Figa' <tomasz.figa@...il.com>
Subject: Re: Exynos850 and ExynosAuto v9 pinctrl wakeup muxed interrupt

On 10/01/2022 08:54, Chanho Park wrote:
>>
>> The error message is valid - correctly points to wrong configuration.
>> All pinctrl nodes should have one interrupt, if they have GPIOs capable of
>> interrupt as a function (usually 0xf as GPIO CON register). Why
>> pinctrl_aud does not have it? Maybe the function EXT_INT (0xf) is not
>> available for its pins?
> 
> Regarding pinctrl_aud, the interrupt number is not defined in interrupt source table because the line is not connected to CPU's GIC. It is directed to the GIC of dedicated audio subsystem which name is ABOX. So, we cannot handle the interrupt of pinctrl_aud even though GPBx_CON registers have EXT_INT(0xf) setting.

Thanks for checking. I will need to include this in the dtschema.


Best regards,
Krzysztof