[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAP05o4K71CuWqePZPa0wc7zRGaXdO4oYosCOSvybgqs0qZjx5Q@mail.gmail.com>
Date: Tue, 4 Oct 2011 17:27:23 +0530
From: "Munegowda, Keshava" <keshava_mgowda@...com>
To: Kevin Hilman <khilman@...com>
Cc: Paul Walmsley <paul@...an.com>, linux-usb@...r.kernel.org,
linux-omap@...r.kernel.org, linux-kernel@...r.kernel.org,
balbi@...com, b-cousson@...com, gadiyar@...com,
sameo@...ux.intel.com, parthab@...ia.ti.com, tony@...mide.com,
johnstul@...ibm.com, vishwanath.bs@...com
Subject: Re: [PATCH 2/5 v12] arm: omap: usb: ehci and ohci hwmod structures
for omap3
On Fri, Sep 30, 2011 at 10:47 PM, Kevin Hilman <khilman@...com> wrote:
> "Munegowda, Keshava" <keshava_mgowda@...com> writes:
>
> [...]
>
>>>> +
>>>> +static struct omap_hwmod_ocp_if omap34xx_f_cfg__usb_tll_hs = {
>>>> + .clk = "usbtll_ick",
>>>> + .user = OCP_USER_MPU,
>>>> + .flags = OCPIF_SWSUP_IDLE,
>>>> +};
>>>
>>> Does this really need OCPIF_SWSUP_IDLE? If so, then there is a hardware
>>> bug, and some explanation is needed.
>>
>>
>> it was not allowing enter usbhs pw domain to enter to low power idle mode; so
>> I add a comment here.
>>
>
> When you add this comment, please be sure it describes *why* the power
> domain was not hitting the target power state, and reference any
> relevant eerrata.
I will add the errata description and id
regards
keshava
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists