From: Manivannan Sadhasivam <mani@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre TORGUE <alexandre.torgue@st.com>,
"open list:SERIAL DRIVERS" <linux-serial@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] Add software flow control support for STM32 UART
Date: Thu, 16 Apr 2020 23:07:10 +0530 [thread overview]
Message-ID: <20200416173710.GA4548@Mani-XPS-13-9360> (raw)
In-Reply-To: <CAHp75VfDUoFMWg42OFHZtKQ972eoR3UDLVAs+BQjJm3h3-fOGw@mail.gmail.com>
Hi Andy,
On Mon, Apr 13, 2020 at 12:17:21PM +0300, Andy Shevchenko wrote:
> On Mon, Apr 13, 2020 at 7:06 AM <mani@kernel.org> wrote:
> >
> > From: Manivannan Sadhasivam <mani@kernel.org>
> >
> > Hello,
> >
> > This patchset adds software flow control support for STM32 UART controller.
> > This is necessary for the upcoming STM32MP1 based board called Stinger96
> > IoT-Box. On that board, a bluetooth chip is connected to one of the UART
> > controller but the CTS/RTS lines got swapped mistakenly. So in order to
> > workaround that hardware bug and also to support the usecase of using only
> > Tx/Rx pins, this patchset adds software flow control support.
> >
> > This patchset has been validated w/ Stinger96 IoT-Box connected to Murata
> > WiFi-BT combo chip.
> >
>
> I think it's a mix of terminology or so. Looking into the patches I
> found that it's required to have GPIOs for SW flow control.
> No, SW flow control does not require any additional signals, except RxD/TxD.
>
Yikes. Yes I got it wrong. 'st,hw-flow-ctrl' property confused me :)
> On top of that, it seems you adding mctrl-gpio functionality. Why
> can't you use that one? And thus no bindings needs to be updated.
>
Sure. This looks feasible. Will submit a follow up patch.
Thanks,
Mani
> > Thanks,
> > Mani
> >
> > Manivannan Sadhasivam (2):
> > dt-bindings: serial: Add binding for software flow control in STM32
> > UART
> > tty: serial: Add software flow control support for STM32 USART
> >
> > .../bindings/serial/st,stm32-uart.yaml | 15 +-
> > drivers/tty/serial/stm32-usart.c | 143 +++++++++++++++++-
> > drivers/tty/serial/stm32-usart.h | 4 +
> > 3 files changed, 155 insertions(+), 7 deletions(-)
> >
> > --
> > 2.17.1
> >
>
>
> --
> With Best Regards,
> Andy Shevchenko
prev parent reply other threads:[~2020-04-16 17:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-12 18:09 [PATCH 0/2] Add software flow control support for STM32 UART mani
2020-04-12 18:09 ` [PATCH 1/2] dt-bindings: serial: Add binding for software flow control in " mani
2020-04-12 18:09 ` [PATCH 2/2] tty: serial: Add software flow control support for STM32 USART mani
2020-04-13 9:17 ` [PATCH 0/2] Add software flow control support for STM32 UART Andy Shevchenko
2020-04-16 17:37 ` Manivannan Sadhasivam [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=20200416173710.GA4548@Mani-XPS-13-9360 \
--to=mani@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--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+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: 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).