From: Rob Herring <robh@kernel.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Rajendra Nayak <rnayak@codeaurora.org>,
Andy Gross <andy.gross@linaro.org>,
devicetree@vger.kernel.org,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
Stephen Boyd <sboyd@codeaurora.org>,
LKML <linux-kernel@vger.kernel.org>,
evgreen@chromium.org,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v4 2/4] dt-bindings: qcom: Add SDM845 bindings
Date: Wed, 21 Feb 2018 17:58:49 -0600 [thread overview]
Message-ID: <CAL_JsqL85KCd+U+1n5QdFu6Bn_ygiTPQnqmZD+xgkUgFu0qvMw@mail.gmail.com> (raw)
In-Reply-To: <CAD=FV=UWUD4VMN4gLxBLsSEnsTnOot+ydsaOiFqvD-B2e_RQAg@mail.gmail.com>
On Wed, Feb 21, 2018 at 10:51 AM, Doug Anderson <dianders@chromium.org> wrote:
> Rob,
>
> On Mon, Feb 19, 2018 at 11:34 AM, Rob Herring <robh@kernel.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@codeaurora.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@kernel.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
next prev parent reply other threads:[~2018-02-21 23:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 6:04 [PATCH v4 0/4] Add DTS for SDM845 SoC and MTP Rajendra Nayak
2018-02-16 6:05 ` [PATCH v4 1/4] dt-bindings: arm: Document kryo385 cpu Rajendra Nayak
2018-02-16 19:27 ` Doug Anderson
2018-02-16 6:05 ` [PATCH v4 2/4] dt-bindings: qcom: Add SDM845 bindings Rajendra Nayak
2018-02-16 19:27 ` Doug Anderson
2018-02-19 19:34 ` Rob Herring
2018-02-21 16:51 ` Doug Anderson
2018-02-21 23:58 ` Rob Herring [this message]
2018-02-16 6:05 ` [PATCH v4 3/4] arm64: dts: sdm845: Add minimal dts/dtsi files for sdm845 SoC and MTP Rajendra Nayak
2018-02-16 19:28 ` Doug Anderson
2018-02-19 16:36 ` Marc Zyngier
2018-02-21 23:23 ` Doug Anderson
2018-02-22 7:57 ` Rajendra Nayak
2018-02-22 6:20 ` Rajendra Nayak
2018-02-16 6:05 ` [PATCH v4 4/4] arm64: dts: sdm845: Add serial console support Rajendra Nayak
2018-02-16 19:28 ` Doug Anderson
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=CAL_JsqL85KCd+U+1n5QdFu6Bn_ygiTPQnqmZD+xgkUgFu0qvMw@mail.gmail.com \
--to=robh@kernel.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=evgreen@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rnayak@codeaurora.org \
--cc=sboyd@codeaurora.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).