From: Timur Tabi <timur@freescale.com>
To: avorontsov@ru.mvista.com
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v2] ucc_uart: add support for Freescale QUICCEngine UART
Date: Sat, 29 Dec 2007 16:10:54 -0600 [thread overview]
Message-ID: <4776C5EE.70004@freescale.com> (raw)
In-Reply-To: <20071226165816.GB11449@localhost.localdomain>
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.
>> + if (soft_uart) {
>> + struct qe_firmware_info *qe_fw_info;
>> +
>> + qe_fw_info = qe_get_firmware_info();
>> +
>> + /* Check if the firmware has been uploaded. */
>> + if (strstr(qe_fw_info->id, "Soft-UART")) {
>
> qe_fw_info used w/o NULL checking.
Ok.
> [...]
>> +
>> + qe_port->port.irq = irq_of_parse_and_map(np, 0);
>> + if (qe_port->port.irq == NO_IRQ) {
>> + dev_err(&ofdev->dev, "could not map IRQ for UCC%u\n",
>> + qe_port->ucc_num + 1);
>> + kfree(qe_port);
>> + return -EINVAL;
>> + }
>> +
>> + np = of_find_node_by_type(NULL, "qe");
>
> Please, add "fsl,qe" compatible matching.
Ok.
>> +static struct of_platform_driver ucc_uart_of_driver = {
>> + .owner = THIS_MODULE,
>> + .name = "ucc_uart",
>
> Maybe better fsl,ucc_uart?
The CPM serial driver uses "cpm_uart" and the QE ethernet driver uses
"ucc_geth", so ucc_uart matches the pattern.
next prev parent reply other threads:[~2007-12-29 22:10 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 [this message]
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
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=4776C5EE.70004@freescale.com \
--to=timur@freescale.com \
--cc=avorontsov@ru.mvista.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).