linux-kernel - Re: [RFC PATCH v3 3/4] irqchip: gic-v3: Add quirk for msm8996 secured registers

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: <86b0d75b-c604-f2ad-e147-270942e05409@linaro.org>
Date:   Thu, 29 Nov 2018 14:10:36 +0000
From:   Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
To:     Bjorn Andersson <bjorn.andersson@...aro.org>
Cc:     marc.zyngier@....com, sudeep.holla@....com, tglx@...utronix.de,
        jason@...edaemon.net, linux-kernel@...r.kernel.org,
        linux-arm-msm@...r.kernel.org, rnayak@...eaurora.org,
        sboyd@...nel.org, srini@...nel.org, nicolas.dechesne@...aro.org,
        ctatlor97@...il.com, vkoul@...nel.org
Subject: Re: [RFC PATCH v3 3/4] irqchip: gic-v3: Add quirk for msm8996 secured
 registers



On 28/11/18 23:33, Bjorn Andersson wrote:
> Given that the change request introducing this restriction looks quite
> generic and that we've heard reports of other shipping platforms having
> the same restriction, could we make this slightly more generic?
> 
> I.e. dropping the MSM8996 from the flag name and perhaps use a bool
> property in devicetree to toggle the flag, instead of adding compatibles
> as we figure out which Qualcomm platforms has this restriction.
If I understand the dt compatible thing correctly. Am not expecting 
other platforms to add new compatible string. If the gic-v3 of that SoC 
is compatible with msm8996, they should be able to use the same 
compatible string!

--srini