From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: Andrew Davis <afd@ti.com>, Apurva Nandan <a-nandan@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
Hari Nagalla <hnagalla@ti.com>
Subject: Re: [PATCH v3 4/4] arm64: dts: ti: Add support for J784S4 EVM board
Date: Tue, 22 Nov 2022 09:35:10 +0200 [thread overview]
Message-ID: <Y3x7rpx7ypaRzeHB@atomide.com> (raw)
In-Reply-To: <20221118221534.52rfyf5gsck3xrrb@sauciness>
* Nishanth Menon <nm@ti.com> [221118 22:12]:
> I don't buy the argument here for 1-1 mapping of aliased serial
> instances to instances - why should main_uart8 be ttyS10, why not
> ttyS8 (it is equally valid - why was it called uart8?).. That mapping
> is just a convention we are choosing to create.
Heh yeah IMO uart8 should be ttyS8.. I agree let's not break the userspace
device names as we've seen what kind of nightmare that ends up being.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: Andrew Davis <afd@ti.com>, Apurva Nandan <a-nandan@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
Hari Nagalla <hnagalla@ti.com>
Subject: Re: [PATCH v3 4/4] arm64: dts: ti: Add support for J784S4 EVM board
Date: Tue, 22 Nov 2022 09:35:10 +0200 [thread overview]
Message-ID: <Y3x7rpx7ypaRzeHB@atomide.com> (raw)
In-Reply-To: <20221118221534.52rfyf5gsck3xrrb@sauciness>
* Nishanth Menon <nm@ti.com> [221118 22:12]:
> I don't buy the argument here for 1-1 mapping of aliased serial
> instances to instances - why should main_uart8 be ttyS10, why not
> ttyS8 (it is equally valid - why was it called uart8?).. That mapping
> is just a convention we are choosing to create.
Heh yeah IMO uart8 should be ttyS8.. I agree let's not break the userspace
device names as we've seen what kind of nightmare that ends up being.
Regards,
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-11-22 7:35 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 13:04 [PATCH v3 0/4] Add initial support for J784S4 SoC Apurva Nandan
2022-11-16 13:04 ` Apurva Nandan
2022-11-16 13:04 ` [PATCH v3 1/4] dt-bindings: arm: ti: Add bindings for J784s4 SoC Apurva Nandan
2022-11-16 13:04 ` Apurva Nandan
2022-11-16 13:04 ` [PATCH v3 2/4] dt-bindings: pinctrl: k3: Introduce pinmux definitions for J784s4 Apurva Nandan
2022-11-16 13:04 ` Apurva Nandan
2022-11-16 13:04 ` [PATCH v3 3/4] arm64: dts: ti: Add initial support for J784S4 SoC Apurva Nandan
2022-11-16 13:04 ` Apurva Nandan
2022-11-18 17:32 ` Andrew Davis
2022-11-18 17:32 ` Andrew Davis
2022-11-18 17:45 ` Nishanth Menon
2022-11-18 17:45 ` Nishanth Menon
2022-11-18 19:41 ` Apurva Nandan
2022-11-18 19:41 ` Apurva Nandan
2022-11-16 13:04 ` [PATCH v3 4/4] arm64: dts: ti: Add support for J784S4 EVM board Apurva Nandan
2022-11-16 13:04 ` Apurva Nandan
2022-11-18 13:46 ` Manorit Chawdhry
2022-11-18 13:46 ` Manorit Chawdhry
2022-11-18 17:40 ` Andrew Davis
2022-11-18 17:40 ` Andrew Davis
2022-11-18 17:47 ` Nishanth Menon
2022-11-18 17:47 ` Nishanth Menon
2022-11-18 17:56 ` Andrew Davis
2022-11-18 17:56 ` Andrew Davis
2022-11-18 18:08 ` Nishanth Menon
2022-11-18 18:08 ` Nishanth Menon
2022-11-18 18:15 ` Andrew Davis
2022-11-18 18:15 ` Andrew Davis
2022-11-18 19:27 ` Nishanth Menon
2022-11-18 19:27 ` Nishanth Menon
2022-11-18 21:08 ` Andrew Davis
2022-11-18 21:08 ` Andrew Davis
2022-11-18 22:15 ` Nishanth Menon
2022-11-18 22:15 ` Nishanth Menon
2022-11-22 7:35 ` Tony Lindgren [this message]
2022-11-22 7:35 ` Tony Lindgren
2022-12-22 17:55 ` Apurva Nandan
2022-12-22 17:55 ` Apurva Nandan
2022-11-22 7:51 ` Tony Lindgren
2022-11-22 7:51 ` Tony Lindgren
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=Y3x7rpx7ypaRzeHB@atomide.com \
--to=tony@atomide.com \
--cc=a-nandan@ti.com \
--cc=afd@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=hnagalla@ti.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.com \
/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 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.