From: Stephen Warren <swarren@wwwdotorg.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: alan@linux.intel.com, gregkh@linuxfoundation.org, jslaby@suse.cz,
grant.likely@secretlab.ca, rob.herring@calxeda.com,
devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH] serial: tegra: add serial driver
Date: Mon, 17 Dec 2012 14:55:21 -0700 [thread overview]
Message-ID: <50CF94C9.2050907@wwwdotorg.org> (raw)
In-Reply-To: <1355746249-15347-1-git-send-email-ldewangan@nvidia.com>
On 12/17/2012 05:10 AM, Laxman Dewangan wrote:
> Nvidia's Tegra has multiple uart controller which supports:
> - APB dma based controller fifo read/write.
> - End Of Data interrupt in incoming data to know whether end
> of frame achieve or not.
> - Hw controlled RTS and CTS flow control to reduce SW overhead.
>
> Add serial driver to use all above feature.
> diff --git a/Documentation/devicetree/bindings/serial/nvidia,serial-tegra.txt b/Documentation/devicetree/bindings/serial/nvidia,serial-tegra.txt
> +Required properties:
> +- compatible : should be "nvidia,tegra20-hsuart", "nvidia,tegra30-hsuart".
I think you want ", or" not just "," there. If both are specified,
"tegra30" should come before "tegra20", so you might want to re-order
that. That said, other bindings say something like
"nvidia,tegra<chip>-hsuart" so avoid having to spell out all the
supported Tegra versions.
> diff --git a/drivers/tty/serial/serial_tegra.c b/drivers/tty/serial/serial_tegra.c
> +struct tegra_uart_chip_data tegra20_uart_chip_data = {
> + .tx_fifo_full_status = false,
> + .allow_txfifo_reset_fifo_mode = true,
> + .support_clk_src_div = false,
> +};
> +
> +struct tegra_uart_chip_data tegra30_uart_chip_data = {
> + .tx_fifo_full_status = true,
> + .allow_txfifo_reset_fifo_mode = false,
> + .support_clk_src_div = true,
> +};
Nit: Perhaps it'd be nice to move those right before
tegra_uart_of_match[] - i.e. right where they're used.
> +static struct tegra_uart_platform_data *tegra_uart_parse_dt(
> + if (of_get_property(np, "nvidia,enable-modem-interrupt", NULL))
> + pdata->enable_modem_interrupt = 1;
That should use of_property_read_bool().
> +static int __devinit tegra_uart_probe(struct platform_device *pdev)
> + if (pdev->dev.of_node) {
That will always be true these days.
I didn't review the body of the UART implementation since I'm not
familiar with drivers/tty/serial nor too much about our UART HW beyond
basic 8250 usage.
prev parent reply other threads:[~2012-12-17 21:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 12:10 [PATCH] serial: tegra: add serial driver Laxman Dewangan
2012-12-17 12:10 ` Laxman Dewangan
2012-12-17 15:13 ` Greg KH
2012-12-17 15:24 ` Rob Herring
2012-12-17 21:30 ` Stephen Warren
2012-12-17 17:10 ` Grant Likely
2012-12-17 17:10 ` Grant Likely
2012-12-17 21:31 ` Stephen Warren
2012-12-19 13:01 ` Grant Likely
2012-12-19 14:15 ` Laxman Dewangan
[not found] ` <50D1CC07.6070506-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-12-19 16:58 ` Stephen Warren
2012-12-19 16:58 ` Stephen Warren
2012-12-20 1:09 ` Grant Likely
2012-12-17 18:23 ` Alan Cox
2012-12-17 18:23 ` Alan Cox
[not found] ` <1355746249-15347-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-12-17 21:36 ` Stephen Warren
2012-12-17 21:36 ` Stephen Warren
[not found] ` <50CF9043.8030308-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-12-17 21:58 ` Mitch Bradley
2012-12-17 21:58 ` Mitch Bradley
[not found] ` <50CF9580.4050300-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
2012-12-17 22:04 ` Stephen Warren
2012-12-17 22:04 ` Stephen Warren
[not found] ` <50CF96D4.6010705-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-12-17 22:17 ` Mitch Bradley
2012-12-17 22:17 ` Mitch Bradley
2012-12-19 13:03 ` Grant Likely
2012-12-17 21:55 ` Stephen Warren [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=50CF94C9.2050907@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=alan@linux.intel.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=ldewangan@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rob.herring@calxeda.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.