From: cw00.choi@samsung•com (Chanwoo Choi)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v4 2/8] arm64: dts: exynos: Add dts files for 64-bit Exynos5433 SoC
Date: Tue, 24 Feb 2015 20:04:17 +0900 [thread overview]
Message-ID: <54EC5AB1.5090802@samsung.com> (raw)
In-Reply-To: <7412525.l6YnQcTxtg@wuerfel>
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 at localhost:~# ls /dev/ttySAC
ttySAC1 ttySAC3
Thanks,
Chanwoo Choi
next prev parent reply other threads:[~2015-02-24 11:04 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 5:16 [PATCH v4 0/8] arm64: Add the support for new Exynos5433 SoC Chanwoo Choi
2015-02-24 5:16 ` [PATCH v4 1/8] arm64: exynos5433: Enable ARMv8 based Exynos5433 (SoC) support Chanwoo Choi
2015-02-24 8:31 ` Arnd Bergmann
2015-02-26 8:28 ` Chanwoo Choi
2015-02-28 0:51 ` Chanwoo Choi
2015-02-24 5:16 ` [PATCH v4 2/8] arm64: dts: exynos: Add dts files for 64-bit Exynos5433 SoC Chanwoo Choi
2015-02-24 8:33 ` Arnd Bergmann
2015-02-24 9:01 ` Chanwoo Choi
2015-02-24 9:50 ` Arnd Bergmann
2015-02-24 12:15 ` Chanwoo Choi
2015-02-24 8:35 ` Arnd Bergmann
2015-02-24 8:52 ` Chanwoo Choi
2015-02-24 9:48 ` Arnd Bergmann
2015-02-24 11:04 ` Chanwoo Choi [this message]
2015-02-24 11:59 ` Arnd Bergmann
2015-02-26 8:18 ` Chanwoo Choi
2015-02-26 8:42 ` Chanwoo Choi
2015-02-26 15:42 ` Arnd Bergmann
2015-02-28 0:47 ` Chanwoo Choi
2015-03-01 21:22 ` Arnd Bergmann
2015-03-04 6:59 ` Chanwoo Choi
2015-03-04 9:38 ` Arnd Bergmann
2015-03-04 10:11 ` Chanwoo Choi
2015-02-24 5:16 ` [PATCH v4 3/8] arm64: dts: exynos: Add MSHC dt node for Exynos5433 Chanwoo Choi
2015-02-24 5:16 ` [PATCH v4 4/8] arm64: dts: exynos: Add SPI/PDMA " Chanwoo Choi
2015-02-24 5:16 ` [PATCH v4 5/8] arm64: dts: exynos: Add PMU " Chanwoo Choi
2015-02-24 5:16 ` [PATCH v4 6/8] arm64: dts: exynos: Add RTC and ADC dt node for Exynos5433 SoC Chanwoo Choi
2015-02-24 5:16 ` [PATCH v4 7/8] arm64: dts: exynos: Add ADMA " Chanwoo Choi
2015-02-24 5:16 ` [PATCH v4 8/8] arm64: dts: exynos: Add I2S " Chanwoo Choi
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=54EC5AB1.5090802@samsung.com \
--to=cw00.choi@samsung$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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