From: Sebastien Guiriec <s-guiriec@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: "Benoît Cousson" <b-cousson@ti.com>,
"Tony Lindgren" <tony@atomide.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
"Peter Ujfalusi" <peter.ujfalusi@ti.com>,
"Liam Girdwood" <lrg@ti.com>, "Tero Kristo" <t-kristo@ti.com>,
"Jon Hunter" <jon-hunter@ti.com>
Subject: Re: [PATCH 1/3] ARM: OMAP2+: hwmod: rename flag to prevent hwmod code from touching IP block during init
Date: Fri, 4 Jan 2013 21:52:42 +0100 [thread overview]
Message-ID: <50E7411A.1030207@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1301041817460.25868@utopia.booyaka.com>
On 01/04/2013 07:19 PM, Paul Walmsley wrote:
> Hi Sebastien
>
> On Fri, 4 Jan 2013, Sebastien Guiriec wrote:
>
>> Rename HWMOD_EXT_OPT_MAIN_CLK flag to indicate that this IP block is
>> dependent on an off-chip functional clock that is not guaranteed to
>> be present during initialization. Same flag can be use for IP with
>> additional HW registers to control Auto IDLE mode.
>>
>> Signed-off-by: Sebastien Guiriec <s-guiriec@ti.com>
>
> We already have the HWMOD_NO_INIT_RESET flag. Wouldn't that accomplish
> the same goal?
I am assuming that it was HWMOD_INIT_NO_RESET flag. This is not solving
the issue. After boot with this mode some of same clocks are still not
gated.
>
> Also I think we can reset the AESS during init. I posted a patch for this
> a few months ago, but looks like it got lost. Will reply to one of your
> other patches with more details.
>
>
> - Paul
>
WARNING: multiple messages have this Message-ID (diff)
From: s-guiriec@ti.com (Sebastien Guiriec)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: OMAP2+: hwmod: rename flag to prevent hwmod code from touching IP block during init
Date: Fri, 4 Jan 2013 21:52:42 +0100 [thread overview]
Message-ID: <50E7411A.1030207@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1301041817460.25868@utopia.booyaka.com>
On 01/04/2013 07:19 PM, Paul Walmsley wrote:
> Hi Sebastien
>
> On Fri, 4 Jan 2013, Sebastien Guiriec wrote:
>
>> Rename HWMOD_EXT_OPT_MAIN_CLK flag to indicate that this IP block is
>> dependent on an off-chip functional clock that is not guaranteed to
>> be present during initialization. Same flag can be use for IP with
>> additional HW registers to control Auto IDLE mode.
>>
>> Signed-off-by: Sebastien Guiriec <s-guiriec@ti.com>
>
> We already have the HWMOD_NO_INIT_RESET flag. Wouldn't that accomplish
> the same goal?
I am assuming that it was HWMOD_INIT_NO_RESET flag. This is not solving
the issue. After boot with this mode some of same clocks are still not
gated.
>
> Also I think we can reset the AESS during init. I posted a patch for this
> a few months ago, but looks like it got lost. Will reply to one of your
> other patches with more details.
>
>
> - Paul
>
next prev parent reply other threads:[~2013-01-04 20:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 13:02 [PATCH 0/3] ARM: OMAP4: Enable AESS IP Sebastien Guiriec
2013-01-04 13:02 ` Sebastien Guiriec
2013-01-04 13:02 ` [PATCH 1/3] ARM: OMAP2+: hwmod: rename flag to prevent hwmod code from touching IP block during init Sebastien Guiriec
2013-01-04 13:02 ` Sebastien Guiriec
2013-01-04 18:19 ` Paul Walmsley
2013-01-04 18:19 ` Paul Walmsley
2013-01-04 20:52 ` Sebastien Guiriec [this message]
2013-01-04 20:52 ` Sebastien Guiriec
2013-01-04 13:02 ` [PATCH 2/3] ARM: OMAP4: hwmod data: do not enable or reset the AESS during kernel init Sebastien Guiriec
2013-01-04 13:02 ` Sebastien Guiriec
2013-01-04 18:35 ` Paul Walmsley
2013-01-04 18:35 ` Paul Walmsley
2013-01-04 20:27 ` Sebastien Guiriec
2013-01-04 20:27 ` Sebastien Guiriec
2013-01-07 8:12 ` Paul Walmsley
2013-01-07 8:12 ` Paul Walmsley
2013-01-04 13:02 ` [PATCH 3/3] OMAP4: hwmod data: Enable AESS hwmod device Sebastien Guiriec
2013-01-04 13:02 ` Sebastien Guiriec
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=50E7411A.1030207@ti.com \
--to=s-guiriec@ti.com \
--cc=b-cousson@ti.com \
--cc=jon-hunter@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=paul@pwsan.com \
--cc=peter.ujfalusi@ti.com \
--cc=t-kristo@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.