[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <54EC5AB1.5090802@samsung.com>
Date: Tue, 24 Feb 2015 20:04:17 +0900
From: Chanwoo Choi <cw00.choi@...sung.com>
To: Arnd Bergmann <arnd@...db.de>
Cc: kgene@...nel.org, mark.rutland@....com, marc.zyngier@....com,
olof@...om.net, catalin.marinas@....com, will.deacon@....com,
inki.dae@...sung.com, chanho61.park@...sung.com,
sw0312.kim@...sung.com, jh80.chung@...sung.com,
ideal.song@...sung.com, a.kesavan@...sung.com,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 2/8] arm64: dts: exynos: Add dts files for 64-bit
Exynos5433 SoC
On 02/24/2015 06:48 PM, Arnd Bergmann wrote:
> On Tuesday 24 February 2015 17:52:01 Chanwoo Choi wrote:
>>
>> But, I have a question.
>> If we put the aliases into the board dts file instaed of SoC dtsi,
>> each board dts file may use the different alias name about same phandle.
>
> Yes, that is the idea. In particular with the uarts, the intention is
> that the numbering of the device nodes in /dev is the same that is
> printed on the board (if any), which may be different from the numbering
> internal to the SoC.
I check the uart device with Exynos5433 SoC based on Linux 4.0-rc1
If some board use the serial_0 and serial_3 as following in board dtsi,
&serial_0 { --> UART 0 device
status = "okay";
};
&serial_3 { --> UART 3 device
status = "okay";
};
The serial core driver create the follwoing /dev/ttySACx device node
by using the number of alias. It maintain the same device number of internel to the SoC.
root@...alhost:~# ls /dev/ttySAC
ttySAC1 ttySAC3
Thanks,
Chanwoo Choi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists