From: "Cousson, Benoit" <b-cousson@ti.com>
To: "Kalliguddi, Hema" <hemahk@ti.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Felipe Balbi <felipe.balbi@nokia.com>,
Tony Lindgren <tony@atomide.com>,
Kevin Hilman <khilman@deeprootsystems.com>
Subject: Re: [PATCH 4/8]usb: musb: HWMOD database structures fixes OMAP4
Date: Mon, 09 Aug 2010 13:52:04 +0200 [thread overview]
Message-ID: <4C5FEBE4.1060707@ti.com> (raw)
In-Reply-To: <1281110249-4098-1-git-send-email-hemahk@ti.com>
Hi Hema,
On 8/6/2010 5:57 PM, Kalliguddi, Hema wrote:
> From: Hema HK<hemahk@ti.com>
>
> Fixed the missing sysc settings for OMAP4 and enabled the OMAP4
> hwmod data structure.
>
> Signed-off-by: Hema HK<hemahk@ti.com>
> Cc: Felipe Balbi<felipe.balbi@nokia.com>
> Cc: Tony Lindgren<tony@atomide.com>
> Cc: Kevin Hilman<khilman@deeprootsystems.com>
It is a good practice, if not mandatory, to CC the authors of the file
you are modifying with your patch.
Neither Paul, nor myself are in CC of this patch. Could you please add
us to this one and the other ones when applicable?
> ---
>
> Index: linux-omap-pm/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> ===================================================================
> --- linux-omap-pm.orig/arch/arm/mach-omap2/omap_hwmod_44xx_data.c 2010-08-06 08:31:45.885868560 -0400
> +++ linux-omap-pm/arch/arm/mach-omap2/omap_hwmod_44xx_data.c 2010-08-06 08:35:41.250112281 -0400
> @@ -4516,8 +4516,15 @@
> */
>
> static struct omap_hwmod_class_sysconfig omap44xx_usb_otg_hs_sysc = {
> - .sysc_flags = SYSS_MISSING,
> - .idlemodes = (SIDLE_FORCE | SIDLE_NO | SIDLE_SMART),
> +
> + .rev_offs = 0x0400,
> + .sysc_offs = 0x0404,
> + .syss_offs = 0x0408,
> + .sysc_flags = SYSC_HAS_SIDLEMODE | SYSC_HAS_MIDLEMODE|
> + SYSC_HAS_ENAWAKEUP | SYSC_HAS_SOFTRESET |
> + SYSC_HAS_AUTOIDLE,
> + .idlemodes = SIDLE_FORCE | SIDLE_NO | SIDLE_SMART,
> + .sysc_fields =&omap_hwmod_sysc_type1,
> };
This part if fine except the missing MIDLE_XXX modes. Here is the
modified version using the same convention as other modules:
> static struct omap_hwmod_class_sysconfig omap44xx_usb_otg_hs_sysc = {
> - .sysc_flags = SYSS_MISSING,
> - .idlemodes = (SIDLE_FORCE | SIDLE_NO | SIDLE_SMART),
> + .rev_offs = 0x0400,
> + .sysc_offs = 0x0404,
> + .syss_offs = 0x0408,
> + .sysc_flags = (SYSC_HAS_AUTOIDLE | SYSC_HAS_ENAWAKEUP |
> + SYSC_HAS_MIDLEMODE | SYSC_HAS_SIDLEMODE |
> + SYSC_HAS_SOFTRESET),
> + .idlemodes = (SIDLE_FORCE | SIDLE_NO | SIDLE_SMART |
> + MSTANDBY_FORCE | MSTANDBY_NO |
MSTANDBY_SMART),
> + .sysc_fields = &omap_hwmod_sysc_type1,
> };
I don't have any preference for the parens, but in order to be
consistent with the already existing hwmods, let's keep them.
Regards,
Benoit
next prev parent reply other threads:[~2010-08-09 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 15:57 [PATCH 4/8]usb: musb: HWMOD database structures fixes OMAP4 Hema HK
2010-08-09 11:52 ` Cousson, Benoit [this message]
[not found] ` <4C5FEBE4.1060707-l0cyMroinI0@public.gmane.org>
2010-08-10 5:12 ` 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=4C5FEBE4.1060707@ti.com \
--to=b-cousson@ti.com \
--cc=felipe.balbi@nokia.com \
--cc=hemahk@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).