From: Felipe Balbi <balbi@ti.com>
To: Hema HK <hemahk@ti.com>
Cc: linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
Felipe Balbi <balbi@ti.com>, Tony Lindgren <tony@atomide.com>,
Kevin Hilman <khilman@deeprootsystems.com>,
"Cousson, Benoit" <b-cousson@ti.com>,
Paul Walmsley <paul@pwsan.com>
Subject: Re: [PATCH 4/5 v4] OMAP2+: musb: HWMOD adaptation for musb.
Date: Fri, 10 Dec 2010 15:02:33 +0200 [thread overview]
Message-ID: <20101210130232.GL6027@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <1291985590-27126-1-git-send-email-hemahk@ti.com>
Hi,
On Fri, Dec 10, 2010 at 06:23:10PM +0530, Hema HK wrote:
>@@ -212,8 +228,28 @@ void __init usb_musb_init(struct omap_mu
> musb_plat.mode = board_data->mode;
> musb_plat.extvbus = board_data->extvbus;
>
>- if (platform_device_register(&musb_device) < 0)
>- printk(KERN_ERR "Unable to register HS-USB (MUSB) device\n");
>+ if (cpu_is_omap3517() || cpu_is_omap3505()) {
>+
>+ if (platform_device_register(&musb_device) < 0)
>+ printk(KERN_ERR "Unable to register HS-USB \
>+ (MUSB) device\n");
>+ } else {
you can amend these two branches to the previous one. move the
platform_device_register() to the previous if (cpu_is_omap3517() ||
cpu_is_omap3505()) check. similarly with the code below.
>+ pdata = &musb_plat;
>+ od = omap_device_build(name, bus_id, oh, pdata,
>+ sizeof(*pdata), omap_musb_latency,
>+ ARRAY_SIZE(omap_musb_latency), false);
>+ if (IS_ERR(od)) {
>+ pr_err("Could not build omap_device for %s %s\n",
>+ name, oh_name);
>+ return;
>+ }
>+ pdev = &od->pdev;
>+ dev = &pdev->dev;
>+ get_device(dev);
>+ dev->dma_mask = &musb_dmamask;
>+ dev->coherent_dma_mask = musb_dmamask;
>+ put_device(dev);
>+ }
> }
>
> #else
--
balbi
next prev parent reply other threads:[~2010-12-10 13:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 12:53 [PATCH 4/5 v4] OMAP2+: musb: HWMOD adaptation for musb Hema HK
2010-12-10 13:02 ` Felipe Balbi [this message]
2010-12-10 13:28 ` Kalliguddi, Hema
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=20101210130232.GL6027@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--cc=b-cousson@ti.com \
--cc=hemahk@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=tony@atomide.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