From: Geert Uytterhoeven <geert@linux-m68k.org> To: Fabrizio Castro <fabrizio.castro@bp.renesas.com> Cc: Chris Paterson <Chris.Paterson2@renesas.com>, Rob Herring <robh+dt@kernel.org>, Mark Rutland <mark.rutland@arm.com>, Russell King <linux@armlinux.org.uk>, Simon Horman <horms@verge.net.au>, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, Linux-Renesas <linux-renesas-soc@vger.kernel.org>, Biju Das <biju.das@bp.renesas.com> Subject: Re: [PATCH] ARM: dts: iwg20d-q7: Add support for ttySC3 Date: Tue, 7 Nov 2017 12:09:27 +0100 [thread overview] Message-ID: <CAMuHMdXPSUmNiFF7gmkWng5OA_U4DUF+4uohjkjvuMPwgffj-g@mail.gmail.com> (raw) In-Reply-To: <TY1PR06MB0895D27B9C7F2D3B3113654EC0460@TY1PR06MB0895.apcprd06.prod.outlook.com> Hi Fabrizio, On Mon, Oct 23, 2017 at 3:25 PM, Fabrizio Castro <fabrizio.castro@bp.renesas.com> wrote: >> > > --- a/arch/arm/boot/dts/iwg20d-q7-common.dtsi >> > > +++ b/arch/arm/boot/dts/iwg20d-q7-common.dtsi >> > > @@ -11,6 +11,7 @@ >> > > / { >> > > aliases { >> > > serial0 = &scif0; >> > > + serial3 = &scifb1; >> > >> > Given this port is not labeled "serial3", but called "data uart", you may want >> > to add a comment to avoid confusion: >> >> It's a little bit confusing, isn't it? The lines related to such interface are named as UART0_x on the carrier board schematic, the section >> of the schematic that contains the header is named "data uart header", and the board documentation names it explicitly as "UART 3 - >> /dev/ttySC3 (SCIFB1)". And you cannot use "serial0" (to match "UART0"), as that's already in use for the SOM... >> I don't think there is anything we can do to make this easier for the user really, is there? :D >> If we decide to add a comment to serial 3, I guess we need to be consistent and add comments for the other serial interfaces too. >> If you still prefer having a comment there I'll send a v2 and patch(es) for adding comments to the other interfaces, just let me know. > > Any thoughts about this? Making life easier for the user is good. Consistency is also good. I have no strong feelings about this, so do as you please... Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
WARNING: multiple messages have this Message-ID (diff)
From: geert@linux-m68k.org (Geert Uytterhoeven) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH] ARM: dts: iwg20d-q7: Add support for ttySC3 Date: Tue, 7 Nov 2017 12:09:27 +0100 [thread overview] Message-ID: <CAMuHMdXPSUmNiFF7gmkWng5OA_U4DUF+4uohjkjvuMPwgffj-g@mail.gmail.com> (raw) In-Reply-To: <TY1PR06MB0895D27B9C7F2D3B3113654EC0460@TY1PR06MB0895.apcprd06.prod.outlook.com> Hi Fabrizio, On Mon, Oct 23, 2017 at 3:25 PM, Fabrizio Castro <fabrizio.castro@bp.renesas.com> wrote: >> > > --- a/arch/arm/boot/dts/iwg20d-q7-common.dtsi >> > > +++ b/arch/arm/boot/dts/iwg20d-q7-common.dtsi >> > > @@ -11,6 +11,7 @@ >> > > / { >> > > aliases { >> > > serial0 = &scif0; >> > > + serial3 = &scifb1; >> > >> > Given this port is not labeled "serial3", but called "data uart", you may want >> > to add a comment to avoid confusion: >> >> It's a little bit confusing, isn't it? The lines related to such interface are named as UART0_x on the carrier board schematic, the section >> of the schematic that contains the header is named "data uart header", and the board documentation names it explicitly as "UART 3 - >> /dev/ttySC3 (SCIFB1)". And you cannot use "serial0" (to match "UART0"), as that's already in use for the SOM... >> I don't think there is anything we can do to make this easier for the user really, is there? :D >> If we decide to add a comment to serial 3, I guess we need to be consistent and add comments for the other serial interfaces too. >> If you still prefer having a comment there I'll send a v2 and patch(es) for adding comments to the other interfaces, just let me know. > > Any thoughts about this? Making life easier for the user is good. Consistency is also good. I have no strong feelings about this, so do as you please... Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
next prev parent reply other threads:[~2017-11-07 11:09 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-10-09 9:06 [PATCH] ARM: dts: iwg20d-q7: Add support for ttySC3 Fabrizio Castro 2017-10-09 9:06 ` Fabrizio Castro 2017-10-09 12:08 ` Geert Uytterhoeven 2017-10-09 12:08 ` Geert Uytterhoeven [not found] ` <CAMuHMdUprE7QuXF_sX47JyrvuZXhXnQFufy4OHeJ5ExwwoogKw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2017-10-09 13:45 ` Fabrizio Castro 2017-10-09 13:45 ` Fabrizio Castro 2017-10-09 13:45 ` Fabrizio Castro 2017-11-02 8:04 ` Simon Horman 2017-11-02 8:04 ` Simon Horman [not found] ` <20171102080412.n3wfabxt2ayswxzp-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org> 2017-11-02 9:20 ` Fabrizio Castro 2017-11-02 9:20 ` Fabrizio Castro 2017-11-02 9:20 ` Fabrizio Castro 2017-10-23 13:25 ` Fabrizio Castro 2017-10-23 13:25 ` Fabrizio Castro 2017-11-07 11:09 ` Geert Uytterhoeven [this message] 2017-11-07 11:09 ` Geert Uytterhoeven
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=CAMuHMdXPSUmNiFF7gmkWng5OA_U4DUF+4uohjkjvuMPwgffj-g@mail.gmail.com \ --to=geert@linux-m68k.org \ --cc=Chris.Paterson2@renesas.com \ --cc=biju.das@bp.renesas.com \ --cc=devicetree@vger.kernel.org \ --cc=fabrizio.castro@bp.renesas.com \ --cc=horms@verge.net.au \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-renesas-soc@vger.kernel.org \ --cc=linux@armlinux.org.uk \ --cc=mark.rutland@arm.com \ --cc=robh+dt@kernel.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.