linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Alexandros Kostopoulos" <akostop@inaccessnetworks.com>
To: "Alexandros Kostopoulos" <akostop@inaccessnetworks.com>,
	linuxppc-dev@ozlabs.org
Subject: Re: regarding cpm_uart and platform_bus_type
Date: Tue, 17 Jul 2007 15:15:15 +0300	[thread overview]
Message-ID: <op.tvlyyor0nhx3hy@phoenix> (raw)
In-Reply-To: <op.tvlxc2sjnhx3hy@phoenix>

Hm, it seems that, after all, cpm_uart works fine without any board  
specific code whatsoever. Sorry about the fuss. My mistake

Regards

Alex


On Tue, 17 Jul 2007 14:55:30 +0300, Alexandros Kostopoulos  
<akostop@inaccessnetworks.com> wrote:

> Hi all,
>
> I was wondering, since arch/powerpc is now based on device trees,  
> shouldn't the cpm_uart driver (or at least a branch of it for  
> arch/powerpc) be changed to use of_platform_bus_type instead of  
> platform_bus_type? In my opinion, cpm_uart driver should take all its  
> configuration (uart address base, ints etc) from dts (via the  
> of_platform code) without any intervention from board specific code. In  
> any case, given the current situation, how can I pass cpm_uart the  
> address/irq of the uarts? by hardcoding it in my board specific code?  
> mpc82xx_ads.c doesn't seem to have such code, and I was wondering how  
> SCC uarts work in this platform? Who initializes them?
>
> thank you
>
> Alex

  reply	other threads:[~2007-07-17 12:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-17 11:55 regarding cpm_uart and platform_bus_type Alexandros Kostopoulos
2007-07-17 12:15 ` Alexandros Kostopoulos [this message]
2007-07-17 16:53 ` 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=op.tvlyyor0nhx3hy@phoenix \
    --to=akostop@inaccessnetworks.com \
    --cc=linuxppc-dev@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).