From: "Jakub Kiciński" <moorray3@wp.pl>
To: linux-serial@vger.kernel.org, devicetree@vger.kernel.org
Cc: Cyrille Pitchen <cyrille.pitchen@atmel.com>,
nicolas.ferre@atmel.com, gregkh@linuxfoundation.org,
wenyou.yang@atmel.com, ludovic.desroches@atmel.com,
leilei.zhao@atmel.com, josh.wu@atmel.com,
alexandre.belloni@free-electrons.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, galak@codeaurora.org,
ijc+devicetree@hellion.org.uk, mark.rutland@arm.com,
pawel.moll@arm.com, robh+dt@kernel.org
Subject: Re: [PATCH linux-next 1/4] ARM: at91/dt: add new DT properties for Atmel usart
Date: Thu, 4 Jun 2015 14:34:57 +0200 [thread overview]
Message-ID: <20150604143457.2a0e0acf@north> (raw)
In-Reply-To: <6fe7914a2c39245ac9a05cdb9962b88c409ec1a4.1433253787.git.cyrille.pitchen@atmel.com>
On Tue, 2 Jun 2015 16:18:21 +0200, Cyrille Pitchen wrote:
> +- atmel,rts-low-threshold: when the RX FIFO level, ie the number of data
> + available to be read from the RX FIFO, crosses down this threshold the RTS
> + line is driven to low level to tell the remote peer that it can (re)start
> + sending new data.
> +- atmel,rts-high-threshold: when the RX FIFO level crosses up this threshold,
> + the RTS line is driven to high level to tell the remote peer that it should
> + stop sending new data.
Maintainers, are there any guidelines for what is appropriate to put
into DT? The parameters above look like they could be programmed at
runtime through some user space API like sysfs.
WARNING: multiple messages have this Message-ID (diff)
From: moorray3@wp.pl (Jakub Kiciński)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH linux-next 1/4] ARM: at91/dt: add new DT properties for Atmel usart
Date: Thu, 4 Jun 2015 14:34:57 +0200 [thread overview]
Message-ID: <20150604143457.2a0e0acf@north> (raw)
In-Reply-To: <6fe7914a2c39245ac9a05cdb9962b88c409ec1a4.1433253787.git.cyrille.pitchen@atmel.com>
On Tue, 2 Jun 2015 16:18:21 +0200, Cyrille Pitchen wrote:
> +- atmel,rts-low-threshold: when the RX FIFO level, ie the number of data
> + available to be read from the RX FIFO, crosses down this threshold the RTS
> + line is driven to low level to tell the remote peer that it can (re)start
> + sending new data.
> +- atmel,rts-high-threshold: when the RX FIFO level crosses up this threshold,
> + the RTS line is driven to high level to tell the remote peer that it should
> + stop sending new data.
Maintainers, are there any guidelines for what is appropriate to put
into DT? The parameters above look like they could be programmed at
runtime through some user space API like sysfs.
WARNING: multiple messages have this Message-ID (diff)
From: "Jakub Kiciński" <moorray3@wp.pl>
To: <linux-serial@vger.kernel.org>, <devicetree@vger.kernel.org>
Cc: Cyrille Pitchen <cyrille.pitchen@atmel.com>,
<nicolas.ferre@atmel.com>, <gregkh@linuxfoundation.org>,
<wenyou.yang@atmel.com>, <ludovic.desroches@atmel.com>,
<leilei.zhao@atmel.com>, <josh.wu@atmel.com>,
<alexandre.belloni@free-electrons.com>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <galak@codeaurora.org>,
<ijc+devicetree@hellion.org.uk>, <mark.rutland@arm.com>,
<pawel.moll@arm.com>, <robh+dt@kernel.org>
Subject: Re: [PATCH linux-next 1/4] ARM: at91/dt: add new DT properties for Atmel usart
Date: Thu, 4 Jun 2015 14:34:57 +0200 [thread overview]
Message-ID: <20150604143457.2a0e0acf@north> (raw)
In-Reply-To: <6fe7914a2c39245ac9a05cdb9962b88c409ec1a4.1433253787.git.cyrille.pitchen@atmel.com>
On Tue, 2 Jun 2015 16:18:21 +0200, Cyrille Pitchen wrote:
> +- atmel,rts-low-threshold: when the RX FIFO level, ie the number of data
> + available to be read from the RX FIFO, crosses down this threshold the RTS
> + line is driven to low level to tell the remote peer that it can (re)start
> + sending new data.
> +- atmel,rts-high-threshold: when the RX FIFO level crosses up this threshold,
> + the RTS line is driven to high level to tell the remote peer that it should
> + stop sending new data.
Maintainers, are there any guidelines for what is appropriate to put
into DT? The parameters above look like they could be programmed at
runtime through some user space API like sysfs.
next prev parent reply other threads:[~2015-06-04 12:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 14:18 [PATCH linux-next 0/4] tty/serial: at91: add support to FIFOs Cyrille Pitchen
2015-06-02 14:18 ` Cyrille Pitchen
2015-06-02 14:18 ` Cyrille Pitchen
[not found] ` <cover.1433253787.git.cyrille.pitchen-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
2015-06-02 14:18 ` [PATCH linux-next 1/4] ARM: at91/dt: add new DT properties for Atmel usart Cyrille Pitchen
2015-06-02 14:18 ` Cyrille Pitchen
2015-06-02 14:18 ` Cyrille Pitchen
2015-06-04 12:34 ` Jakub Kiciński [this message]
2015-06-04 12:34 ` Jakub Kiciński
2015-06-04 12:34 ` Jakub Kiciński
2015-06-02 14:18 ` [PATCH linux-next 2/4] tty/serial: at91: fix some macro definitions to fit coding style Cyrille Pitchen
2015-06-02 14:18 ` Cyrille Pitchen
2015-06-02 14:18 ` Cyrille Pitchen
2015-06-02 14:18 ` [PATCH linux-next 3/4] tty/serial: at91: add support to FIFOs Cyrille Pitchen
2015-06-02 14:18 ` Cyrille Pitchen
2015-06-02 14:18 ` Cyrille Pitchen
2015-06-02 14:18 ` [PATCH linux-next 4/4] tty/serial: at91: use 32bit writes into TX FIFO when DMA is enabled Cyrille Pitchen
2015-06-02 14:18 ` Cyrille Pitchen
2015-06-02 14:18 ` Cyrille Pitchen
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=20150604143457.2a0e0acf@north \
--to=moorray3@wp.pl \
--cc=alexandre.belloni@free-electrons.com \
--cc=cyrille.pitchen@atmel.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=josh.wu@atmel.com \
--cc=leilei.zhao@atmel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=ludovic.desroches@atmel.com \
--cc=mark.rutland@arm.com \
--cc=nicolas.ferre@atmel.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=wenyou.yang@atmel.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.