From: Andy Gross <agross@codeaurora.org>
To: Kiran Padwal <kiran.padwal@smartplayin.com>
Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
davidb@codeaurora.org, afaerber@suse.de,
devicetree@vger.kernel.org, linux@arm.linux.org.uk,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] ARM: apq8064: Add pinmux and i2c pinctrl nodes
Date: Mon, 15 Sep 2014 21:39:22 -0500 [thread overview]
Message-ID: <20140916023922.GB2386@qualcomm.com> (raw)
In-Reply-To: <1409052645-14984-1-git-send-email-kiran.padwal@smartplayin.com>
On Tue, Aug 26, 2014 at 05:00:45PM +0530, Kiran Padwal wrote:
> This patch adds pinmux and i2c pinctrl DT node for IFC6410 board.
> It also adds necessary DT support for i2c eeprom which is present on
> IFC6410.
>
> Tested on IFC6410 board.
Looks fine
>
> Signed-off-by: Kiran Padwal <kiran.padwal@smartplayin.com>
> ---
> Changes since v2:
> - Renamed pinmux i2c subnode "i2c1_pinmux" to "i2c1".
> - Removed labes of node.
> - Used canonical value as "okay" instead of "ok".
> - Used macros.
>
> Changes since v1:
> - Renamed pinmux phandle "qcom_pinmux" to "tlmm_pinmux".
> - Updated pinmux interrupt.
>
> arch/arm/boot/dts/qcom-apq8064-ifc6410.dts | 27 ++++++++++++++
> arch/arm/boot/dts/qcom-apq8064.dtsi | 53 ++++++++++++++++++++++++++++
> 2 files changed, 80 insertions(+)
>
> diff --git a/arch/arm/boot/dts/qcom-apq8064-ifc6410.dts b/arch/arm/boot/dts/qcom-apq8064-ifc6410.dts
> index 7c2441d..ef0857e 100644
> --- a/arch/arm/boot/dts/qcom-apq8064-ifc6410.dts
> +++ b/arch/arm/boot/dts/qcom-apq8064-ifc6410.dts
> @@ -5,6 +5,24 @@
> compatible = "qcom,apq8064-ifc6410", "qcom,apq8064";
>
> soc {
> + gsbi@12440000 {
> + status = "okay";
> + qcom,mode = <GSBI_PROT_I2C>;
> +
> + i2c@12460000 {
> + status = "okay";
> + clock-frequency = <200000>;
> + pinctrl-0 = <&i2c1_pins>;
> + pinctrl-names = "default";
> +
> + eeprom: eeprom@52 {
> + compatible = "atmel,24c128";
> + reg = <0x52>;
> + pagesize = <32>;
> + };
don't need read only here. the eeprom is not being used by anything....
thankfully.
> + };
> + };
> +
> gsbi@16600000 {
> status = "ok";
> qcom,mode = <GSBI_PROT_I2C_UART>;
> @@ -12,5 +30,14 @@
> status = "ok";
> };
> };
> +
> + pinmux@800000 {
> + i2c1_pins: i2c1 {
> + mux {
> + pins = "gpio20", "gpio21";
> + function = "gsbi1";
> + };
> + };
> + };
> };
> };
> diff --git a/arch/arm/boot/dts/qcom-apq8064.dtsi b/arch/arm/boot/dts/qcom-apq8064.dtsi
> index 92bf793..5dddbf3 100644
> --- a/arch/arm/boot/dts/qcom-apq8064.dtsi
> +++ b/arch/arm/boot/dts/qcom-apq8064.dtsi
> @@ -89,6 +89,17 @@
> cpu-offset = <0x80000>;
> };
>
> + tlmm_pinmux: pinmux@800000 {
> + compatible = "qcom,apq8064-pinctrl";
> + reg = <0x800000 0x4000>;
> +
> + gpio-controller;
> + #gpio-cells = <2>;
> + interrupt-controller;
> + #interrupt-cells = <2>;
> + interrupts = <0 16 IRQ_TYPE_LEVEL_HIGH>;
> + };
> +
> acc0: clock-controller@2088000 {
> compatible = "qcom,kpss-acc-v1";
> reg = <0x02088000 0x1000>, <0x02008000 0x1000>;
> @@ -133,6 +144,48 @@
> regulator;
> };
>
> + gsbi1: gsbi@12440000 {
> + status = "disabled";
> + compatible = "qcom,gsbi-v1.0.0";
> + reg = <0x12440000 0x100>;
> + clocks = <&gcc GSBI1_H_CLK>;
> + clock-names = "iface";
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges;
> +
> + i2c1: i2c@12460000 {
> + compatible = "qcom,i2c-qup-v1.1.1";
> + reg = <0x12460000 0x1000>;
> + interrupts = <0 194 IRQ_TYPE_NONE>;
> + clocks = <&gcc GSBI1_QUP_CLK>, <&gcc GSBI1_H_CLK>;
> + clock-names = "core", "iface";
> + #address-cells = <1>;
> + #size-cells = <0>;
> + };
> + };
> +
> + gsbi2: gsbi@12480000 {
> + status = "disabled";
> + compatible = "qcom,gsbi-v1.0.0";
> + reg = <0x12480000 0x100>;
> + clocks = <&gcc GSBI2_H_CLK>;
> + clock-names = "iface";
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges;
> +
> + i2c2: i2c@124a0000 {
> + compatible = "qcom,i2c-qup-v1.1.1";
> + reg = <0x124a0000 0x1000>;
> + interrupts = <0 196 IRQ_TYPE_NONE>;
> + clocks = <&gcc GSBI2_QUP_CLK>, <&gcc GSBI2_H_CLK>;
> + clock-names = "core", "iface";
> + #address-cells = <1>;
> + #size-cells = <0>;
> + };
> + };
> +
> gsbi7: gsbi@16600000 {
> status = "disabled";
> compatible = "qcom,gsbi-v1.0.0";
> --
> 1.7.9.5
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2014-09-16 2:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 11:30 [PATCH v3] ARM: apq8064: Add pinmux and i2c pinctrl nodes Kiran Padwal
2014-09-16 2:39 ` Andy Gross [this message]
2014-09-16 12:36 ` kiran.padwal
2014-09-16 19:00 ` Kumar Gala
2014-09-17 10:26 ` kiran.padwal
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=20140916023922.GB2386@qualcomm.com \
--to=agross@codeaurora.org \
--cc=afaerber@suse.de \
--cc=davidb@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kiran.padwal@smartplayin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@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