From: Mark Rutland <mark.rutland@arm.com>
To: Fabien Lahoudere <fabien.lahoudere@collabora.co.uk>
Cc: Rob Herring <robh+dt@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <kernel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"moderated list:ARM PORT" <linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] Add PPD device tree
Date: Fri, 5 Aug 2016 14:39:55 +0100 [thread overview]
Message-ID: <20160805133954.GC25152@leverpostej> (raw)
In-Reply-To: <1470403887-15190-1-git-send-email-fabien.lahoudere@collabora.co.uk>
On Fri, Aug 05, 2016 at 03:31:25PM +0200, Fabien Lahoudere wrote:
> +/*
> + * Hardware uses CKO2 at 24MHz at several places. Set the parent clock of
> + * CKO2 to OSC.
> + */
> +#define CKO2_CONFIGURATION \
> + clock-frequency = <24000000>; \
> + clocks = <&clks IMX5_CLK_CKO2>; \
> + assigned-clocks = <&clks IMX5_CLK_CKO2_SEL>, <&clks IMX5_CLK_OSC>; \
> + assigned-clock-parents = <&clks IMX5_CLK_OSC>
This makes the DT harder to read.
Please place these explicitly where used.
> +
> +/ {
> + model = "Freescale i.MX53 CPUV0 PPD rev6";
> + compatible = "fsl,imx53-ppd", "fsl,imx53";
> +
> + aliases {
> + spi0 = &cspi;
> + spi1 = &ecspi1;
> + spi2 = &ecspi2;
> + };
> +
> + chosen {
> + stdout-path = &uart1;
> + };
It would be good if you could also define the rate, using an alias if
necessary.
> +
> + memory {
> + reg = <0x70000000 0x20000000>,
> + <0xb0000000 0x20000000>;
> + };
> +
> + clocks {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + cko2_11M: sgtl_clock_cko2 {
> + compatible = "fixed-clock";
> + #clock-cells = <0>;
> + clock-frequency = <11289600>;
> + };
> + };
Get rid of the clocks node, and place the clock directly under the root
node.
> +
> + regulators {
> + compatible = "simple-bus";
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + reg_sgtl5k: regulator@0 {
> + compatible = "regulator-fixed";
> + reg = <0>;
> + regulator-name = "reg-sgtl5k";
> + regulator-min-microvolt = <3300000>;
> + regulator-max-microvolt = <3300000>;
> + regulator-always-on;
> + };
Likewise for these. Get rid of the regulators container node and place
these directly under the root node.
Please don't make fake up reg and unit-address values. Just suffix the
node name, e.g. regulator-sgtl5k.
> +&ecspi1 {
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_ecspi1>;
> + fsl,spi-num-chipselects = <4>;
> + /* Fake this GPIO, this has special handling in userspace. */
NAK. The DT should reflect reality, and should not be specific to a
given userspace.
> + cs-gpios = <&gpio5 1 GPIO_ACTIVE_LOW
> + &gpio4 10 GPIO_ACTIVE_LOW
> + &gpio4 11 GPIO_ACTIVE_LOW
> + &gpio4 12 GPIO_ACTIVE_LOW>;
> + status = "okay";
> +
> + spidev0: spi@0 {
> + compatible = "spidev";
> + reg = <0>;
> + spi-max-frequency = <1000000>;
> + status = "okay";
> + };
> +
> + spidev1: spi@1 {
> + compatible = "spidev";
> + reg = <1>;
> + spi-max-frequency = <1000000>;
> + status = "okay";
> + };
> +
> + spidev2: spi@2 {
> + compatible = "spidev";
> + reg = <2>;
> + spi-max-frequency = <1000000>;
> + status = "okay";
> + };
> +
> + spidev3: spi@3 {
> + compatible = "spidev";
> + reg = <3>;
> + spi-max-frequency = <1000000>;
> + status = "okay";
> + };
> +};
What are these SPI devices?
Please fully describe them, with a complete compatible list.
Thanks,
Mark.
next prev parent reply other threads:[~2016-08-05 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 13:31 [PATCH 1/1] Add PPD device tree Fabien Lahoudere
2016-08-05 13:39 ` Mark Rutland [this message]
2016-08-17 7:34 ` Fabien Lahoudere
[not found] ` <1470403887-15190-1-git-send-email-fabien.lahoudere-ZGY8ohtN/8pPYcu2f3hruQ@public.gmane.org>
2016-09-06 6:11 ` Uwe Kleine-König
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=20160805133954.GC25152@leverpostej \
--to=mark.rutland@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=fabien.lahoudere@collabora.co.uk \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.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).