linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Anton Vorontsov <cbouatmailru@gmail.com>
To: Timur Tabi <timur@freescale.com>
Cc: Scott Wood <scottwood@freescale.com>, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v2] ucc_uart: add support for Freescale QUICCEngine UART
Date: Fri, 4 Jan 2008 02:41:50 +0300	[thread overview]
Message-ID: <20080103234150.GA24052@zarina> (raw)
In-Reply-To: <477D28D3.3000102@freescale.com>

On Thu, Jan 03, 2008 at 12:26:27PM -0600, Timur Tabi wrote:
> Scott Wood wrote:
> 
> >>>> +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.
> 
> Wait, I'm confused.  What does the of_platform_driver.name string have to do 
> with the compatible field in the device tree?  Like I said earlier, I'm just 

Eh, initially I meant compatible stuff, not the driver name. I've quoted
wrong code snippet, thus the confusion.

You're using "ucc_uart" for compatible matching:

> +static struct of_device_id ucc_uart_match[] = {
> +       {
> +               .type = "serial",
> +               .compatible = "ucc_uart",

here "fsl,qe-uart" will look better, no?

> +       },
> +       {},
> +};
> +MODULE_DEVICE_TABLE(of, ucc_uart_match);

Thanks,

-- 
Anton Vorontsov
email: cbou@mail.ru
backup email: ya-cbou@yandex.ru
irc://irc.freenode.net/bd2

      parent reply	other threads:[~2008-01-03 23:54 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
2008-01-03 18:26       ` Timur Tabi
2008-01-03 18:26         ` Scott Wood
2008-01-03 23:41         ` Anton Vorontsov [this message]

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=20080103234150.GA24052@zarina \
    --to=cbouatmailru@gmail.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@freescale.com \
    --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).