From: Felipe Balbi <balbi@ti.com>
To: Keshava Munegowda <keshava_mgowda@ti.com>
Cc: linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org, balbi@ti.com, gadiyar@ti.com,
sameo@linux.intel.com, parthab@india.ti.com, kishon@ti.com
Subject: Re: [PATCH] arm: omap: usb: clock enable typo fix in usbhs driver
Date: Fri, 22 Jul 2011 15:22:22 +0300 [thread overview]
Message-ID: <20110722122221.GG32058@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <1311084703-10266-1-git-send-email-keshava_mgowda@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]
Hi,
On Tue, Jul 19, 2011 at 07:41:43PM +0530, Keshava Munegowda wrote:
> From: Keshava Munegowda <Keshava_mgowda@ti.com>
$SUBJECT is quite weird. First, this is not a patch on arch/arm/*omap*/
so arm: omap: is already wrong. Also, "enable typo fix" is quite werid.
Something like: "mfd: omap-usb-host: fix clock API usage on
usbhs_disable()" would read better.
> The usbhs_disable function was invoking clk_enable api
> instead of clk_disable; The clk_disable is called to
^ this semicolon should be a period.
ok, you're missing the actual problem here. How about you extend it to
read as:
usbhs_disable function was invoking clk_enable() instead of
clk_disable(), thus only increasing the clock usage counter and
preventing this particular clock from being ever turned off.
Because of that, the power domain where the USB Host subsystem is
located, would never reach lower power states.
> disble the port clocks of usbhs
^^ disable.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-07-22 12:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 14:11 Keshava Munegowda
2011-07-22 12:22 ` Felipe Balbi [this message]
2011-07-22 12:27 ` Munegowda, Keshava
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=20110722122221.GG32058@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--cc=gadiyar@ti.com \
--cc=keshava_mgowda@ti.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=parthab@india.ti.com \
--cc=sameo@linux.intel.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
all inboxes | Powered by JetHome®