All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 0/4] arch/powerpc support for SBC8560 board
Date: Fri, 21 Dec 2007 14:59:52 +1100	[thread overview]
Message-ID: <20071221035952.GB5930@localhost.localdomain> (raw)
In-Reply-To: <20071221033815.GA13921@windriver.com>

On Thu, Dec 20, 2007 at 10:38:15PM -0500, Paul Gortmaker wrote:
> In message: Re: [PATCH 0/4] arch/powerpc support for SBC8560 board
> on 20/12/2007 Kumar Gala wrote:
> 
> >> 3) Add device tree source for Wind River SBC8560 board
> >>
> >> This is probably the most interesting part of the group, given that the
> >> board doesn't use the CPM2 to provide the serial console.  I've made a
> >> duart dts entry that is kind of similar to what is done for the tsi108
> >> on the mpc7448/hpc-ii board, and made sure that the serial had their
> >> parent marked as "soc" (found out the hard way that UARTs were ignored
> >> as possible consoles unless they were soc or tsi108 children...)
> >>
> >> b/arch/powerpc/boot/dts/sbc8560.dts |  203 
> >> +++++++++++++++++++++++++++++++++++-
> >
> > we need to figure out to fix this so we don't need the parent marked as 
> > 'soc'.
> 
> Here is my interpretation of what is happening here -- we come in via
> find_legacy_serial_ports() to pick a console port.  It grabs "chosen"
> to get np stdout, and then checks the parent of the 16550 compat ports
> against the following, requiring at least one of them to match:
> 
> 	parent->type == "soc" ? add_legacy_soc_port()
> 
> 	parent->type == "isa" ? add_legacy_isa_port()
> 
> 	parent->type == "tsi-bridge" ? add_legacy_soc_port()
> 
> 	parent->type == "opb" ? add_legacy_soc_port()
> 
> No match means no serial console, it seems.

Not necessarily.  If the port is picked up by the of_serial driver it
should work.  The drawback is that the console will be initialized
rather late by this method.

>  I figured that parent == "soc"
> was the lesser lie to choose from, but I'm open to an alternate approach 
> that is less apt to make David go "ewww" (an understandable
> reaction...).

Lying in the device tree like this is just bad.  Adding another case
to legacy_serial for your specific case would be ugly but infinitely
preferable to mislabelling the node with type "doc".

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

  reply	other threads:[~2007-12-21  3:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-20 14:54 [PATCH 0/4] arch/powerpc support for SBC8560 board Paul Gortmaker
2007-12-20 14:54 ` [PATCH 1/4] sbc8560: add basic support for Wind River SBC8560 as powerpc Paul Gortmaker
2007-12-20 14:54   ` Paul Gortmaker
2007-12-20 23:14     ` Stephen Rothwell
2007-12-21 15:37       ` Paul Gortmaker
2007-12-20 23:49     ` Kumar Gala
2007-12-20 14:54   ` [PATCH 2/4] CPM2: Make support for the CPM2 optional on 8560 based boards Paul Gortmaker
2007-12-20 14:54     ` Paul Gortmaker
2007-12-20 14:54   ` [PATCH 3/4] sbc8560: Add device tree source for Wind River SBC8560 board Paul Gortmaker
2007-12-20 14:54     ` Paul Gortmaker
2007-12-20 23:54       ` Kumar Gala
2007-12-20 23:57     ` David Gibson
2007-12-21 17:40       ` Scott Wood
2007-12-20 14:54   ` [PATCH 4/4] sbc8560: Add default .config file for Wind River SBC8560 Paul Gortmaker
2007-12-20 14:54     ` Paul Gortmaker
2007-12-20 23:49 ` [PATCH 0/4] arch/powerpc support for SBC8560 board Kumar Gala
2007-12-21  0:00   ` Paul Gortmaker
2007-12-20 23:56 ` Kumar Gala
2007-12-21  3:38   ` Paul Gortmaker
2007-12-21  3:59     ` David Gibson [this message]
2007-12-21 17:31     ` Scott Wood

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=20071221035952.GB5930@localhost.localdomain \
    --to=david@gibson.dropbear.id.au \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paul.gortmaker@windriver.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.