linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: dts: dra7: remove ti,hwmod property from pcie phy
Date: Wed, 18 Mar 2015 13:23:53 -0700	[thread overview]
Message-ID: <20150318202353.GU31346@atomide.com> (raw)
In-Reply-To: <5509D3BD.6030004@linaro.org>

* Grygorii.Strashko at linaro.org <grygorii.strashko@linaro.org> [150318 12:36]:
> 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.

OK applying into omap-for-v4.0/fixes thanks.

Tony
 
> >> On 02/20/2015 10:51 AM, Kishon Vijay Abraham I wrote:
> >>> Now that we don't have hwmod entry for pcie PHY remove the
> >>> ti,hwmod property from PCIE PHY's
> >>>
> >>> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
> >>> ---
> >>>    arch/arm/boot/dts/dra7.dtsi |    2 --
> >>>    1 file changed, 2 deletions(-)
> >>>
> >>> diff --git a/arch/arm/boot/dts/dra7.dtsi b/arch/arm/boot/dts/dra7.dtsi
> >>> index 5827fed..18a904d 100644
> >>> --- a/arch/arm/boot/dts/dra7.dtsi
> >>> +++ b/arch/arm/boot/dts/dra7.dtsi
> >>> @@ -1111,7 +1111,6 @@
> >>>    					      "wkupclk", "refclk",
> >>>    					      "div-clk", "phy-div";
> >>>    				#phy-cells = <0>;
> >>> -				ti,hwmods = "pcie1-phy";
> >>>    			};
> >>>    
> >>>    			pcie2_phy: pciephy at 4a095000 {
> >>> @@ -1130,7 +1129,6 @@
> >>>    					      "wkupclk", "refclk",
> >>>    					      "div-clk", "phy-div";
> >>>    				#phy-cells = <0>;
> >>> -				ti,hwmods = "pcie2-phy";
> >>>    				status = "disabled";
> >>>    			};
> >>>    		};
> >>>
> >>
> 
> 
> -- 
> regards,
> -grygorii

  reply	other threads:[~2015-03-18 20:23 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 [this message]
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
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=20150318202353.GU31346@atomide.com \
    --to=tony@atomide.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).