linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
	Andy Gross <andy.gross@linaro.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	David Brown <david.brown@linaro.org>
Subject: Re: [PATCH 5/5] ARM: dts: add Qualcomm APQ8060-based Dragonboard
Date: Tue, 14 Jun 2016 12:11:54 -0700	[thread overview]
Message-ID: <20160614191154.GK28218@codeaurora.org> (raw)
In-Reply-To: <1465918259-11138-6-git-send-email-linus.walleij@linaro.org>

On 06/14, Linus Walleij wrote:
> +/ {
> +	model = "Qualcomm APQ8060 Dragonboard";
> +	compatible = "qcom,apq8060-dragonboard", "qcom,msm8660";
> +
> +	aliases {
> +		serial0 = &gsbi12_serial;
> +	};
> +
> +	chosen {
> +		stdout-path = "serial0:115200n8";
> +	};
> +
> +	regulators {
> +		compatible = "simple-bus";
> +		/* Main power of the board: 3.7V */
> +		vph: regulator-fixed@1 {
> +			compatible = "regulator-fixed";
> +			regulator-min-microvolt = <3700000>;
> +			regulator-max-microvolt = <3700000>;
> +			regulator-name = "VPH";
> +			regulator-type = "voltage";
> +			regulator-always-on;
> +			regulator-boot-on;
> +		};
> +	};
> +
> +	/* This is a levelshifter for SDCC5 */
> +	dragon_vio_txb: txb0104rgyr {
> +		compatible = "regulator-fixed";
> +		regulator-name = "Dragon SDCC levelshifter";
> +		vin-supply = <&pm8058_l14>;
> +		regulator-always-on;
> +	};

Why not put this under regulators node as well?

> +
> +	soc {
> +		gsbi@19c00000 {
> +			status = "ok";
> +			pinctrl-names = "default";
> +			pinctrl-0 = <&dragon_serial0_pins>;
> +			qcom,mode = <GSBI_PROT_I2C_UART>;
> +			serial@19c40000 {
> +				status = "ok";
> +			};
> +		};
> +	};
> +};
> +
> +/* Intenal 3.69 GiB eMMC */
> +&sdcc1 {
> +	status = "okay";
> +	pinctrl-names = "default";
> +	pinctrl-0 = <&dragon_sdcc1_pins>;
> +	vmmc-supply = <&pm8901_l5>;
> +	vqmmc-supply = <&pm8901_lvs0>;
> +};

I think we're following a non-phandle approach to filling out
board dts files. We didn't follow it that well on 8660 surf,
probably because it was so basic, but it would be nice to follow
that style here as well and populate board properties in nodes
like how gsbi@19c00000 has been done. I'll leave this up to Andy
though as he's the maintainer here.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2016-06-14 19:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-14 15:30 [PATCH 0/5] APQ8060 Dragonboard support Linus Walleij
2016-06-14 15:30 ` [PATCH 1/5] ARM: dts: add GPIO and MPP to MSM8660 PMIC Linus Walleij
2016-06-14 18:57   ` Stephen Boyd
2016-06-14 15:30 ` [PATCH 2/5] ARM: dts: add SDCC5 to Qualcomm MSM8660 Linus Walleij
2016-06-14 18:57   ` Stephen Boyd
2016-06-14 15:30 ` [PATCH 3/5] ARM: dts: add L2CC and RPM with regulators for MSM8660 Linus Walleij
2016-06-14 18:55   ` Stephen Boyd
2016-06-14 19:02     ` Bjorn Andersson
2016-06-14 19:48       ` Stephen Boyd
2016-06-14 22:51         ` Russell King - ARM Linux
2016-06-14 22:48     ` Russell King - ARM Linux
2016-06-16  0:17       ` Stephen Boyd
2016-06-16  8:09         ` Russell King - ARM Linux
2016-06-15 13:16     ` Linus Walleij
2016-06-16  0:57       ` Stephen Boyd
2016-06-14 15:30 ` [PATCH 4/5] ARM: dts: move the fixed MMC regulator to SURF board Linus Walleij
2016-06-14 18:55   ` Stephen Boyd
2016-06-14 15:30 ` [PATCH 5/5] ARM: dts: add Qualcomm APQ8060-based Dragonboard Linus Walleij
2016-06-14 19:11   ` Stephen Boyd [this message]
2016-06-15 13:37     ` Linus Walleij
2016-06-16  0:11   ` Stephen Boyd

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=20160614191154.GK28218@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=andy.gross@linaro.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=david.brown@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-soc@vger.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).