From: Paul Walmsley <paul.walmsley@sifive.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"open list:SERIAL DRIVERS" <linux-serial@vger.kernel.org>,
linux-riscv@lists.infradead.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Paul Walmsley <paul@pwsan.com>,
devicetree@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>,
Palmer Dabbelt <palmer@sifive.com>
Subject: Re: [PATCH v5 1/2] dt-bindings: serial: add documentation for the SiFive UART driver
Date: Fri, 26 Apr 2019 09:36:34 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1904260931310.28496@viisi.sifive.com> (raw)
In-Reply-To: <CAL_JsqLMFmkM3YHS3BK9LBdidmqRMZn0w+_WUGg7zZvyv3g=sw@mail.gmail.com>
On Fri, 26 Apr 2019, Rob Herring wrote:
> On Fri, Apr 12, 2019 at 9:01 PM Paul Walmsley <paul.walmsley@sifive.com> wrote:
> >
> > Add DT binding documentation for the Linux driver for the SiFive
> > asynchronous serial IP block.
> >
> > This revision incorporates changes based on feedback from Rob
> > Herring <robh@kernel.org>.
> >
> > Signed-off-by: Paul Walmsley <paul.walmsley@sifive.com>
> > Signed-off-by: Paul Walmsley <paul@pwsan.com>
> > Cc: linux-serial@vger.kernel.org
> > Cc: devicetree@vger.kernel.org
> > Cc: linux-riscv@lists.infradead.org
> > Cc: linux-kernel@vger.kernel.org
> > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Cc: Rob Herring <robh+dt@kernel.org>
> > Cc: Mark Rutland <mark.rutland@arm.com>
> > Cc: Palmer Dabbelt <palmer@sifive.com>
> > ---
> > .../bindings/serial/sifive-serial.txt | 33 +++++++++++++++++++
> > 1 file changed, 33 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/serial/sifive-serial.txt
>
> Reviewed-by: Rob Herring <robh@kernel.org>
Thanks Rob.
> However, what about flow-control configuration? You'd better think now
> about what the default is and overriding that.
The underlying IP doesn't support it.
https://github.com/sifive/riscv-linux/blob/dev/paulw/dts-v5.1-rc6-experimental/drivers/tty/serial/sifive.c#L30
- Paul
next prev parent reply other threads:[~2019-04-26 16:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-13 2:01 [PATCH v5 0/2] tty: serial: add DT bindings and serial driver for the SiFive FU540 UART Paul Walmsley
2019-04-13 2:01 ` [PATCH v5 1/2] dt-bindings: serial: add documentation for the SiFive UART driver Paul Walmsley
2019-04-26 14:08 ` Rob Herring
2019-04-26 16:36 ` Paul Walmsley [this message]
2019-04-13 2:01 ` [PATCH v5 2/2] tty: serial: add driver for the SiFive UART Paul Walmsley
2019-05-02 18:58 ` Kevin Hilman
2019-04-18 23:22 ` [PATCH v5 0/2] tty: serial: add DT bindings and serial driver for the SiFive FU540 UART Kevin Hilman
2019-04-19 1:04 ` Atish Patra
2019-04-19 19:18 ` Kevin Hilman
2019-04-19 19:29 ` Atish Patra
2019-04-19 20:34 ` Kevin Hilman
2019-04-19 21:13 ` Paul Walmsley
2019-05-02 18:57 ` Kevin Hilman
2019-05-03 19:05 ` Paul Walmsley
2019-04-24 18:58 ` Paul Walmsley
2019-05-27 16:12 ` Loys Ollivier
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=alpine.DEB.2.21.9999.1904260931310.28496@viisi.sifive.com \
--to=paul.walmsley@sifive.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=palmer@sifive.com \
--cc=paul@pwsan.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).