All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sanchayan Maity <maitysanchayan@gmail.com>
To: arnd@arndb.de, shawnguo@kernel.org
Cc: stefan@agner.ch, robh+dt@kernel.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Sanchayan Maity <maitysanchayan@gmail.com>
Subject: [PATCH v3 3/4] ARM: dts: vfxxx: Add device tree node required by Vybrid SoC driver
Date: Fri, 20 May 2016 15:32:04 +0530	[thread overview]
Message-ID: <94eb84f49274732dce3390a217e4f37a81e50373.1463737502.git.maitysanchayan@gmail.com> (raw)
In-Reply-To: <cover.1463737502.git.maitysanchayan@gmail.com>
In-Reply-To: <cover.1463737502.git.maitysanchayan@gmail.com>

Add a device tree node which will be used to bind the Vybrid
SoC driver and provide information adhering to the following:
https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-devices-soc

Signed-off-by: Sanchayan Maity <maitysanchayan@gmail.com>
---
 arch/arm/boot/dts/vfxxx.dtsi | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/arch/arm/boot/dts/vfxxx.dtsi b/arch/arm/boot/dts/vfxxx.dtsi
index 6c5222e..24979d6 100644
--- a/arch/arm/boot/dts/vfxxx.dtsi
+++ b/arch/arm/boot/dts/vfxxx.dtsi
@@ -770,5 +770,13 @@
 			compatible = "iio-hwmon";
 			io-channels = <&adc0 16>, <&adc1 16>;
 		};
+
+		vf610-soc {
+			compatible = "fsl,vf610-soc";
+			rom-revision = <&ocrom>;
+			mscm = <&mscm_cpucfg>;
+			nvmem-cells = <&ocotp_cfg0>, <&ocotp_cfg1>;
+			nvmem-cell-names = "cfg0", "cfg1";
+		};
 	};
 };
-- 
2.8.2

WARNING: multiple messages have this Message-ID (diff)
From: Sanchayan Maity <maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: arnd-r2nGTMty4D4@public.gmane.org,
	shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Cc: stefan-XLVq0VzYD2Y@public.gmane.org,
	robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Sanchayan Maity
	<maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: [PATCH v3 3/4] ARM: dts: vfxxx: Add device tree node required by Vybrid SoC driver
Date: Fri, 20 May 2016 15:32:04 +0530	[thread overview]
Message-ID: <94eb84f49274732dce3390a217e4f37a81e50373.1463737502.git.maitysanchayan@gmail.com> (raw)
In-Reply-To: <cover.1463737502.git.maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
In-Reply-To: <cover.1463737502.git.maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

Add a device tree node which will be used to bind the Vybrid
SoC driver and provide information adhering to the following:
https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-devices-soc

Signed-off-by: Sanchayan Maity <maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
---
 arch/arm/boot/dts/vfxxx.dtsi | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/arch/arm/boot/dts/vfxxx.dtsi b/arch/arm/boot/dts/vfxxx.dtsi
index 6c5222e..24979d6 100644
--- a/arch/arm/boot/dts/vfxxx.dtsi
+++ b/arch/arm/boot/dts/vfxxx.dtsi
@@ -770,5 +770,13 @@
 			compatible = "iio-hwmon";
 			io-channels = <&adc0 16>, <&adc1 16>;
 		};
+
+		vf610-soc {
+			compatible = "fsl,vf610-soc";
+			rom-revision = <&ocrom>;
+			mscm = <&mscm_cpucfg>;
+			nvmem-cells = <&ocotp_cfg0>, <&ocotp_cfg1>;
+			nvmem-cell-names = "cfg0", "cfg1";
+		};
 	};
 };
-- 
2.8.2

--
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

WARNING: multiple messages have this Message-ID (diff)
From: maitysanchayan@gmail.com (Sanchayan Maity)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 3/4] ARM: dts: vfxxx: Add device tree node required by Vybrid SoC driver
Date: Fri, 20 May 2016 15:32:04 +0530	[thread overview]
Message-ID: <94eb84f49274732dce3390a217e4f37a81e50373.1463737502.git.maitysanchayan@gmail.com> (raw)
In-Reply-To: <cover.1463737502.git.maitysanchayan@gmail.com>

Add a device tree node which will be used to bind the Vybrid
SoC driver and provide information adhering to the following:
https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-devices-soc

Signed-off-by: Sanchayan Maity <maitysanchayan@gmail.com>
---
 arch/arm/boot/dts/vfxxx.dtsi | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/arch/arm/boot/dts/vfxxx.dtsi b/arch/arm/boot/dts/vfxxx.dtsi
index 6c5222e..24979d6 100644
--- a/arch/arm/boot/dts/vfxxx.dtsi
+++ b/arch/arm/boot/dts/vfxxx.dtsi
@@ -770,5 +770,13 @@
 			compatible = "iio-hwmon";
 			io-channels = <&adc0 16>, <&adc1 16>;
 		};
+
+		vf610-soc {
+			compatible = "fsl,vf610-soc";
+			rom-revision = <&ocrom>;
+			mscm = <&mscm_cpucfg>;
+			nvmem-cells = <&ocotp_cfg0>, <&ocotp_cfg1>;
+			nvmem-cell-names = "cfg0", "cfg1";
+		};
 	};
 };
-- 
2.8.2

  parent reply	other threads:[~2016-05-20 10:09 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-20 10:02 [PATCH v3 0/4] Implement SoC driver for Vybrid Sanchayan Maity
2016-05-20 10:02 ` Sanchayan Maity
2016-05-20 10:02 ` Sanchayan Maity
2016-05-20 10:02 ` [PATCH v3 1/4] ARM: dts: vfxxx: Add device tree node for OCOTP Sanchayan Maity
2016-05-20 10:02   ` Sanchayan Maity
2016-05-20 10:02   ` Sanchayan Maity
2016-05-20 10:02 ` [PATCH v3 2/4] ARM: dts: vfxxx: Add On-Chip ROM node for Vybrid Sanchayan Maity
2016-05-20 10:02   ` Sanchayan Maity
2016-05-20 10:02   ` Sanchayan Maity
2016-05-20 10:02 ` Sanchayan Maity [this message]
2016-05-20 10:02   ` [PATCH v3 3/4] ARM: dts: vfxxx: Add device tree node required by Vybrid SoC driver Sanchayan Maity
2016-05-20 10:02   ` Sanchayan Maity
2016-05-20 10:02 ` [PATCH v3 4/4] soc: Add SoC driver for Freescale Vybrid platform Sanchayan Maity
2016-05-20 10:02   ` Sanchayan Maity
2016-05-23 21:18   ` Rob Herring
2016-05-23 21:18     ` Rob Herring
2016-05-24  4:14     ` maitysanchayan
2016-05-24  4:14       ` maitysanchayan at gmail.com
2016-05-24 17:09       ` Rob Herring
2016-05-24 17:09         ` Rob Herring
2016-05-24 17:09         ` Rob Herring
2016-05-25 15:18         ` Arnd Bergmann
2016-05-25 15:18           ` Arnd Bergmann
2016-05-25 15:18           ` Arnd Bergmann
2016-05-27  6:33         ` maitysanchayan
2016-05-27  6:33           ` maitysanchayan at gmail.com
2016-05-27  6:33           ` maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w
2016-05-27  8:31           ` Arnd Bergmann
2016-05-27  8:31             ` Arnd Bergmann
2016-05-27  8:31             ` Arnd Bergmann
2016-05-27 10:08             ` maitysanchayan
2016-05-27 10:08               ` maitysanchayan at gmail.com
2016-05-27 10:08               ` maitysanchayan
2016-05-27 17:28               ` Stefan Agner
2016-05-27 17:28                 ` Stefan Agner
2016-05-27 17:28                 ` Stefan Agner
2016-05-27 17:56                 ` maitysanchayan
2016-05-27 17:56                   ` maitysanchayan at gmail.com
2016-06-09 10:38               ` maitysanchayan
2016-06-09 10:38                 ` maitysanchayan at gmail.com
2016-06-09 10:38                 ` maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w

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=94eb84f49274732dce3390a217e4f37a81e50373.1463737502.git.maitysanchayan@gmail.com \
    --to=maitysanchayan@gmail.com \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=stefan@agner.ch \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.