linux-kernel - Re: [PATCH v4 2/4] dt-bindings: qcom: Add SDM845 bindings

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: <CAL_JsqL85KCd+U+1n5QdFu6Bn_ygiTPQnqmZD+xgkUgFu0qvMw@mail.gmail.com>
Date:   Wed, 21 Feb 2018 17:58:49 -0600
From:   Rob Herring <robh@...nel.org>
To:     Doug Anderson <dianders@...omium.org>
Cc:     Rajendra Nayak <rnayak@...eaurora.org>,
        Andy Gross <andy.gross@...aro.org>, devicetree@...r.kernel.org,
        linux-arm-msm <linux-arm-msm@...r.kernel.org>,
        Stephen Boyd <sboyd@...eaurora.org>,
        LKML <linux-kernel@...r.kernel.org>, evgreen@...omium.org,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v4 2/4] dt-bindings: qcom: Add SDM845 bindings

On Wed, Feb 21, 2018 at 10:51 AM, Doug Anderson <dianders@...omium.org> wrote:
> Rob,
>
> On Mon, Feb 19, 2018 at 11:34 AM, Rob Herring <robh@...nel.org> wrote:
>> On Fri, Feb 16, 2018 at 11:35:01AM +0530, Rajendra Nayak wrote:
>>> Add a SoC string 'sdm845' for the qualcomm SDM845 SoC
>>>
>>> Signed-off-by: Rajendra Nayak <rnayak@...eaurora.org>
>>> ---
>>>  Documentation/devicetree/bindings/arm/qcom.txt | 1 +
>>>  1 file changed, 1 insertion(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/arm/qcom.txt b/Documentation/devicetree/bindings/arm/qcom.txt
>>> index 0ed4d39d7fe1..ee532e705d6c 100644
>>> --- a/Documentation/devicetree/bindings/arm/qcom.txt
>>> +++ b/Documentation/devicetree/bindings/arm/qcom.txt
>>> @@ -26,6 +26,7 @@ The 'SoC' element must be one of the following strings:
>>>       msm8996
>>>       mdm9615
>>>       ipq8074
>>> +     sdm845
>>
>> These should really be the full string with 'qcom,', but you don't have
>> to fix that now.
>>
>> Reviewed-by: Rob Herring <robh@...nel.org>
>
> Thanks for the review!  I agree that we should land this and then make
> further progress in additional patches.
>
>
> Are you suggesting to rewriting this whole bindings doc to not specify
> things in an "M x N" type of way?  AKA the top of this doc says:
>
>> Each board must specify a top-level board compatible string with the following
>> format:
>>         compatible = "qcom,<SoC>[-<soc_version>][-<foundry_id>]-<board>[/<subtype>][-<board_version>]"
>> The 'SoC' and 'board' elements are required. All other elements are optional.
>
> ...and then the doc goes on to give lists of known SoC and board values.
>
>
> Presumably if someone were to fix this then they'd need to try to
> track down existing boards so they could enumerate every known
> combination?

Ah, I forgot about all this QCom craziness. NM.

Though I'm not sure any of these optional suffixes ever got
implemented. AFAIK, downstream still uses those separate board-id
properties (though the bootloaders can finally deal with them being
absent).

Rob