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: [RFC PATCH 0/3] ARM: omap3: add Seagate Wireless Plus board
Date: Thu, 9 May 2013 09:05:52 -0700	[thread overview]
Message-ID: <20130509160551.GC31554@atomide.com> (raw)
In-Reply-To: <20130509155645.GB31554@atomide.com>

* Tony Lindgren <tony@atomide.com> [130509 09:03]:
> * Jason Cooper <jason@lakedaemon.net> [130508 17:41]:
> > On Wed, May 08, 2013 at 12:45:04PM -0700, Tony Lindgren wrote:
> > > * Jason Cooper <jason@lakedaemon.net> [130508 12:29]:
> > > > 
> > > > Tony has been helping me out offline with this, and he suggested trying the
> > > > gpmc against Linus' ToT.  Which locks up before it even has a chance to get
> > > > going.  So this series is against v3.9.
> > > 
> > > You may have better luck with today's mainline treeand the following fix:
> > > 
> > > http://lkml.org/lkml/2013/5/8/374#
> > 
> > Ok, I'm attempting to do that, but got this for 'make dtbs':
> > 
> > ERROR (phandle_references): Reference to non-existent node or label "usb2_phy"
> > 
> > ERROR: Input tree has errors, aborting (use -f to force output)
> > make[1]: *** [arch/arm/boot/dts/omap3-wireless_plus.dtb] Error 2
> > make[1]: *** Waiting for unfinished jobs....
> > make: *** [dtbs] Error 2
> > 
> > which was created by:
> > 
> >   ad871c10 ARM: dts: OMAP: Add usb_otg and glue data to OMAP3+ boards
> > 
> > It assumes the board has twl4030 (and then includes it).  Bootlogs from
> > the vendor provided kernel don't show a single message from twl4030, so
> > I've omitted it.
> > 
> > Assuming I did the correct thing by omitting the twl4030, I think the
> > correct answer is to declare the phy in the dts files, like so:
> 
> Thanks, that is correct. We should not assume any PMIC with a processor
> as it can also be a custom chip. For example, Nokia n8x0 is using their
> retu + tahvo chips instead of tps chips.
> 
> I'll apply your patch into omap-for-v3.10/fixes.

I mean omap-for-v3.10/dt-fixes instead of fixes since it's .dts changes.
 
> Regards,
> 
> Tony
>  
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2013-05-09 16:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-08 19:23 [RFC PATCH 0/3] ARM: omap3: add Seagate Wireless Plus board Jason Cooper
2013-05-08 19:23 ` [RFC PATCH 1/3] ARM: omap3: " Jason Cooper
2013-05-08 19:23 ` [RFC PATCH 2/3] ARM: omap3: Seagate Wireless Plus DT entry Jason Cooper
2013-05-08 19:23 ` [RFC PATCH 3/3] ARM: omap3: wireless plus gpmc wip Jason Cooper
2013-05-08 19:45 ` [RFC PATCH 0/3] ARM: omap3: add Seagate Wireless Plus board Tony Lindgren
2013-05-09  0:36   ` Jason Cooper
2013-05-09 15:56     ` Tony Lindgren
2013-05-09 16:05       ` Tony Lindgren [this message]
2013-05-08 19:51 ` Tony Lindgren
2013-05-08 21:58   ` Jason Cooper
2013-05-08 22:30     ` Tony Lindgren

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=20130509160551.GC31554@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).