From: Valentin CARON - foss <valentin.caron@foss.st.com>
To: Rob Herring <robh@kernel.org>
Cc: Alexandre TORGUE - foss <alexandre.torgue@foss.st.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Erwan LE-RAY - foss <erwan.leray@foss.st.com>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-stm32@st-md-mailman.stormreply.com"
<linux-stm32@st-md-mailman.stormreply.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: serial: stm32: add examples
Date: Wed, 10 Mar 2021 08:41:43 +0000 [thread overview]
Message-ID: <60c2caa0-4b69-4460-63b4-6debf1065c42@foss.st.com> (raw)
In-Reply-To: <20210305185347.GA466473@robh.at.kernel.org>
On 3/5/21 7:53 PM, Rob Herring wrote:
> On Tue, Feb 09, 2021 at 10:59:48AM +0100, Valentin Caron wrote:
>> From: Valentin Caron <valentin.caron@st.com>
>>
>> Add examples to show more use cases :
>> - uart2 with hardware flow control
>> - uart4 without flow control
> Why do I need these? I can go read your dts files if I need more
> examples.
Hi,
These examples were present in the dt-binding before the convertion to
json :
https://patchwork.kernel.org/project/linux-arm-kernel/patch/20200122095558.22553-3-benjamin.gaignard@st.com/
Would you like a v2 with this precision ?
However this is not an essential patch, we can just drop it.
>
>> Signed-off-by: Valentin Caron <valentin.caron@foss.st.com>
>> ---
>> .../bindings/serial/st,stm32-uart.yaml | 20 +++++++++++++++++++
>> 1 file changed, 20 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/serial/st,stm32-uart.yaml b/Documentation/devicetree/bindings/serial/st,stm32-uart.yaml
>> index 06d5f251ec88..3a4aab5d1862 100644
>> --- a/Documentation/devicetree/bindings/serial/st,stm32-uart.yaml
>> +++ b/Documentation/devicetree/bindings/serial/st,stm32-uart.yaml
>> @@ -82,6 +82,26 @@ additionalProperties: false
>> examples:
>> - |
>> #include <dt-bindings/clock/stm32mp1-clks.h>
>> +
>> + usart4: serial@40004c00 {
>> + compatible = "st,stm32-uart";
>> + reg = <0x40004c00 0x400>;
>> + interrupts = <52>;
>> + clocks = <&clk_pclk1>;
>> + pinctrl-names = "default";
>> + pinctrl-0 = <&pinctrl_usart4>;
>> + };
>> +
>> + usart2: serial@40004400 {
>> + compatible = "st,stm32-uart";
>> + reg = <0x40004400 0x400>;
>> + interrupts = <38>;
>> + clocks = <&clk_pclk1>;
>> + st,hw-flow-ctrl;
>> + pinctrl-names = "default";
>> + pinctrl-0 = <&pinctrl_usart2 &pinctrl_usart2_rtscts>;
>> + };
>> +
>> usart1: serial@40011000 {
>> compatible = "st,stm32-uart";
>> reg = <0x40011000 0x400>;
>> --
>> 2.17.1
>>
prev parent reply other threads:[~2021-03-10 8:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 9:59 [PATCH] dt-bindings: serial: stm32: add examples Valentin Caron
2021-03-05 18:53 ` Rob Herring
2021-03-10 8:41 ` Valentin CARON - foss [this message]
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=60c2caa0-4b69-4460-63b4-6debf1065c42@foss.st.com \
--to=valentin.caron@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=devicetree@vger.kernel.org \
--cc=erwan.leray@foss.st.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh@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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).