linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Timur Tabi <timur@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v2] ucc_uart: add support for Freescale QUICCEngine UART
Date: Wed, 2 Jan 2008 12:12:26 -0600	[thread overview]
Message-ID: <20080102181226.GA4486@loki.buserror.net> (raw)
In-Reply-To: <4776C5EE.70004@freescale.com>

On Sat, Dec 29, 2007 at 04:10:54PM -0600, Timur Tabi wrote:
> Anton Vorontsov wrote:
> 
> >> +		ucc@2400 {
> >> +			device_type = "serial";
> >> +			compatible = "ucc_uart";
> >> +			model = "UCC";
> > 
> > model isn't used, is it needed at all?
> 
> I have no idea, but all the other UCC nodes have it, so I'm going to 
> keep it.  Maybe one day we'll merge QE and CPM drivers, so this would be 
> useful.

No, it wouldn't -- that's what compatible is for.

> >> +static struct of_platform_driver ucc_uart_of_driver = {
> >> +	.owner  	= THIS_MODULE,
> >> +	.name   	= "ucc_uart",
> > 
> > Maybe better fsl,ucc_uart?

fsl,qe-uart is defined by Documentation/powerpc/booting-without-of.txt.

> The CPM serial driver uses "cpm_uart" and the QE ethernet driver uses 
> "ucc_geth", so ucc_uart matches the pattern.

cpm_uart is a legacy match -- the current binding specifies
fsl,cpm1-smc-uart, fsl,cpm2-scc-uart, etc.

-Scott

  reply	other threads:[~2008-01-02 18:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-07 16:44 [PATCH v2] ucc_uart: add support for Freescale QUICCEngine UART Timur Tabi
2007-12-26 16:58 ` Anton Vorontsov
2007-12-29 22:10   ` Timur Tabi
2008-01-02 18:12     ` Scott Wood [this message]
2008-01-03 18:26       ` Timur Tabi
2008-01-03 18:26         ` Scott Wood
2008-01-03 23:41         ` Anton Vorontsov

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=20080102181226.GA4486@loki.buserror.net \
    --to=scottwood@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=timur@freescale.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 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).