linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Anton Vorontsov <avorontsov@ru.mvista.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, 26 Dec 2007 19:58:16 +0300	[thread overview]
Message-ID: <20071226165816.GB11449@localhost.localdomain> (raw)
In-Reply-To: <11970458703666-git-send-email-timur@freescale.com>

On Fri, Dec 07, 2007 at 10:44:30AM -0600, Timur Tabi wrote:
> Add support for UART serial ports using a Freescale QUICC Engine
> (found on some MPC83xx and MPC85xx SOCs).
> 
> Updated booting-without-of.txt to define new properties for a QE UART node,
> and a new node definition that describes uploaded QE firmware.
> 
> Because of a silicon bug in some QE-enabled SOCs (e.g. 8323 and 8360), a new
> microcode is required. This microcode implements UART via a work-around,
> hence it's called "Soft-UART".  This driver can use the QE firmware upload
> feature to upload the correct microcode to the QE.
> 
> Signed-off-by: Timur Tabi <timur@freescale.com>
> ---

> @@ -250,6 +279,26 @@
>  			pio-handle = < &pio4 >;
>  		};
>  
> +		ucc@2400 {
> +			device_type = "serial";
> +			compatible = "ucc_uart";
> +			model = "UCC";

model isn't used, is it needed at all?

> +			device-id = <5>;	/* The UCC number, 1-7*/
> +			port-number = <0>;	/* Which ttyQEx device */
> +			soft-uart;		/* We need Soft-UART */
> +			reg = <2400 200>;
> +			interrupts = <28>;	/* From Table 18-12 */
> +			interrupt-parent = < &qeic >;
> +			/*
> +			 * For Soft-UART, we need to set TX to 1X, which
> +			 * means specifying separate clock sources.
> +			 */
> +			rx-clock-name = "brg5";
> +			tx-clock-name = "brg6";
> +			pio-handle = < &pio5 >;
[...]
> +	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.

> +			firmware_loaded = 1;
> +		} else {
> +			char filename[32];
> +			unsigned int soc;
> +			unsigned int rev_h;
> +			unsigned int rev_l;
> +
> +			soc = soc_info(&rev_h, &rev_l);
> +			if (!soc) {
> +				dev_err(&ofdev->dev, "unknown CPU model\n");
> +				return -ENXIO;
> +			}
> +			sprintf(filename, "fsl_qe_ucode_uart_%u_%u%u.bin",
> +				soc, rev_h, rev_l);
> +
> +			dev_info(&ofdev->dev, "waiting for firmware %s\n",
> +				filename);
> +
> +			/*
> +			 * We call request_firmware_nowait instead of
> +			 * request_firmware so that the driver can load and
> +			 * initialize the ports without holding up the rest of
> +			 * the kernel.  If hotplug support is enabled in the
[...]
> +
> +	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.

> +	if (!np) {
> +		dev_err(&ofdev->dev, "could not find parent 'qe' node\n");
> +		kfree(qe_port);
> +		return -EINVAL;
> +	}
> +
[...]
> +static struct of_platform_driver ucc_uart_of_driver = {
> +	.owner  	= THIS_MODULE,
> +	.name   	= "ucc_uart",

Maybe better fsl,ucc_uart?


Thanks,

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

  reply	other threads:[~2007-12-26 16:56 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 [this message]
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

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=20071226165816.GB11449@localhost.localdomain \
    --to=avorontsov@ru.mvista.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).