From: Wadim Egorov <w.egorov@phytec.de>
To: Bryan Brattlof <bb@ti.com>, Nishanth Menon <nm@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] arm64: dts: ti: introduce a minimal am642 device tree
Date: Wed, 30 Mar 2022 15:55:45 +0200 [thread overview]
Message-ID: <73a4a16b-193a-3075-61e9-82bcf21fc7d2@phytec.de> (raw)
In-Reply-To: <20220321155417.13267-1-bb@ti.com>
Hi Bryan,
> +/* (optional) for console */
> +&main_uart0 {
> + pinctrl-names = "default";
> + pinctrl-0 = <&main_uart0_pins_default>;
> +};
> +
> +/* reserved for firmware */
> +&main_uart1 {
> + status = "reserved";
> +};
k3-image-gen says UART0 is used as a debug interface. See
https://git.ti.com/cgit/k3-image-gen/k3-image-gen/tree/soc/am64x/evm/board-cfg.c#n81
So it seems that you can enable uart1 here. But people may run into a
conflict with uart0 and k3-image-gen compiled with ENABLE_TRACE=1.
If I am wrong, can you please clarify why you mark uart1 as reserved.
Regards,
Wadim
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Wadim Egorov <w.egorov@phytec.de>
To: Bryan Brattlof <bb@ti.com>, Nishanth Menon <nm@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] arm64: dts: ti: introduce a minimal am642 device tree
Date: Wed, 30 Mar 2022 15:55:45 +0200 [thread overview]
Message-ID: <73a4a16b-193a-3075-61e9-82bcf21fc7d2@phytec.de> (raw)
In-Reply-To: <20220321155417.13267-1-bb@ti.com>
Hi Bryan,
> +/* (optional) for console */
> +&main_uart0 {
> + pinctrl-names = "default";
> + pinctrl-0 = <&main_uart0_pins_default>;
> +};
> +
> +/* reserved for firmware */
> +&main_uart1 {
> + status = "reserved";
> +};
k3-image-gen says UART0 is used as a debug interface. See
https://git.ti.com/cgit/k3-image-gen/k3-image-gen/tree/soc/am64x/evm/board-cfg.c#n81
So it seems that you can enable uart1 here. But people may run into a
conflict with uart0 and k3-image-gen compiled with ENABLE_TRACE=1.
If I am wrong, can you please clarify why you mark uart1 as reserved.
Regards,
Wadim
next prev parent reply other threads:[~2022-03-30 13:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 15:54 [RFC] arm64: dts: ti: introduce a minimal am642 device tree Bryan Brattlof
2022-03-21 15:54 ` Bryan Brattlof
2022-03-22 18:14 ` Krzysztof Kozlowski
2022-03-22 18:14 ` Krzysztof Kozlowski
2024-07-09 16:20 ` Logan Bristol
2024-07-10 6:52 ` Krzysztof Kozlowski
2024-07-15 14:12 ` Logan Bristol
2024-07-10 7:38 ` Francesco Dolcini
2024-07-15 14:02 ` Logan Bristol
2024-07-15 14:55 ` Francesco Dolcini
2022-03-30 13:55 ` Wadim Egorov [this message]
2022-03-30 13:55 ` Wadim Egorov
2022-03-31 6:58 ` Vignesh Raghavendra
2022-03-31 6:58 ` Vignesh Raghavendra
2022-03-31 7:19 ` Wadim Egorov
2022-03-31 7:19 ` Wadim Egorov
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=73a4a16b-193a-3075-61e9-82bcf21fc7d2@phytec.de \
--to=w.egorov@phytec.de \
--cc=bb@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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.