From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: "Grygorii.Strashko@linaro.org" <grygorii.strashko@linaro.org>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
nsekhar@ti.com, linux-omap@vger.kernel.org,
sumit.semwal@linaro.org, linux-arm-kernel@lists.infradead.org,
nm@ti.com, t-kristo@ti.com
Subject: Re: [PATCH 2/2] ARM: dts: dra7: remove ti,hwmod property from pcie phy
Date: Thu, 19 Mar 2015 09:03:02 -0700 [thread overview]
Message-ID: <20150319160301.GE31346@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1503191541270.9480@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [150319 08:46]:
> On Thu, 19 Mar 2015, Grygorii.Strashko@linaro.org wrote:
>
> > On 03/19/2015 04:55 PM, Paul Walmsley wrote:
> > > On Wed, 18 Mar 2015, Grygorii.Strashko@linaro.org wrote:
> > >
> > > > On 03/18/2015 06:57 PM, Tony Lindgren wrote:
> > > > > * Grygorii Strashko <grygorii.strashko@ti.com> [150318 09:37]:
> > > > > > As I can see Patch 1 from this series was merged in 4.0-rc4,
> > > > > > but this patch wasn't. As result, I can see below warning all the time
> > > > > > during boot now:
> > > > > >
> > > > > > [ 0.594591] platform 4a094000.pciephy: Cannot lookup hwmod
> > > > > > 'pcie1-phy'
> > > > >
> > > > > OK. Is this needed as a fix for the v4.0-rc series, or can this wait
> > > > > for v4.1?
> > > >
> > > > I think, Yes. These two patches should go all together, because they are
> > > > interrelated.
> > >
> > > Does the warning result in a functional problem, or is it just a warning?
> > >
> >
> > PCE1 PHY device is not registered any more.
>
> How does the second patch fix that?
It seems it should be just a warning fix if the pciephy hwmod entries
are now gone?
Anyways, I'm planning to send a pull request for omap-for-v4.0/fixes
today. Please let me know ASAP if the $subject patch should be dropped,
otherwise I'll send it as it fixes a boot time warning and is already
applied.
Regards,
Tony
next prev parent reply other threads:[~2015-03-19 16:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 8:51 [PATCH 1/2] ARM: DRA7: hwmod_data: Fix hwmod data for pcie Kishon Vijay Abraham I
2015-02-20 8:51 ` [PATCH 2/2] ARM: dts: dra7: remove ti,hwmod property from pcie phy Kishon Vijay Abraham I
2015-03-18 16:36 ` Grygorii Strashko
2015-03-18 16:57 ` Tony Lindgren
2015-03-18 19:36 ` Grygorii.Strashko@linaro.org
2015-03-18 20:23 ` Tony Lindgren
2015-03-19 14:55 ` Paul Walmsley
2015-03-19 15:39 ` Grygorii.Strashko@linaro.org
2015-03-19 15:45 ` Paul Walmsley
2015-03-19 16:03 ` Tony Lindgren [this message]
2015-03-19 16:36 ` Paul Walmsley
2015-03-19 16:21 ` Grygorii.Strashko@linaro.org
2015-03-19 16:49 ` Paul Walmsley
2015-03-25 22:53 ` Kishon Vijay Abraham I
2015-03-26 7:29 ` Paul Walmsley
2015-03-02 4:05 ` [PATCH 1/2] ARM: DRA7: hwmod_data: Fix hwmod data for pcie 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=20150319160301.GE31346@atomide.com \
--to=tony@atomide.com \
--cc=grygorii.strashko@linaro.org \
--cc=grygorii.strashko@ti.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=paul@pwsan.com \
--cc=sumit.semwal@linaro.org \
--cc=t-kristo@ti.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;
as well as URLs for NNTP newsgroup(s).