From: Laxman Dewangan <ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: "linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org"
<linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] ARM: tegra: dts: add aliases and DMA requestor for serial controller
Date: Fri, 21 Dec 2012 09:48:40 +0530 [thread overview]
Message-ID: <50D3E320.2090804@nvidia.com> (raw)
In-Reply-To: <50D344E9.70305-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
On Thursday 20 December 2012 10:33 PM, Stephen Warren wrote:
> On 12/19/2012 11:15 PM, Laxman Dewangan wrote:
>> On Wednesday 19 December 2012 10:30 PM, Stephen Warren wrote:
>>> On 12/18/2012 11:31 PM, Laxman Dewangan wrote:
>>>> Add APB DMA requestor and serial aliases for serial controller.
>>>> There will be two serial driver i.e. 8250 based simple serial driver
>>>> and APB DMA based serial driver for higher baudrate and performace.
>>>>
>>>> The simple serial driver get enabled with compatible nvidia,tegra20-uart
>>>> and APB DMA based driver will get enabled with compatible
>>>> nvidia,tegra20-hsuart.
>>> This patch seems to do two things:
>>>
>>> 1) Add a comment describing how to select the basic or DMA-based driver.
>>> I can see why this is useful.
>>>
>>> 2) Add aliases for the serial ports. I have no idea why this is useful.
>> Serial aliases are added because we want to get the port number like
>> /dev/ttyTHS0, /d/ttyTHS2 etc. The uarta should be /dev/ttyTHS0 and
>> uartc should be /dev/ttyTHS2. The port number can be found using aliases
>> and of_alias_get_id() in driver file:
>>
>> port_number = of_alias_get_id(np, "serial");
> Oh, I see. I guess the aliases make sense then.
>
> But, wouldn't you only add aliases for the specific UARTs that are in
> use on a particular board (so put them in tegraNN-board.dts) rather than
> all UARTs on Tegra (i.e. the current patch which puts them into
> tegraNN.dtsi)?
I like to have this in tegraN N.dtsi file becasue:
- This policy is not going to change the board to board. For high speed
driver the uarta will be ttyTHS0 and uartb ttyTHS1.
- In board file I will only enable driver and make compatible, not worry
about the making aliases.
This approach will simplify the instantiation. This will also avoid
confusion like the aliases get added or not when we create board dts file.
This will be on same line we have with board files where pdev->id is
fixed for all board in common place i.e. device.c which decide the
port-number.
next prev parent reply other threads:[~2012-12-21 4:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 6:31 [PATCH] ARM: tegra: dts: add aliases and DMA requestor for serial controller Laxman Dewangan
[not found] ` <1355898671-3960-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-12-19 17:00 ` Stephen Warren
[not found] ` <50D1F2CB.3090206-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-12-20 6:15 ` Laxman Dewangan
[not found] ` <50D2AD02.6060101-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-12-20 17:03 ` Stephen Warren
[not found] ` <50D344E9.70305-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-12-21 4:18 ` Laxman Dewangan [this message]
[not found] ` <50D3E320.2090804-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-12-21 20:50 ` Stephen Warren
[not found] ` <50D4CBB0.7080603-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-12-22 20:15 ` Laxman Dewangan
[not found] ` <50D614D9.8020106-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-12-25 5:33 ` Stephen Warren
[not found] ` <50D93AB6.7040905-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-12-25 9:43 ` Laxman Dewangan
2012-12-22 20:15 ` Laxman Dewangan
2013-01-02 19:19 ` 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=50D3E320.2090804@nvidia.com \
--to=ldewangan-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.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).