From: Stephen Warren <swarren@wwwdotorg.org>
To: Rob Herring <robherring2@gmail.com>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
alan@linux.intel.com, gregkh@linuxfoundation.org, jslaby@suse.cz,
grant.likely@secretlab.ca, 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:30:00 -0700 [thread overview]
Message-ID: <50CF8ED8.2030602@wwwdotorg.org> (raw)
In-Reply-To: <50CF393F.4040009@gmail.com>
On 12/17/2012 08:24 AM, Rob Herring wrote:
> On 12/17/2012 06: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.
>>
>> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
>> ---
>> .../bindings/serial/nvidia,serial-tegra.txt | 26 +
>
> Can we have a name without a comma. If serial-tegra is specific enough
> for the kernel, then it is for the binding doc too.
I would vastly prefer that the binding doc filenames use the compatible
value exactly. All (or as many as possible) of the other Tegra bindings
do this, and I think it's good style.
>> diff --git a/Documentation/devicetree/bindings/serial/nvidia,serial-tegra.txt b/Documentation/devicetree/bindings/serial/nvidia,serial-tegra.txt
>> +- nvidia,dma-request-selector : The Tegra DMA controller's phandle and
>> + request selector for this UART controller.
>
> This should use the generic DMA binding although I'm not sure if that
> made it into 3.8.
It didn't as far as I can tell, even though I think someone said it
should... Will it make 3.9? As a general rule, I'd like to move forward
on drivers and then refactor this aspect once the generic API/binding is
finalized and implemented.
(I couldn't find any more comments of yours below, but since the whole
patch was quoted, it was difficult to tell)
next prev parent reply other threads:[~2012-12-17 21:30 UTC|newest]
Thread overview: 17+ 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 15:13 ` Greg KH
2012-12-17 15:24 ` Rob Herring
2012-12-17 21:30 ` Stephen Warren [this message]
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-20 1:09 ` Grant Likely
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
[not found] ` <50CF9043.8030308-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-12-17 21:58 ` Mitch Bradley
[not found] ` <50CF9580.4050300-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
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-19 13:03 ` Grant Likely
2012-12-17 21:55 ` Stephen Warren
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=50CF8ED8.2030602@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=robherring2@gmail.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).