linux-kernel - Re: [PATCH] arm64: dts: qcom: sc7280: All current evoker boards are LTE

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: <20220920114020.2185607-1-sheng-liang.pan@quanta.corp-partner.google.com>
Date:   Tue, 20 Sep 2022 19:40:20 +0800
From:   Sheng-Liang Pan <sheng-liang.pan@...nta.corp-partner.google.com>
To:     dianders@...omium.org
Cc:     agross@...nel.org, andersson@...nel.org,
        devicetree@...r.kernel.org, konrad.dybcio@...ainline.org,
        krzysztof.kozlowski+dt@...aro.org, linux-arm-msm@...r.kernel.org,
        linux-kernel@...r.kernel.org, mka@...omium.org,
        quic_sibis@...cinc.com, robh+dt@...nel.org,
        sheng-liang.pan@...nta.corp-partner.google.com, swboyd@...omium.org
Subject: Re: [PATCH] arm64: dts: qcom: sc7280: All current evoker boards are LTE

> At the time that commit 2abf6b6b9429 ("arm64: dts: qcom: sc7280: Add
> device tree for herobrine evoker") was posted, all herobrine SKUs were
> LTE.
>
> At the time that commit d42fae738f3a ("arm64: dts: qcom: Add LTE SKUs
> for sc7280-villager family"), the evoker board device tree hadn't yet
> landed.
>
> I belive that the above two facts mean that the evoker boards ought to
> be setup for LTE but currently aren't. Let's fix that.
Evoker should also have wifi/lte SKU, 
I think we need to follow villager to create evoker.dtsi then separate wifi/lte dts.