From: Nishanth Menon <nm@ti.com>
To: "Kumar, Udit" <u-kumar1@ti.com>
Cc: Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>, Tero Kristo <kristo@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Nitin Yadav <n-yadav@ti.com>,
Neha Malcom Francis <n-francis@ti.com>,
Sinthu Raja <sinthu.raja@ti.com>
Subject: Re: [PATCH 3/6] arm64: dts: ti: k3-am68-sk-base-board: Add uart pinmux
Date: Tue, 6 Jun 2023 06:40:28 -0500 [thread overview]
Message-ID: <20230606114028.croeykqxsf6zvhhh@boxer> (raw)
In-Reply-To: <fb128289-f459-4fe2-0426-6cd6cac93c1a@ti.com>
On 15:23-20230606, Kumar, Udit wrote:
[...]
> Series look good.
Could you confirm by providing a Reviewed-by Tag to the cover-letter?
>
> One small question, We don't have CTS and RTS Pin for mcu uart ,
>
> is this due to board connections ?
yup.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
WARNING: multiple messages have this Message-ID (diff)
From: Nishanth Menon <nm@ti.com>
To: "Kumar, Udit" <u-kumar1@ti.com>
Cc: Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>, Tero Kristo <kristo@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Nitin Yadav <n-yadav@ti.com>,
Neha Malcom Francis <n-francis@ti.com>,
Sinthu Raja <sinthu.raja@ti.com>
Subject: Re: [PATCH 3/6] arm64: dts: ti: k3-am68-sk-base-board: Add uart pinmux
Date: Tue, 6 Jun 2023 06:40:28 -0500 [thread overview]
Message-ID: <20230606114028.croeykqxsf6zvhhh@boxer> (raw)
In-Reply-To: <fb128289-f459-4fe2-0426-6cd6cac93c1a@ti.com>
On 15:23-20230606, Kumar, Udit wrote:
[...]
> Series look good.
Could you confirm by providing a Reviewed-by Tag to the cover-letter?
>
> One small question, We don't have CTS and RTS Pin for mcu uart ,
>
> is this due to board connections ?
yup.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
_______________________________________________
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:[~2023-06-06 11:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 15:35 [PATCH 0/6] arm64: dts: ti: k3-j721s2: Mux fixups and eeprom misc Nishanth Menon
2023-06-02 15:35 ` Nishanth Menon
2023-06-02 15:35 ` [PATCH 1/6] arm64: dts: ti: k3-j721s2: Fix wkup pinmux range Nishanth Menon
2023-06-02 15:35 ` Nishanth Menon
2023-06-02 15:35 ` [PATCH 2/6] arm64: dts: ti: k3-am68-sk-base-board: Add pinmux for RPi Header Nishanth Menon
2023-06-02 15:35 ` Nishanth Menon
2023-06-02 15:35 ` [PATCH 3/6] arm64: dts: ti: k3-am68-sk-base-board: Add uart pinmux Nishanth Menon
2023-06-02 15:35 ` Nishanth Menon
2023-06-06 9:53 ` Kumar, Udit
2023-06-06 9:53 ` Kumar, Udit
2023-06-06 11:40 ` Nishanth Menon [this message]
2023-06-06 11:40 ` Nishanth Menon
2023-06-02 15:35 ` [PATCH 4/6] arm64: dts: ti: k3-am68-sk-som: Enable wakeup_i2c0 and eeprom Nishanth Menon
2023-06-02 15:35 ` Nishanth Menon
2023-06-06 6:24 ` Raja, M Sinthu
2023-06-06 6:24 ` Raja, M Sinthu
2023-06-02 15:35 ` [PATCH 5/6] arm64: dts: ti: k3-j721s2-common-proc-board: Add uart pinmux Nishanth Menon
2023-06-02 15:35 ` Nishanth Menon
2023-06-02 15:35 ` [PATCH 6/6] arm64: dts: ti: k3-j721s2-som-p0: Enable wakeup_i2c0 and eeprom Nishanth Menon
2023-06-02 15:35 ` Nishanth Menon
2023-06-06 13:07 ` [PATCH 0/6] arm64: dts: ti: k3-j721s2: Mux fixups and eeprom misc Kumar, Udit
2023-06-06 13:07 ` Kumar, Udit
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=20230606114028.croeykqxsf6zvhhh@boxer \
--to=nm@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=n-francis@ti.com \
--cc=n-yadav@ti.com \
--cc=robh+dt@kernel.org \
--cc=sinthu.raja@ti.com \
--cc=u-kumar1@ti.com \
--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.