From: Kevin Hilman <khilman@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: l-o <linux-omap@vger.kernel.org>,
l-a <linux-arm-kernel@lists.infradead.org>,
Tony <tony@atomide.com>, Steve Sakoman <steve@sakoman.com>,
Maximilian Schwerin <mvs@tigris.de>
Subject: Re: [PATCH] OMAP2+: OPP: allow OPP enumeration to continue if device is not present
Date: Mon, 19 Mar 2012 14:48:31 -0700 [thread overview]
Message-ID: <8739945kk0.fsf@ti.com> (raw)
In-Reply-To: <1331914749-23171-1-git-send-email-nm@ti.com> (Nishanth Menon's message of "Fri, 16 Mar 2012 11:19:09 -0500")
Nishanth Menon <nm@ti.com> writes:
> On platforms such as OMAP3, certain variants may not have IVA, SGX
> or some specific component. We currently have a check to aid fixing
> wrong population of OPP entries for issues such as typos. This however
> causes a conflict with valid requirement where the SoC variant does
> not actually have the module present.
>
> So, reduce the severity of the print to a debug statement and skip
> registering that specific OPP, but continue down the list.
>
> Reported-by: Steve Sakoman <steve@sakoman.com>
> Reported-by: Maximilian Schwerin <mvs@tigris.de>
> Acked-by: Steve Sakoman <steve@sakoman.com>
> Tested-by: Maximilian Schwerin <mvs@tigris.de>
> Signed-off-by: Nishanth Menon <nm@ti.com>
Thanks, queuing as a fix for for v3.4-rc (branch: for_3.4/fixes/pm)
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] OMAP2+: OPP: allow OPP enumeration to continue if device is not present
Date: Mon, 19 Mar 2012 14:48:31 -0700 [thread overview]
Message-ID: <8739945kk0.fsf@ti.com> (raw)
In-Reply-To: <1331914749-23171-1-git-send-email-nm@ti.com> (Nishanth Menon's message of "Fri, 16 Mar 2012 11:19:09 -0500")
Nishanth Menon <nm@ti.com> writes:
> On platforms such as OMAP3, certain variants may not have IVA, SGX
> or some specific component. We currently have a check to aid fixing
> wrong population of OPP entries for issues such as typos. This however
> causes a conflict with valid requirement where the SoC variant does
> not actually have the module present.
>
> So, reduce the severity of the print to a debug statement and skip
> registering that specific OPP, but continue down the list.
>
> Reported-by: Steve Sakoman <steve@sakoman.com>
> Reported-by: Maximilian Schwerin <mvs@tigris.de>
> Acked-by: Steve Sakoman <steve@sakoman.com>
> Tested-by: Maximilian Schwerin <mvs@tigris.de>
> Signed-off-by: Nishanth Menon <nm@ti.com>
Thanks, queuing as a fix for for v3.4-rc (branch: for_3.4/fixes/pm)
Kevin
next prev parent reply other threads:[~2012-03-19 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 16:19 [PATCH] OMAP2+: OPP: allow OPP enumeration to continue if device is not present Nishanth Menon
2012-03-16 16:19 ` Nishanth Menon
2012-03-19 21:48 ` Kevin Hilman [this message]
2012-03-19 21:48 ` Kevin Hilman
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=8739945kk0.fsf@ti.com \
--to=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=mvs@tigris.de \
--cc=nm@ti.com \
--cc=steve@sakoman.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.