From: b-cousson@ti.com (Cousson, Benoit)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: omap: hwmod: warn only when clkdm is missing from both clk and hwmod
Date: Wed, 18 Apr 2012 10:09:39 +0200 [thread overview]
Message-ID: <4F8E76C3.7080803@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1204121106010.29473@utopia.booyaka.com>
Hi Paul,
On 4/12/2012 7:06 PM, Paul Walmsley wrote:
> Hi
>
> On Thu, 12 Apr 2012, Rajendra Nayak wrote:
>
>> On OMAP4+, the clkdm association is moved to hwmod while on older OMAPs'
>> its associated with a clk.
>
> Sounds like this should be conditional based on the platform, then,
> rather than weakening the warning for all platforms ?
Well, as already discussed the clockdomain information is mostly useless
for most clock nodes because the HW is taking care of the dependencies,
so highlighting only the ones missing in hwmod is far from enough and
will avoid scaring people with something that is normal.
Considering that OMAP4 clock domain partition is way more complex than
it was on OMAP2 & 3, if OMAP4 can leave without that, I doubt OMAP2 & 3
clock nodes will ever need it, except HW bugs, as usual.
But still, it is an exception more than the regular case.
>> Hence look for a clkdm in both clk and hwmod and warn only when
>> its missing in both. Also fix the pr_warning() to print the correct
>> hwmod name.
>>
>> Signed-off-by: Rajendra Nayak<rnayak@ti.com>
Acked-by: Benoit Cousson <b-cousson@ti.com>
Regards,
Benoit
next prev parent reply other threads:[~2012-04-18 8:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 13:41 [PATCH] ARM: omap: hwmod: warn only when clkdm is missing from both clk and hwmod Rajendra Nayak
2012-04-12 17:06 ` Paul Walmsley
2012-04-18 8:09 ` Cousson, Benoit [this message]
2012-04-18 8:52 ` Paul Walmsley
2012-04-18 9:08 ` Paul Walmsley
2012-04-18 9:09 ` Cousson, Benoit
2012-04-18 9:40 ` Paul Walmsley
2012-04-18 9:57 ` Cousson, Benoit
2012-04-18 10:12 ` Paul Walmsley
2012-04-18 10:29 ` Cousson, Benoit
2012-04-18 10:53 ` Paul Walmsley
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=4F8E76C3.7080803@ti.com \
--to=b-cousson@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).