From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932276AbbBZISt (ORCPT ); Thu, 26 Feb 2015 03:18:49 -0500 Received: from mailout2.samsung.com ([203.254.224.25]:52445 "EHLO mailout2.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751340AbbBZISp (ORCPT ); Thu, 26 Feb 2015 03:18:45 -0500 X-AuditID: cbfee690-f79ab6d0000046f7-7a-54eed6e202fc Message-id: <54EED6E1.4060908@samsung.com> Date: Thu, 26 Feb 2015 17:18:41 +0900 From: Chanwoo Choi User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-version: 1.0 To: Arnd Bergmann Cc: linux-arm-kernel@lists.infradead.org, mark.rutland@arm.com, jh80.chung@samsung.com, linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org, marc.zyngier@arm.com, catalin.marinas@arm.com, will.deacon@arm.com, linux-kernel@vger.kernel.org, a.kesavan@samsung.com, inki.dae@samsung.com, sw0312.kim@samsung.com, kgene@kernel.org, olof@lixom.net, chanho61.park@samsung.com, ideal.song@samsung.com, =?UTF-8?B?7LWc7LCs7Jqw?= Subject: Re: [PATCH v4 2/8] arm64: dts: exynos: Add dts files for 64-bit Exynos5433 SoC References: <1424755011-15999-1-git-send-email-cw00.choi@samsung.com> <7412525.l6YnQcTxtg@wuerfel> <54EC5AB1.5090802@samsung.com> <6850624.bdB2Ab6zJx@wuerfel> In-reply-to: <6850624.bdB2Ab6zJx@wuerfel> Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrEIsWRmVeSWpSXmKPExsWyRsSkUPfRtXchBg9PKFo8XrOYyeLvpGPs Fu+X9TBaXN6vbXH9y3NWi/lHzrFa7Pp7n9Fi0v0JLBY3frWxWvQ/fs1ssenxNVaLy7vmsFnM OL8PqPXOPzaLpdcvMlmcuv4ZKDb5JZvFy48nWByEPNbMW8Po8fvXJEaPTas62Tw2L6n3uHKi idWjb8sqRo/Pm+QC2KO4bFJSczLLUov07RK4Mo7fW8RU8Ei+4s9/5wbGWxJdjJwcEgImEidP 7maEsMUkLtxbzwZiCwksZZSYtFQVpmZmz22mLkYuoPgiRomPxw9COa8ZJfof9YJ18ApoSby/ fw3I5uBgEVCVOLGnCiTMBhTe/+IGWImoQJjEyulXWCDKBSV+TL4HZosIKEpMffGMGWQms8B5 ZomOLQeYQRLCApESD382s8FtXr2kAayDU0BTYvWk92A2s4C6xKR5i5ghbHmJzWvegk2SEFjI IbHwEEQRi4CAxLfJh1hArpMQkJXYBLFAQkBS4uCKGywTGMVmITlqFpKxs5CMXcDIvIpRNLUg uaA4Kb3IRK84Mbe4NC9dLzk/dxMjMOpP/3s2YQfjvQPWhxgFOBiVeHgTst+FCLEmlhVX5h5i NAW6YiKzlGhyPjC15JXEGxqbGVmYmpgaG5lbmimJ876W+hksJJCeWJKanZpakFoUX1Sak1p8 iJGJg1OqgTFlhQrLvfOnb+md43DqatJPZavyd89ONJvmefncl5jrxw55WW6Uurh69mubuwdY 7q989OB5ZgTv6eWOxya0HHawvPXuoHvrotzZUatU3lVO7ud6+XVTpsqUc5c4OIvF2p0FmCv+ lnaZp7M9stvh+re03Gbp8ZJSTduHivz5H03EMs9GOCkn2yqxFGckGmoxFxUnAgAGZUC09QIA AA== X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrLKsWRmVeSWpSXmKPExsVy+t9jAd1H196FGHT+ErN4vGYxk8XfScfY Ld4v62G0uLxf2+L6l+esFvOPnGO12PX3PqPFpPsTWCxu/Gpjteh//JrZYtPja6wWl3fNYbOY cX4fUOudf2wWS69fZLI4df0zUGzySzaLlx9PsDgIeayZt4bR4/evSYwem1Z1snlsXlLvceVE E6tH35ZVjB6fN8kFsEc1MNpkpCampBYppOYl56dk5qXbKnkHxzvHm5oZGOoaWlqYKynkJeam 2iq5+AToumXmAL2hpFCWmFMKFApILC5W0rfDNCE0xE3XAqYxQtc3JAiux8gADSSsYcw4fm8R U8Ej+Yo//50bGG9JdDFyckgImEjM7LnNBGGLSVy4t56ti5GLQ0hgEaPEx+MHmSCc14wS/Y96 2UCqeAW0JN7fvwZkc3CwCKhKnNhTBRJmAwrvf3EDrERUIExi5fQrLBDlghI/Jt8Ds0UEFCWm vnjGDDKTWeA8s0THlgPMIAlhgUiJhz+bETavXtIA1sEpoCmxetJ7MJtZQF1i0rxFzBC2vMTm NW+ZJzAKzEKyZBaSsllIyhYwMq9iFE0tSC4oTkrPNdIrTswtLs1L10vOz93ECE4qz6R3MK5q sDjEKMDBqMTDm5D9LkSINbGsuDL3EKMEB7OSCO/ZY0Ah3pTEyqrUovz4otKc1OJDjKbAIJjI LCWanA9MeHkl8YbGJmZGlkbmhhZGxuZK4rxK9m0hQgLpiSWp2ampBalFMH1MHJxSDYxFWlv0 Lm9m2Rigv/iD+tt037zUNcGep3TnXb6bfSHuxpnoGpV5R1oWSpnsvJXksG3mxz0ft/6ccPf+ Wz7B96+2L7bdLrJb9/2b9yw/+U7Z33NVL3/mN/ui68Rli1r6V7IpvTZYZvzf4dMPC4v/h8Ln pr0V3DFVTSMzNFheKyhown6ha7IHzy5fqMRSnJFoqMVcVJwIAI9sfKxAAwAA DLP-Filter: Pass X-MTR: 20000000000000000@CPGS X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/24/2015 08:59 PM, Arnd Bergmann wrote: > On Tuesday 24 February 2015 20:04:17 Chanwoo Choi wrote: >> 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@localhost:~# ls /dev/ttySAC >> ttySAC1 ttySAC3 >> > > I'm not completely following. So you have set the serial1 alias to > the &serial_0 device node and serial3 to &serial_3? > > Why not use serial0=&serial_0 and serial1=&serial_3? Does the serial0 > alias have a special meaning? I add following aliases and serial_1/serial_3 dt node in board dtsi: I tested that change the alias of serial_x node. aliases { serial0 = &serial_1; serial1 = &serial_3; }; /* Add 'linux,stdout-path' property to print kernel log by using ealycon */ chosen { linux,stdout-path = &serial_1; }; [snip] /* serial_1 is used for printing kernel log throught JIG cable */ &serial_1 { status = "okay"; }; &serial_3 { status = "okay"; }; In result, serial driver create the /dev/ttySAC0 for serial_1 and /dev/ttySAC1 for serial_3. But, I cannot complete the kernel booting and stop it with following kernel log [ 0.000000] Booting Linux on physical CPU 0x100 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 4.0.0-rc1-00066-g49bfcec-dirty (cwchoi00@chan) (gcc version 4.9.2 20140904 (prerelease) (crosstool-NG l5 [snip] [ 0.000000] Kernel command line: console=ttySAC1,115200 earlycon=exynos4210,0x14C20000 [snip] [ 0.651647] dma-pl330 15610000.pdma: Loaded driver for PL330 DMAC-341330 [ 0.651851] dma-pl330 15610000.pdma: DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32 [ 0.658566] dma-pl330 15600000.pdma: Loaded driver for PL330 DMAC-341330 [ 0.662872] dma-pl330 15600000.pdma: DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32 [ 0.672487] dma-pl330 11420000.adma: Loaded driver for PL330 DMAC-341330 [ 8466.414900] dma-pl330 11420000.adma: DBUFF-8x8bytes Num_Chans-8 Num_Peri-16 Num_Events-8 [ 8466.481648] 14c20000.serial: ttySAC0 at MMIO 0x14c20000 (irq = 21, base_baud = 0) is a S3C6400/10 (dont' print any kernel log) So, I change the kernel command line about ('console' bootparam) as following: because tty framework must use the 'console' bootparam to print kernel log. - original : Kernel command line: console=ttySAC1,115200 ... (cannot the kernel log from serial driver probed) - modification : Kernel command line: console=ttySAC0,115200 ... (got the successful kernel booting) After modification, I got the successful kernel booting. If should use the serial_0 device and then modify the 'aliases' as following: I have to modify the commandline of bootloader if the commandline of bootloader is used instad of default kernel command line. aliases { serial0 = &serial_0; serial1 = &serial_1; serial2 = &serial_3; }; Thanks, Chanwoo Choi