From: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
To: Jeremy McNicoll <jeremymc-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
andy.gross-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
arnd-r2nGTMty4D4@public.gmane.org,
bjorn.andersson-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org
Subject: Re: [RFC V3 PATCH 1/7] arm64: dts: msm8992 SoC and LG Bullhead (Nexus 5X) support
Date: Wed, 12 Oct 2016 11:30:02 +0100 [thread overview]
Message-ID: <20161012103001.GB19509@remoulade> (raw)
In-Reply-To: <1476265054-22511-2-git-send-email-jeremymc-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On Wed, Oct 12, 2016 at 02:37:28AM -0700, Jeremy McNicoll wrote:
> +/ {
> + model = "LGE MSM8992 BULLHEAD rev-1.01";
> + compatible = "qcom,msm8992";
> + qcom,board-id = <0xb64 0>;
> +};
This last property doesn't seem to be documented or used in mainline.
What is it for?
> +/ {
> + aliases {
> + serial0 = &blsp1_uart2;
> + };
> +
> + chosen {
> + stdout-path = "serial0";
> + };
I'd recommend describing the configured rate, per
Documentation/devicetree/bindings/chosen.txt
[...]
> +/ {
> + model = "Qualcomm Technologies, Inc. MSM 8992";
> + compatible = "qcom,msm8992";
> + qcom,msm-id = <251 0>, <252 0>;
> + qcom,pmic-id = <0x10009 0x1000A 0x0 0x0>;
These last two are not documented, and not used in mainline.
What are they for?
> + memory {
> + #address-cells = <2>;
> + #size-cells = <2>;
> +
> + device_type = "memory";
> + reg = <0 0 0 0>;
If this is filled in by the bootloader, please havea coment to that effect.
> + peripheral_mem: peripheral_region@0 {
> + linux,reserve-contiguous-region;
> + linux,reserve-region;
> + linux,remove-completely;
> + reg = <0 0x07400000 0 0x1c00000>;
> + label = "peripheral_mem";
> + };
> + };
What is this?
There aren't any sub-nodes of memory (iirc reserved-memory is a separate node),
an none of these 'liux,' prefixed properties exist in mainline.
[...]
> + timer {
> + compatible = "arm,armv8-timer";
> + interrupts = <1 2 0xf08>,
> + <1 3 0xf08>,
> + <1 4 0xf08>,
> + <1 1 0xf08>;
> + clock-frequency = <19200000>;
> + };
Why is the FW not programming the frequency register?
> + clocks {
> + xo_board: xo_board {
> + compatible = "fixed-clock";
> + #clock-cells = <0>;
> + clock-frequency = <19200000>;
> + };
> +
> + sleep_clk: sleep_clk {
> + compatible = "fixed-clock";
> + #clock-cells = <0>;
> + clock-frequency = <32768>;
> + };
> + };
Get rid of the clocks container node, and places these directly under the root node.
Thanks,
Mark.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-10-12 10:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 9:37 [RFC V3 PATCH 0/7] msm8992/msm8994: Google Nexus 5X/6P initial board support Jeremy McNicoll
[not found] ` <1476265054-22511-1-git-send-email-jeremymc-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-10-12 9:37 ` [RFC V3 PATCH 1/7] arm64: dts: msm8992 SoC and LG Bullhead (Nexus 5X) support Jeremy McNicoll
[not found] ` <1476265054-22511-2-git-send-email-jeremymc-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-10-12 10:30 ` Mark Rutland [this message]
2016-10-13 4:15 ` Jeremy McNicoll
2016-10-21 8:55 ` Jeremy McNicoll
2016-10-12 9:37 ` [RFC V3 PATCH 4/7] arm64: dts: msm8992 default serial config Jeremy McNicoll
2016-10-12 13:28 ` Mark Rutland
2016-10-12 9:37 ` [RFC V3 PATCH 2/7] msm8994 clocks: global clock support Global clock support for the msm8994 SOC Jeremy McNicoll
2016-10-12 9:37 ` [RFC V3 PATCH 3/7] dt-bindings: qcom: Add msm899(2/4) bindings Jeremy McNicoll
[not found] ` <1476265054-22511-4-git-send-email-jeremymc-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-10-18 13:06 ` Rob Herring
2016-10-12 9:37 ` [RFC V3 PATCH 5/7] arm64: dts: msm8994 SoC and Huawei Angler (Nexus 6P) support Jeremy McNicoll
[not found] ` <1476265054-22511-6-git-send-email-jeremymc-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-10-12 13:34 ` Mark Rutland
2016-10-12 14:20 ` Rob Herring
[not found] ` <CAL_JsqLMs3cE6qne_GN-3E7c1ub_6U0y5UF0aLkxUD=k5fiOTw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-10-13 0:42 ` Jeremy McNicoll
[not found] ` <3e641d25-8ca6-3594-5d3e-038d6f7a9eba-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-10-14 22:06 ` Michael Scott
2016-10-17 22:15 ` Andy Gross
2016-10-12 9:37 ` [RFC V3 PATCH 6/7] arm64: dts: msm8994 default serial config Jeremy McNicoll
2016-10-12 13:28 ` Mark Rutland
2016-10-21 8:42 ` Jeremy McNicoll
2016-10-12 9:37 ` [RFC V3 PATCH 7/7] arm64: configs: enable configs for msm899(2/4) basic support Jeremy McNicoll
2016-10-12 13:37 ` Mark Rutland
2016-10-21 8:59 ` Jeremy McNicoll
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=20161012103001.GB19509@remoulade \
--to=mark.rutland-5wv7dgnigg8@public.gmane.org \
--cc=andy.gross-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=bjorn.andersson-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jeremymc-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.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).