devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Gross <andy.gross@ti.com>
To: linux-omap@vger.kernel.org
Cc: Benoit Cousson <bicousson@ti.com>,
	Santosh Shilimkar <santosh.shilimkar@ti.com>,
	devicetree-discuss@lists.ozlabs.org, Nishanth Menon <nm@ti.com>,
	Andy Gross <andy.gross@ti.com>
Subject: [PATCH 2/2] ARM: OMAP2+: Remove dmm device creation
Date: Tue, 19 Mar 2013 23:43:44 -0500	[thread overview]
Message-ID: <1363754624-5209-3-git-send-email-andy.gross@ti.com> (raw)
In-Reply-To: <1363754624-5209-1-git-send-email-andy.gross@ti.com>

Remove DMM device creation via the hwmod entry.  The DMM device will
now be enumerated as part of the device tree information for the
processor.

Signed-off-by: Andy Gross <andy.gross@ti.com>
---
 Documentation/devicetree/bindings/arm/omap/dmm.txt |   16 ++++++++++++++++
 arch/arm/mach-omap2/drm.c                          |   12 ------------
 2 files changed, 16 insertions(+), 12 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/arm/omap/dmm.txt

diff --git a/Documentation/devicetree/bindings/arm/omap/dmm.txt b/Documentation/devicetree/bindings/arm/omap/dmm.txt
new file mode 100644
index 0000000..5fd1134
--- /dev/null
+++ b/Documentation/devicetree/bindings/arm/omap/dmm.txt
@@ -0,0 +1,16 @@
+OMAP Dynamic Memory Manager (DMM) bindings
+
+Required properties:
+- compatible:	Must be "ti,dmm" for OMAP processors containing DMM block
+- reg:		Contains timer register address range (base address and length)
+- interrupts:	Contains interrupt information (source, etc) for the DMM IRQ
+- ti,hwmods:	Name of the hwmod associated to the counter, which is typically
+		"dmm"
+
+Example:
+
+dmm: dmm@4e000000 {
+	compatible = "ti,dmm";
+	reg = <0x4e000000 0x800>;
+	ti,hwmods = "dmm";
+};
diff --git a/arch/arm/mach-omap2/drm.c b/arch/arm/mach-omap2/drm.c
index 59a4af7..1fd0487 100644
--- a/arch/arm/mach-omap2/drm.c
+++ b/arch/arm/mach-omap2/drm.c
@@ -44,18 +44,6 @@ static struct platform_device omap_drm_device = {
 
 static int __init omap_init_drm(void)
 {
-	struct omap_hwmod *oh = NULL;
-	struct platform_device *pdev;
-
-	/* lookup and populate the DMM information, if present - OMAP4+ */
-	oh = omap_hwmod_lookup("dmm");
-
-	if (oh) {
-		pdev = omap_device_build(oh->name, -1, oh, NULL, 0);
-		WARN(IS_ERR(pdev), "Could not build omap_device for %s\n",
-			oh->name);
-	}
-
 	platform_data.omaprev = GET_OMAP_TYPE;
 
 	return platform_device_register(&omap_drm_device);
-- 
1.7.5.4


  parent reply	other threads:[~2013-03-20  4:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-20  4:43 [PATCH 0/2] ARM: dts: OMAP4+: Add dmm device bindings Andy Gross
2013-03-20  4:43 ` [PATCH 1/2] ARM: dts: OMAP4+: Add DMM bindings Andy Gross
2013-03-20  5:59   ` Santosh Shilimkar
2013-03-20  4:43 ` Andy Gross [this message]
2013-03-20  5:56   ` [PATCH 2/2] ARM: OMAP2+: Remove dmm device creation Santosh Shilimkar
2013-03-20  6:16     ` Archit Taneja
2013-03-20  6:22       ` Santosh Shilimkar
2013-03-20  6:28         ` Gross, Andy

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=1363754624-5209-3-git-send-email-andy.gross@ti.com \
    --to=andy.gross@ti.com \
    --cc=bicousson@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=santosh.shilimkar@ti.com \
    /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).