From: kishon@ti.com (Kishon Vijay Abraham I)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 4/5] ARM: OMAP4: add _dev_attr_ to ocp2scp for representing usb_phy
Date: Wed, 30 May 2012 16:26:33 +0530 [thread overview]
Message-ID: <1338375394-16268-5-git-send-email-kishon@ti.com> (raw)
In-Reply-To: <1338375394-16268-1-git-send-email-kishon@ti.com>
In order to reflect devices(usb_phy) attached to ocp2scp bus, ocp2scp
is assigned a device attribute to represent the attached devices.
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
Cc: Benoit Cousson <b-cousson@ti.com>
---
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 21 +++++++++++++++++++++
1 files changed, 21 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
index 249ff76..b5a91e8 100644
--- a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
+++ b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
@@ -19,6 +19,7 @@
*/
#include <linux/io.h>
+#include <linux/platform_data/omap_ocp2scp.h>
#include <plat/omap_hwmod.h>
#include <plat/cpu.h>
@@ -2499,6 +2500,25 @@ static struct omap_hwmod_class omap44xx_ocp2scp_hwmod_class = {
.name = "ocp2scp",
};
+/* ocp2scp dev_attr */
+static struct resource omap44xx_usb_phy_and_pll_addrs[] = {
+ {
+ .name = "usb_phy",
+ .start = 0x4a0ad080,
+ .end = 0x4a0ae000,
+ .flags = IORESOURCE_MEM,
+ },
+ { }
+};
+
+static struct omap_ocp2scp_dev ocp2scp_dev_attr[] = {
+ {
+ .drv_name = "omap-usb2",
+ .res = omap44xx_usb_phy_and_pll_addrs,
+ },
+ { }
+};
+
/* ocp2scp_usb_phy */
static struct omap_hwmod_opt_clk ocp2scp_usb_phy_opt_clks[] = {
{ .role = "phy_48m", .clk = "ocp2scp_usb_phy_phy_48m" },
@@ -2516,6 +2536,7 @@ static struct omap_hwmod omap44xx_ocp2scp_usb_phy_hwmod = {
.modulemode = MODULEMODE_HWCTRL,
},
},
+ .dev_attr = ocp2scp_dev_attr,
.opt_clks = ocp2scp_usb_phy_opt_clks,
.opt_clks_cnt = ARRAY_SIZE(ocp2scp_usb_phy_opt_clks),
};
--
1.7.5.4
next prev parent reply other threads:[~2012-05-30 10:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 10:56 [RFC PATCH 0/5] omap: add ocp2scp as a misc driver Kishon Vijay Abraham I
2012-05-30 10:56 ` [RFC PATCH 1/5] arm: omap: hwmod: make *phy_48m* as the main_clk of ocp2scp Kishon Vijay Abraham I
2012-05-30 14:48 ` Shilimkar, Santosh
2012-05-30 10:56 ` [RFC PATCH 2/5] arm: omap: remove ocp2scp_usb_phy_ick clock node Kishon Vijay Abraham I
2012-05-30 14:51 ` Shilimkar, Santosh
2012-05-30 15:23 ` Cousson, Benoit
2012-06-01 12:52 ` ABRAHAM, KISHON VIJAY
2012-06-01 13:24 ` Cousson, Benoit
2012-06-01 15:54 ` ABRAHAM, KISHON VIJAY
2012-09-06 15:02 ` ABRAHAM, KISHON VIJAY
2012-05-30 10:56 ` [RFC PATCH 3/5] drivers: misc: omap: add a new driver for ocp2scp Kishon Vijay Abraham I
2012-05-30 14:55 ` Shilimkar, Santosh
2012-05-30 10:56 ` Kishon Vijay Abraham I [this message]
2012-05-30 10:56 ` [RFC PATCH 5/5] arm: omap: ocp2scp: create omap device " Kishon Vijay Abraham I
2012-05-30 18:43 ` [RFC PATCH 0/5] omap: add ocp2scp as a misc driver Arnd Bergmann
2012-05-31 8:14 ` ABRAHAM, KISHON VIJAY
2012-05-31 9:22 ` Arnd Bergmann
2012-05-31 11:18 ` ABRAHAM, KISHON VIJAY
2012-05-31 20:46 ` Arnd Bergmann
2012-06-06 15:10 ` ABRAHAM, KISHON VIJAY
2012-06-12 17:07 ` Kevin Hilman
2012-06-18 9:34 ` ABRAHAM, KISHON VIJAY
2012-06-01 10:58 ` Tony Lindgren
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=1338375394-16268-5-git-send-email-kishon@ti.com \
--to=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.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).