linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	David Woodhouse <dwmw2@infradead.org>,
	linuxppc-embedded list <linuxppc-embedded@ozlabs.org>
Subject: Re: [PATCH] Use platform device for 8250 registration
Date: Wed, 17 Aug 2005 16:34:38 +1000	[thread overview]
Message-ID: <1124260479.8849.28.camel@gaston> (raw)
In-Reply-To: <11F30454-6808-44A3-8F5B-F36ED0028EF4@freescale.com>

On Wed, 2005-08-17 at 01:30 -0500, Kumar Gala wrote:
> On Aug 16, 2005, at 11:21 AM, David Woodhouse wrote:
> 
> > My dual G4 PowerMac crashes sometimes when it probes for the (absent)
> > serial ports. Theoretically it's supposed to take a machine check and
> > recover -- but it doesn't always work like that.
> >
> > This patch removes the defaults from asm/pc_serial.h and uses the code
> > which already existed for ppc64 to register any ports which are  
> > found in
> > the device tree. It's slightly updated to work in 32-bit and also  
> > on the
> > Pegasos which claims the input frequency is 0Hz.
> >
> > We could probably remove all the rest of the crap from asm/serial.h  
> > and
> > let platforms register their own serial8250 platform devices. And this
> > probably breaks serial ports on PReP, which needs to do likewise.
> 
> Hmm, I wondering if we can provide some standard way of handling this  
> for the embedded platforms as well.  It would be nice to drop the old  
> style of initialization completely and move to using a platform  
> device always.

Sure, if they have a device-tree :) The code from ppc64 could be useable
there too. For others, they need to create their ports which whatever
mecanism they have to "know" where the port actually is ... little
common code here... but then, instanciating a platform device is easy.

Ben.

  reply	other threads:[~2005-08-17  6:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16 16:21 [PATCH] Use platform device for 8250 registration David Woodhouse
2005-08-17  6:30 ` Kumar Gala
2005-08-17  6:34   ` Benjamin Herrenschmidt [this message]
2005-08-17  7:31   ` David Woodhouse
2005-08-17 13:54     ` Kumar Gala
2005-08-17 15:05     ` Tom Rini
2005-08-17 15:22       ` Kumar Gala
2005-08-17 15:30         ` Tom Rini
2005-08-17 16:16           ` Kumar Gala
2005-08-17 16:27             ` Matt Porter
2005-08-17 16:35               ` Tom Rini
2005-08-17 16:27             ` Tom Rini
2005-08-17 11:11 ` Russell King
2005-08-17 16:39   ` David Woodhouse
2005-08-17 16:46     ` Russell King
2005-08-17 14:00 ` When are machine checks suppose to be recoverable? Kumar Gala
2005-08-17 21:44   ` Benjamin Herrenschmidt
2005-08-17 22:30     ` David Woodhouse
2005-08-18  3:42       ` Kumar Gala
2005-08-23  2:56         ` Marcelo Tosatti
2005-08-23 16:43           ` David Woodhouse
2005-08-23 17:04             ` Kumar Gala
2005-08-23 23:10               ` David Woodhouse

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=1124260479.8849.28.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=dwmw2@infradead.org \
    --cc=kumar.gala@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc-embedded@ozlabs.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).